Gif by muppetwiki on Giphy
You spent two weeks building a roadmap. Talked to stakeholders. Gathered input. Prioritized ruthlessly. Presented it to leadership with confidence.
That was six weeks ago. Since then, your biggest customer changed their requirements. A competitor launched something that shifted the conversation. And the engineer who was going to build the Q2 initiative gave notice.
Your roadmap doesn't know any of this. It's still sitting in a slide deck, looking authoritative.
The confidence problem
Roadmaps create a false sense of certainty. The further out you plan, the less accurate it gets. But the format doesn't show that. Q1 looks just as solid as Q4. Every box is the same size. Every timeline looks firm.
Nobody puts error bars on a roadmap. But they should.
What decays fastest
Strategic assumptions decay first. The market insight that shaped your H2 plan might be irrelevant by the time H2 starts. The customer segment you're targeting might have shifted. The competitive landscape you analyzed is a snapshot of a moving picture.
Then resource assumptions decay. The team you planned around won't be the team you have. People leave. Priorities shift. That "available in April" engineer is now firefighting a production issue until June.
The real cost
Teams keep building toward an outdated roadmap because changing it feels like failure. So you ship features that made sense in January but not in May. You hit the plan and miss the point.
What works instead
Treat your roadmap like a living document with an expiration date on every item. Review it monthly. Not to check progress. To check relevance.
The question isn't "are we on track?" It's "is this still the right track?"
Tom