A missed milestone is the first indication of a project going awry.

— #ProjectManagementTweet, Himanshu Jhamb & Guy Ralfe (2010)

It was a rare slow Monday. I’d made it to my desk, filled the coffee mug, and had just enough time for one good sip while it was still hot before the head of sales appeared in my doorway, looking harried.

He hadn’t come to chat. He’d just come off a call with an unhappy customer — two months from launch, and, in his words, out of confidence that we’d make it. It was a clear escalation, the kind that lands on your desk fully formed, before anyone below you has had the chance to explain themselves.

What the Investigation Found

When I sat down with the delivery team, the plan on paper looked fine. Work was broken into sprints, each with its own interim milestone. What had actually happened was that several of those interim milestones had been missed — quietly, one after another, for weeks.

The root cause, once we found it, was almost mundane. The original plan hadn’t allowed enough time for the customer to test each increment and send back changes. Every feedback cycle ran a little longer than budgeted, which pushed straight into the next sprint’s development time. When the customer came back with a heavy batch of defects, the team had to choose between fixing what had already shipped and building what came next. They chose fixing, — because that’s what the customer wanted. Building fell further behind. Nobody planned for this to happen. It simply compounded, sprint after sprint, until it surfaced as a phone call to a head of sales who had no idea it was coming.

Why Nobody Caught It Sooner

This is the part that actually interests me, more than the scheduling mistake itself. None of the individual missed milestones looked serious enough to escalate. Each one had an explanation — a slow test cycle here, a defect list there — and each explanation was true. Taken one at a time, every miss looked recoverable. It was only when I looked across all of them together that the pattern became obvious: the gap between where we said we were and where we actually were had been growing, quietly, for over a month.

That’s the trap. A missed milestone doesn’t announce itself as a crisis. It looks like a rounding error, a bad sprint, a one-off. The people closest to the work have every incentive to treat it that way, because investigating it properly takes time they feel they don’t have, and admitting it might be a pattern feels like admitting failure before anyone is sure there is one.

What I Took Away

Not every missed milestone is a five-alarm fire. Some genuinely are recoverable, and treating every hiccup as a crisis is its own kind of dysfunction. But the milestones that aren’t recoverable are, without exception, the ones nobody investigated the first time they slipped.

The fix isn’t more process. It’s a standing discipline: the first time a milestone is missed, get to the actual root cause before deciding it’s minor — not after the third or fourth miss, when the gap has already become expensive to close. Vigilance means watching for the miss before it happens. Being clinical means, once it does happen, refusing to accept the first plausible-sounding explanation as the real one.

If your team’s response to a missed date always comes with a specific, reasonable-sounding explanation, that’s worth listening to twice — once for the excuse, and once for the pattern that might be hiding behind it. I’m happy to help you listen for the second one.