roadmap-communication
Roadmap Communication Expert
Overview
A single roadmap cannot serve every audience. Executives need confidence and strategic framing. Customers need plausible promises with credible timelines. Internal teams need detail, dependency awareness, and honest risk. When PMs publish one roadmap to all three, one audience is always wrong -- either the executives are bored, customers feel misled, or engineers feel managed.
This skill produces three variants of the same underlying roadmap, each tailored to its audience. The underlying source of truth -- the roadmap data -- stays single. The framing, the level of detail, the risk language, and the visualization all change. The variants share names and identifiers so a customer reference can be traced back through the internal variant to the actual ticket.
The structural backbone is Now / Next / Later (popularized by Janna Bastow at ProdPad and now used widely), which Marty Cagan calls "right-sizing the roadmap" -- forecast confidence decreases with time horizon, so commit explicitly to "Now" items, name "Next" items by theme, and keep "Later" deliberately fuzzy. Each variant exposes a different slice of that backbone.
When to Use
- Quarterly roadmap publication -- the regular cadence where you communicate to multiple audiences.
- Pre-board meeting -- the executive variant feeds the board packet.
- Annual customer conference -- the customer variant becomes the conference roadmap session.
- Engineering kickoff -- the internal variant grounds sprint planning across multiple teams.
- Sales enablement -- the customer variant feeds sales reps' "what's coming" pitch.