September 22, 2026 · 3 min read
A roadmap is not a wish list
It is the visible consequence of business decisions made under scarcity. The difference is not wordplay — it decides where the conflict gets fought.
There are two ways to read a roadmap. One sees a list of what is coming. The other sees a list of what is not coming because of it. Both read the same document. Only the second describes what actually happened.
A roadmap does not emerge from ideas. It emerges from scarcity. Every entry means a certain number of people are not working on something else for a certain length of time. Communicate without that reverse side and you have not published a plan but a statement of intent.
Why this is more than a question of wording
A wish list can be extended. That is its decisive advantage and its actual problem: it knows no resistance. A new requirement arrives, it gets added — and everyone involved can continue to believe their concern is covered.
The conflict does not disappear. It moves to where it is most expensive: into delivery. There it no longer meets product management and the board, but a team asked to ship three committed things at once, deciding by proxy — usually by urgency, which is to say by volume.
That is the point where prioritisation is effectively delegated to the place with the least context for it.
The three time horizons
At a roadmap, interests meet that should not compete but do, because they need the same capacity.
A customer opportunity counts in weeks. It is concrete, nameable, often attached to a name and an amount. It always has an advocate.
Strategic product development counts in quarters. It is harder to justify, because at the moment of decision its value is an assumption. It usually has exactly one advocate: the product function.
Technical stability counts in years. It has no advocate at all. Nobody in sales argues for quality work, and that is not a criticism of sales — it is not their job.
All three are right. That is exactly what makes it hard: there is no proposal you can simply reject. Anyone who believes prioritisation means separating the good from the bad has never seriously prioritised.
What belongs in place of the wish list
Not a better scoring model. Models with eight factors and two decimal places produce a number everyone can hide behind — the number appears to make the decision, and nobody has to own it.
What helps is visible criteria. Demand, resources, scope, timing, dependencies, rollout impact — considered together rather than worked through in sequence. Criteria that are not spoken still operate, only uncontrolled.
And it helps to move from themes to packages. You can like a theme. You can only decide on a scope. As long as an initiative sits in the room as a headline, every agreement is consequence-free — only a cut scope forces a statement about what is in and what is out.
The price
Visible criteria make uncomfortable capacity limits visible. That is not a side effect, it is the purpose. Whoever creates transparency loses the option of deferring conflict — and deferral is the most popular instrument in any organisation, because in the short term it satisfies everyone.
So the switch initially produces more friction, not less. That is the right friction at the right time: early, among the people allowed to decide, rather than late, in a team that can only absorb it.
What this looks like in practice is in the case study on product governance.