Main idea

A roadmap is reviewed on a cadence, and that cadence is chosen between two symmetrical failures. Too short, and the roadmap turns back into a permanent topic of discussion: every new opportunity reopens the debate, check-ins turn into power games, and the team spends its time defending what it should have been doing. Too long, and it keeps topics that no longer match the strategy, the market or actual capacity, and the gap gets discovered at execution.

A quarterly cadence is often a workable baseline. It can coexist with more frequent check-ins — monthly with sales and stakeholders — as long as their role is to surface signals and not to overturn the roadmap with every opportunity.

The entry and exit rules must stay simple: a topic enters if it has enough value, signals, strategic tie-in and available capacity; it exits if a stronger topic enters, if the strategy changes, if the signals disappear, if feasibility collapses, or if a disruption redistributes the priorities.

Why it matters

It gives something to discuss when a roadmap "doesn't hold": the frequency, rather than the content. Many conflicts over priorities are conflicts over the right to reopen them.

It also distinguishes two rituals people often merge — the review that decides and the check-in that informs. Giving the second the same format as the first is authorizing continuous renegotiation.

Nuances and limits

The right cadence depends on the speed of the market: in a domain where disruptions are rare, six months is enough; in a moving domain, a quarter is already long.

And a fixed cadence does not rule out exceptional reopenings. What matters is that they stay exceptional and are recognized as such, otherwise the cadence is only for show.

Open questions

• What event justifies reopening a roadmap off-cadence, without the exception becoming the rule?