Main idea

People read a roadmap through what it displays. Its effect, however, comes from what it leaves outside: everything absent from all of its columns is out of scope for the current horizon. That refusal is written nowhere — no column is called "no" — and it is nonetheless the only part that produces focus.

Saying you are moving forward on automation, onboarding and reducing support load is saying, in the same move, that you will not now do the interface overhaul, the integrations marketplace, the accountant portal and the specific requests of a small segment. What you do and what you do not do are two halves of the same decision; writing only one of them lets people believe the other stays open.

A roadmap that does not allow that refusal aligns nobody. It files the conflicts into a presentable order and defers them to execution, when the choice will have to be made for real and nobody will remember it should have been made earlier.

Why it matters

It shifts the quality test for a roadmap. It is usually judged on the relevance of what it contains; the useful test is to ask what it excludes, and to check that someone can name it.

It also defuses the charge made against renunciation — "we're closing doors". Renunciation is not collateral damage of prioritization: it is the mechanism by which prioritization produces anything at all.

Nuances and limits

An implicit refusal is still a refusal nobody has formulated. It protects the team's focus without protecting the discarded topic from reappearing: nobody signed, so nobody has to go back on their signature.

And exclusion only makes sense within a bounded horizon. A "we won't do it" that reads as "never" manufactures needless opposition, when the exact sentence is: for now, barring a major disruption.

Open questions

• Should the list of what is out of scope be written down, at the risk of turning an implicit refusal into an explicit negotiation topic by topic?