Setting Milestones: What, When, and Who Reviews

This section reveals the specific negative impacts that inadequate milestone setting has on projects.

Consider a website development project where client company A and freelance designer B set a milestone of "design completion by month-end." However, this setting lacks crucial elements.

Chain Reaction of Delivery Delays

Because "design completion" was ambiguous, B submitted three rough concept patterns, but company A expected detailed mockups. As a result, additional work was required, delaying the subsequent coding phase by two weeks. This delay forced company A to postpone their planned marketing campaign, resulting in opportunity losses.

Delayed Surface Recognition of Quality Issues

Since the review personnel were unclear, the approval process within company A stalled. When the representative sought confirmation from their supervisor, fundamental directional changes were requested, necessitating rework of most of the project. At this point, 70% of the entire project had already been completed, so revision costs ballooned to three times the initial estimate.

Additional Cost Generation and Disputes

Because the review items at milestones were unclear, functions that company A considered "naturally included" were outside B's scope of work. This perception gap led to disputes over additional fee requests, ultimately deteriorating the relationship between both parties and resulting in contract termination. B fell into a situation where even collecting payment for completed work became difficult.

Common to these failures is the ambiguity in milestone setting regarding "what to review," "when to review," and "who reviews." Seemingly simple progress management oversights developed into serious issues that determined the success or failure of entire projects.

This section analyzes the structural causes behind milestone setting becoming mere formalities and the perception gaps between stakeholders.

The "We're Doing It" Trap

Despite milestones being set in many projects, they often don't actually function. This is because while the concept of "project milestones" is understood, its implementation remains superficial.

For example, milestones like "Phase 1 completion," "interim report," and "final review" appear appropriate at first glance. However, these actually contain only timeline information—the "when"—while lacking the "what" and "who" elements.

Contractor Thought Patterns

Contractors have a psychological tendency to focus on their area of expertise. Therefore, they tend to perceive milestone setting as "reporting obligations to clients." Under this perception, milestones become bothersome interruptions that disrupt work, leading to merely formal responses.

In reality, freelance programmer C, thinking "if the code works, there's no problem," neglected detailed progress reporting to clients. As a result, they implemented functions that differed from the client's expected specifications, requiring major revisions.

Client Management Deficiencies

Clients also face problems. Many clients neglect appropriate reviews due to excessive trust, thinking "I'm leaving it to professionals, so it's fine." Additionally, because internal decision-making processes aren't established, they cannot respond quickly to review requests from contractors.

Information Asymmetry

Information gaps exist between contractors and clients regarding specialized knowledge and industry practices. This asymmetry causes both parties to assume "the other party naturally understands," leading to oversight of important review items.

Consider a milestone example of "design comp review." The designer envisions "layout and color scheme confirmation," but the client believes it includes "implementation feasibility and usability verification." This gap becomes the source of later troubles.

This section presents a specific five-stage process for effective milestone setting.

Stage 1: Detailed Definition of Deliverables

First, specify "what to review." Avoid abstract expressions and define measurable deliverables.

Good examples:

• "TOP page design comps (PC and mobile versions), 3 color pattern options, font specification document, image specification document"
• "User registration function test URL, 50 test data entries, operation verification procedure manual"

Bad examples:

• "Design proposal"
• "Function implementation"

Stage 2: Setting Review Criteria

Quantify or specify the criteria by which deliverables are considered "complete."

Specific criteria setting examples:

• Design comps: Use of specified brand colors, font size 14px or larger, 3 responsive design patterns
• Function implementation: Error handling implemented, response time under 2 seconds, operation confirmed on 3 major browsers

Stage 3: Subdividing Review Timing

Divide "when to review" into multiple timings to enable early detection.

Timing setting example (for website development):

• 3 days after kickoff: Requirements definition document draft review
• 1 week after start: Wireframe interim review
• 10 days after start: Design comp first draft review
• 14 days after start: Design comp final review

Stage 4: Clear Designation of Responsible Parties

Designate responsible parties for both contractor and client sides regarding "who reviews."

Responsibility distribution clarification:

• Contractor side: Project manager (progress management), technical lead (quality confirmation)
• Client side: Project contact (daily confirmation), final decision maker (approval), technical reviewer (specification validity)

Stage 5: Standardizing Review Processes

Standardize review procedures for each milestone to achieve efficient operations.

Standard review process example:

1. Contractor submits deliverables and review request (2 business days before deadline)
2. Client reviews content and conducts internal coordination (within 1 business day)
3. Review meeting held (30 minutes, as needed)
4. Issue revision instruction document if modifications needed (within 1 business day of review)
5. Final approval/rejection response (within 1 business day of revision completion)

