Roadmaps and Communicating Priorities
Explain intended outcomes and the confidence behind timing. · Execution & Communication · Lesson 65 · 3 min
Roadmaps and Communicating Priorities · 3 min
Situation
A date becomes a promise nobody meant to make.
A roadmap places “advanced search” in November. A stakeholder treats it as a committed launch, even though discovery has not established scope or feasibility.
Roadmaps communicate intent. Without explicit confidence and commitment levels, a planning aid can create misleading expectations.
Mental model
Separate outcome, investment, and commitment.
An outcome describes the change you want for users or the business. An investment names work intended to produce it. A delivery commitment includes defined scope and timing with an understood basis.
Near-term work can be more specific. Distant work usually carries more uncertainty. Choose a format that makes that difference visible.
Example
Communicate the reason for the sequence.
“Now: improve successful document retrieval for support teams. Next: extend retrieval across connected tools after we validate permissions and data access. Later: explore broader knowledge discovery.”
This explains a direction without pretending every feature is fully defined. Real deadlines still belong in the plan when they reflect actual constraints.
Failure case
An outcome label hides a feature calendar.
Calling a quarter “customer delight” while listing fixed features underneath does not create an outcome-oriented roadmap. State the behavior to improve and how evidence can change the solution.
Likewise, avoiding all dates can be unhelpful when other teams must plan a launch. Communicate uncertainty honestly rather than using vagueness to avoid coordination.
PM decision
Explain “not now” with a condition.
“We are deferring custom themes because retrieval failures affect the core workflow. We will revisit themes after the reliability target is met and we understand demand among retained teams.”
Acknowledge the request's value without inventing a delivery promise. Give stakeholders a clear review condition and a place to add new evidence.
Remember this
A roadmap should explain why the sequence makes sense.
Show outcomes, assumptions, and confidence. People can coordinate better when they know which items are commitments and which are still bets.