A milestone is a date with a flag on it. It exists so that someone not on the journey can look at a chart and feel informed. A waypoint is different. A waypoint is a place you actually stand, look around, and decide where to step next. One is reporting. The other is navigation.
Most teams drown in the first and starve for the second.
The trouble with milestones
Milestones aren't evil. They're just optimised for the wrong audience. They answer "are we on schedule?" — a reasonable question — but they answer it with a binary that hides everything interesting. A milestone is hit or missed. It tells you nothing about whether you're walking toward the right summit, only whether you're walking fast enough toward the one someone picked months ago.
And because missing a milestone feels like failure, they quietly corrupt behaviour. Teams hit the date by cutting the corner you couldn't see from the chart. The flag goes up. The map says progress. The territory says debt.
What a waypoint is for
The manifesto prefers a low-ceremony, low-noise follow-up on the actual work — checking the things, not the calendar. A waypoint is a deliberate pause to ask the only questions that matter mid-journey:
- What do we know now that we didn't at the last waypoint?
- Is the destination still the right one, given what we've learned?
- What's the next, smallest, most useful step?
Notice these are navigation questions, not status questions. They assume the map might be wrong — which it always is — and they give the team permission to adjust course without it being a crisis.
Whilst stand-ups are useful, prefer a low-ceremony, less-noisy follow-up on work items.
The stand-up trap
I have nothing against stand-ups in principle. But watch one that's gone stale and you'll see the milestone disease in miniature. Three questions, performed daily, optimised for the manager's comfort rather than the team's navigation. "Yesterday I... today I... no blockers." Fifteen minutes of status theatre where the real blocker is the one nobody says out loud because the format doesn't have a slot for it.
A waypoint check-in is quieter and rarer and more honest. It's tied to the work — a push reaching its middle, a result coming in — not to the clock. It can be a fifteen-minute conversation over a screen, or a comment thread on the actual work item, or two people at a whiteboard. The ceremony isn't the point. The course-correction is.
Following the work, not the watch
Here's the reframe that helps me. Don't ask "where should we be by Friday?" Ask "what's the next thing we need to learn, and what's the cheapest way to learn it?" The first question pulls you toward a flag on someone's chart. The second pulls you along the actual path.
Plan the journey in waypoints — real places where you stop, look, and choose — and let the milestones be a thin reporting layer on top for the people who need a chart. Just don't confuse the chart for the climb. The flag isn't the summit. It's an annotation.