Through this five-stage process, "milestone setting" transforms from mere schedule management into a system for early detection and response to project risks.

This section presents frequently occurring problems in the operational phase after milestone setting and their countermeasures.

Trap 1: Formalized Reviews

Even with properly set milestones, actual reviews often become superficial. Particularly when projects are progressing smoothly, review work becomes a mere ritual of "pretending to have reviewed."

In an actual case from an e-commerce site construction project, the client approved the design saying "it looks good, so approved," but hadn't actually conducted usability testing. Later, numerous complaints about poor usability came from actual users, requiring major revisions.

Countermeasure: Always use "checklists" during reviews and verify each item specifically. Document review criteria so the same quality can be maintained regardless of who conducts the review.

Trap 2: Blank Periods Between Milestones

Progress reviews cease during periods between milestones. Problems occurring during these blank periods remain undetected until the next milestone.

For example, a serious misunderstanding about requirements interpretation occurred during the 3-week period between "requirements definition completion" and "design document completion," but wasn't discovered until design document submission. By this point, massive amounts of work had already been wasted.

Countermeasure: Establish "interim checks" between milestones. Build weekly brief progress reports and systems for consulting on questions as they arise.

Trap 3: Ambiguous Revision Instructions

Even when problems are discovered at milestones, revision work isn't performed accurately due to vague revision instructions.

Abstract instructions like "make it feel brighter" or "make it more user-friendly" don't allow contractors to determine specific revision directions. This results in repeated revisions.

Countermeasure: Make revision instructions clear about "what," "how," and "why." Provide reference examples and numerical criteria whenever possible.

Trap 4: Unclear Approval Authority

Even when approvers are determined at project start, approval delays frequently occur at actual approval stages due to reasons like "supervisor confirmation needed" or "coordination with other departments required."

In an actual example from a small company's website renewal project, the representative held up approval saying "CEO's final confirmation needed," and the CEO couldn't review for two weeks due to being busy. During this time, the contractor couldn't proceed to the next phase, causing the entire project to stagnate.

Countermeasure: Clearly determine approval flows and proxy approvers for each milestone at project start. Document the scope and limitations of approval authority.

By avoiding these traps, you can maintain a progress management system where milestones truly function.

This section presents mechanisms for continuous improvement that leverage milestone setting and methods for building long-term collaborative relationships.

Institutionalizing Reflection Cycles

Always conduct reflection meetings after achieving each milestone. These reflections verify deviations from plans, problems that occurred, and the effectiveness of countermeasures, applying lessons learned to setting subsequent milestones.

Specific reflection perspectives:

• Schedule: Was completion on time achieved? What caused delays?
• Quality: Were review criteria appropriate? Were there overlooked problems?
• Communication: Was information sharing smooth? Did misunderstandings occur?
• Process: Is there room for improvement in review procedures?

Precision Improvement Through Data Accumulation

Accumulate data on milestone achievement status, revision frequency, and approval time for each project. Analyzing this data enables more realistic milestone setting.

For example, if the average time required for "design comp review" across the past 10 website development projects was 5.2 days, future projects could be planned with a comfortable 7-day allocation.

Growth Support for Both Contractors and Clients

Through effective milestone operations, project management skills improve for both parties. Contractors become able to create more precise work plans, while clients develop appropriate review and judgment capabilities.

Risk Prevention System Strengthening

Use milestones not just for progress confirmation but as early risk detection systems. Always confirm "is it safe to proceed as is?" and "are there additional risks?" at each milestone.

Risk confirmation perspectives:

• Technical risks: Implementation feasibility, performance requirement achievability
• Schedule risks: Impact on subsequent phases, delay possibilities from external factors
• Quality risks: Deviation from requirements, usability problems
• Cost risks: Additional work occurrence, specification change impacts

Continuous Relationship Building

Even for one-off projects, build trust relationships through milestone operations with future collaboration in mind. Understanding each other's working styles and judgment criteria enables more efficient collaboration in subsequent projects.

Balancing Standardization and Customization

Prepare basic milestone setting templates while maintaining flexibility to customize according to project characteristics. Complete standardization cannot address individual project peculiarities, while complete customization reduces efficiency.

Through this continuous improvement mechanism, milestone setting transforms from a simple management technique into important competitive advantage that increases project success rates. For contractors, it leads to improved evaluation as reliable partners; for clients, it realizes reduced collaboration costs with external partners and quality improvements.

Effective milestone setting isn't finished once established. By improving with each project and accumulating organizational learning, it becomes the foundation for building sustainable collaborative systems. Contractors become able to make more precise proposals for subsequent projects, while clients develop the ability to fulfill proactive management responsibilities in collaborations with external partners.