Build a simple roadmap that expresses priorities and direction rather than a guaranteed list of dates.
What a roadmap actually is
A roadmap communicates direction, not a delivery calendar
A product roadmap is not a project plan. It does not promise exact features on exact dates. Instead, it answers: What problems are we solving? In what order do they matter? Where are we going?
The danger of a date-oriented roadmap is that it freezes assumptions. When discovery reveals something new, the team is trapped — the date is already on the calendar, the feature is already promised, and learning becomes the enemy of the plan.
Outcome-oriented roadmaps focus on the change in user behavior or business result you want to achieve, not on the output (feature) you intend to ship. Instead of "Launch dark mode in Q2," an outcome roadmap says: "Reduce evening session drop-off by 20%."
The now / next / later framing replaces calendar columns with confidence columns. "Now" = what the team is actively working on. "Next" = what is planned with reasonable confidence. "Later" = directional bets that may change. This framing is honest about uncertainty and keeps the roadmap a living document, not a commitment ledger.
Prioritization frameworks from Unit 4 — RICE, MoSCoW, Kano — feed directly into roadmap ordering: the items with the highest validated priority land in "Now" or "Next"; lower-priority and more speculative items stay in "Later."
Lesson notes
A roadmap communicates direction, not a delivery calendar
A product roadmap is not a project plan. It does not promise exact features on exact dates. Instead, it answers: What problems are we solving? In what order do they matter? Where are we going?
The danger of a date-oriented roadmap is that it freezes assumptions. When discovery reveals something new, the team is trapped — the date is already on the calendar, the feature is already promised, and learning becomes the enemy of the plan.
Outcome-oriented roadmaps focus on the change in user behavior or business result you want to achieve, not on the output (feature) you intend to ship. Instead of "Launch dark mode in Q2," an outcome roadmap says: "Reduce evening session drop-off by 20%."
The now / next / later framing replaces calendar columns with confidence columns. "Now" = what the team is actively working on. "Next" = what is planned with reasonable confidence. "Later" = directional bets that may change. This framing is honest about uncertainty and keeps the roadmap a living document, not a commitment ledger.
Prioritization frameworks from Unit 4 — RICE, MoSCoW, Kano — feed directly into roadmap ordering: the items with the highest validated priority land in "Now" or "Next"; lower-priority and more speculative items stay in "Later."