Project milestones: what they are for and how to place them

A milestone is a point in the schedule with no duration and no workload: it marks that something has been reached. End of a phase, deliverable accepted, gate passed, go-live. Where a task answers “who does what, for how long”, a milestone answers a single question — is it done, yes or no. That binary nature is exactly what makes it readable by people who will never open the detailed plan.

Why a plan without milestones is unsteerable

A schedule made only of tasks slides quietly: each task moves a little, nothing looks alarming, and the end date drifts by two months without any single moment where someone had to say so. Milestones force that moment. They are the points where the project stops and states its position, and they are what a steering committee actually reviews — not the 400 lines underneath.

What makes a good milestone

A milestone must be verifiable without discussion. “Specification approved by the business” is a milestone; “specification nearly finished” is not. It must also belong to someone: a milestone with no owner is a date nobody defends. And it must be rare enough to mean something — a plan with a milestone every week has none.

Where to place them

Place milestones where the project changes state or where a decision is made: end of framing, validated design, integration complete, acceptance signed, production launch. Add one wherever an external dependency lands — a supplier delivery, a regulatory approval — because those are the dates you do not control and therefore the ones you must watch.

Milestone, gate and deliverable are not the same thing

A deliverable is a produced object. A gate is a decision authorising the next phase. A milestone is the date on which one or the other is recorded. Confusing them produces plans where a milestone is passed while the deliverable it was supposed to mark is still being written — and the schedule keeps saying everything is fine.

Following milestones in FoxPlan

In FoxPlan a milestone is a zero-duration task in the Gantt, linked to the tasks that feed it, so a delay upstream moves it visibly instead of silently. The portfolio view lists the milestones of every project on a single timeline: that is the reading a management committee needs — a few dozen dates that either hold or do not, rather than thousands of tasks.