Creating Milestones Customers Can Understand
Milestones should describe meaningful project outcomes. A list of internal development tasks can be detailed while still leaving a customer unsure what has been achieved.

Describe the deliverable or decision
Use milestones such as approval of a page design or completion of a tested enquiry journey. Explain what evidence demonstrates completion and whether the customer must provide anything. Keep estimates separate from commitments and update them when the agreed plan changes.
Practical checklist
- Name a visible outcome.
- Define completion criteria.
- Identify dependencies.
- Show the next required action.
How to review the result
A customer should be able to understand the milestone without learning your internal task system. Rewrite items that only make sense to the implementation team.