roadmapping-and-tradeoff-communication

Roadmapping and Tradeoff Communication

Build roadmaps around outcomes and horizons, not features and dates. Communicate tradeoffs by naming the mechanism that would have to change, not by softening a refusal.

Why date-committed feature roadmaps backfire

A roadmap that lists "Feature X — ships March 15" makes a promise the team usually cannot keep, for reasons that have nothing to do with execution quality: estimates made months out are wrong by construction (unknown unknowns compound over time), priorities shift as the market or the data changes, and the roadmap gets treated as a contract the moment a stakeholder builds their own plan on top of that date. When the date slips — and on any roadmap spanning more than a few weeks, some date will slip — the failure mode isn't the delay itself, it's that stakeholders correctly learn the roadmap's dates were never reliable and stop trusting the next roadmap too. The trust damage compounds across cycles, not just within one.

The deeper problem: a date-committed feature list states false certainty about two things at once — that this specific feature is the right solution (not yet validated), and that it will take exactly this long (not yet known). Bundling an unvalidated solution with a precise date manufactures confidence the underlying work doesn't support.

Now / Next / Later

Popularized by Janna Bastow (co-founder of ProdPad) as a response to the date-driven Gantt roadmap, Now/Next/Later organizes roadmap items into three horizons instead of a calendar:

• Now — actively being worked on. Specific enough to describe concrete scope; confidence is high because it's in progress or fully scoped.
• Next — validated as a priority and coming after Now, but not yet scoped in detail. Sequencing is fairly firm; timing is not.
• Later — directionally important, on the radar, but not yet validated or prioritized against everything else that could land there. Genuinely likely to change.

The horizon itself communicates confidence implicitly, without ever writing a date — an item in "Later" tells the stakeholder "this is a direction we believe in, not a commitment" without saying that sentence out loud every time someone asks. This is the format's real mechanism: it replaces an explicit date (which reads as a promise) with a positional signal (which reads as a confidence level) that degrades gracefully instead of breaking trust when it moves.