What makes a good milestone
A milestone is an observable state with a date: the beta is in ten customers’ hands, the new pricing is live, the audit letter is signed. Good milestones share three properties. They are verifiable by someone outside the team, so status debates end. They are outcomes, not activities, so "testing complete" beats "testing in progress" and "requirements written" is suspiciously weak. And they are spaced two to six weeks apart, close enough to catch drift, far enough apart to be meaningful.
If a milestone cannot fail, it is not a milestone, it is a status update wearing a date.
Rolling wave: plan near, sketch far
The rolling wave method resolves the planning paradox: detail decays with distance, but leadership needs a full horizon. Plan the next six to eight weeks at milestone level with owners and dates. Sketch the following quarter as named milestones without commitments. Leave everything beyond as themes. Each week, the wave rolls: the nearest sketch hardens into commitments, and the horizon extends.
This is also where the market has landed. The visible trend across modern portfolio tooling and practice is away from twelve month task plans toward near term commitments plus a themed horizon, because that is the shape that survives contact with customers.
Keeping the roadmap honest
A roadmap stays honest through two rules. Moving a milestone is a decision, made by the sponsor and logged, never a quiet edit; the difference between a slip and a decision is whether anyone chose it. And the roadmap is reviewed against reality weekly in the same standing review that covers risks and decisions, so drift is caught inside the two to six week spacing of the milestones themselves. A dishonest roadmap is worse than none, because it launders drift into surprise.
Milestones with owners, dates and a memory
The PMO Desk plans in milestones natively: each project carries its dated commitments, My Day surfaces anything due within seven days or overdue, and moving a date is a logged decision with a reason, so the roadmap keeps its memory. The portfolio view rolls every project’s milestones into one picture for the weekly review.
Velora drafts a milestone plan from the charter in seconds and flags spacing that is too coarse or too fine. It is the rolling wave method with the bookkeeping done for you, from the Plus membership up.
Frequently asked questions
How many milestones should a project have?
Five to eight for a typical SMB project, spaced two to six weeks apart. Fewer and drift hides between them; more and you are back to task tracking.
Are Gantt charts obsolete?
No, they still suit fixed-sequence work like construction or compliance programs. For product, marketing and operations projects, milestone plans plus a themed horizon steer better and cost far less to maintain.
What happens when a milestone slips?
It becomes a decision: the sponsor moves the date with a logged reason, or the scope changes, or the project returns to a gate. The one forbidden outcome is the quiet edit.