Your roadmap is a lie and that's fine
Most roadmaps are fiction dressed up as strategy. The problem is not that plans change, it is that teams pretend they won’t.
6 min read
Most roadmaps are fiction dressed up as strategy. A list of features sorted by quarter, colour coded by team, presented to stakeholders as a plan. Everyone in the room knows it will change. Nobody says it out loud.
The problem is not that roadmaps are inaccurate. It is that teams treat them as commitments instead of hypotheses. When the roadmap shifts, which it always does, the conversation becomes about why the plan failed rather than what the new information is telling you.
The roadmap is not the strategy
A roadmap is an output. It represents what you think you will build, in what order, given what you know today. The strategy is the thinking underneath it. Why these problems. Why this sequence. What you are trying to learn and what you are optimising for.
When those two things get confused, the roadmap starts to drive decisions it was never meant to make. Teams defend items on the list because they are on the list. Stakeholders anchor to dates because the dates were written down. The document becomes more important than the reasoning behind it.
Certainty is the wrong goal
A roadmap that never changes is not a sign of good planning. It is a sign that nobody is paying attention. Markets shift, customers tell you things you did not expect, engineers surface constraints that change the shape of the problem. A team that absorbs all of that and ships exactly what was on the slide deck three quarters ago has not demonstrated discipline. It has demonstrated rigidity.
The goal is not a roadmap that holds. The goal is a team that can update its thinking quickly and communicate that clearly.
What to do instead
Be honest about the horizon. The next six weeks can probably be planned with reasonable confidence. The next six months is a direction. Anything beyond that is a guess and should be presented as one.
Separate the now from the later. Items close to shipping deserve detail. Items further out deserve less. A roadmap that has the same level of specificity across twelve months is misleading by design.
Make the reasoning visible. When something moves or gets cut, explain why. Not as a defence, but as a record. Teams that understand the thinking behind decisions make better ones themselves.
The lie is fine
Every roadmap is wrong before it is finished. That is not a failure of planning, it is just the nature of building products in uncertain conditions. The teams that handle this well are not the ones with the most accurate roadmaps. They are the ones that are honest about what they know, clear about what they are trying to achieve, and quick to update when the picture changes.
A roadmap that nobody believes is a problem. A roadmap that everyone knows is a hypothesis is just a tool doing its job.
By Curtis Blunden
9 March 2026