The status report lists twenty completed tasks, yet nobody knows whether the next delivery commitment is secure. Tasks describe work to do. A milestone marks a significant point or achievement in the project. Use both, but do not mistake a busy task list for evidence that an important outcome is ready.
Photo by Rodrigo Rodrigues, WOLF ART on Unsplash.
For a small team, the useful question is simple: what must be demonstrably true at this checkpoint, and who will confirm it?
Write milestones as checkable states
“Testing” is an activity. “Agreed acceptance checks completed and reviewed” describes a checkpoint. Avoid using a milestone label to conceal unfinished decisions.
For each milestone, record:
The state or event being confirmed.
Evidence needed to demonstrate it.
Person authorised to confirm the result.
Planned date and latest credible forecast.
Dependencies that could prevent the checkpoint.
The date matters, but it is not the definition of completion. Reaching Friday does not make a deliverable ready.
Connect tasks to the checkpoint
Work backwards from the required evidence. If a milestone needs an approved process, the tasks might include drafting it, testing a representative case, resolving exceptions and obtaining approval. Each task should contribute to a result rather than simply keep someone occupied.
You do not need a milestone for every small task. Too many checkpoints can make the meaningful decisions difficult to see. Choose the ones that release dependent work, confirm an important result or require a sponsor's decision.
A hypothetical checkpoint review
A service business is introducing a new client reporting process. “Template designed” is complete, but the first trial exposes missing information and no agreed owner for obtaining it. The milestone “Reporting process ready for operational use” remains open.
The team can report the completed design honestly while showing the remaining acceptance gap. That gives the sponsor a useful decision: resolve ownership, adjust the intended use or move the readiness date.
Report movement in the forecast
At each review, compare the expected checkpoint date with the agreed plan and explain the cause of any movement. Keep completed task counts as supporting information where useful, not the headline proof of readiness.
Related guidance: small-team project planning guide.
If project updates show activity without a clear view of delivery confidence, Hili Consulting can help define milestones that make progress and decisions easier to judge.
