Unit 7: Roadmapping: planning without over-committing

Learning objectives

By the end of this unit, you should be able to distinguish between different roadmap formats and when to use each, create a now-next-later roadmap, and communicate a roadmap to stakeholders with appropriate levels of commitment.

Video script

Reading material

Roadmap formats compared

Feature roadmap (timeline). A list of features mapped to dates or quarters. Easy to understand, easy to over-commit. Best for: situations where stakeholders need delivery commitments and the team is building well-understood features.

Outcome roadmap. Organized around metrics or objectives rather than features. Each row is an outcome with the initiatives that contribute to it. Best for: mature product organizations where stakeholders trust teams to find the right solutions.

Now-next-later. Three columns of decreasing commitment. Best for: most teams, especially those navigating uncertainty or building in fast-changing areas like AI.

Theme-based roadmap. Organized around strategic themes or pillars. Each theme groups related work without committing to specific timelines. Best for: communicating direction to broad audiences like all-hands meetings or customer advisory boards.

No format is universally correct. Choose based on your audience and the level of certainty you can honestly provide.

Stakeholder communication

Different stakeholders need different things from your roadmap.

Sales needs to know what they can promise customers in the near term. Give them the "now" column with enough detail to have credible conversations.

Leadership needs to know the strategic direction and that progress is being made. Give them the outcome framing with evidence of learning and impact.

Engineering needs to know what's coming so they can plan architecture and staffing. Give them the "now" column in detail and the "next" column for preliminary planning.

Customers need to know that their problems are being addressed without getting specific delivery commitments. Give them the theme-based view.

Tailor the format to the audience. Using the same roadmap for all stakeholders is a common mistake that either over-commits to the detail-oriented audiences or under-informs the strategic ones.

Practical exercise

Exercise: Create a now-next-later roadmap

Using the product you chose in earlier exercises (or a new one), create a now-next-later roadmap.

"Now" (2-4 weeks): List 2-3 specific things being built or about to be built. Include a brief outcome each one targets.

"Next" (1-2 months): List 2-3 problems that have been validated but don't have committed solutions yet. Describe the problem, not the solution.

"Later" (3-6 months): List 2-3 opportunity areas based on strategic direction. Keep these broad.

Then write a three-sentence summary you could use to present this roadmap to a non-technical stakeholder. Focus on the "why" behind the priorities.