Roadmapping

A roadmap isn't a list of features with dates. It's a living negotiation about where the organization places its bets and why.

Overview

Roadmapping is both an activity and an artifact. The artifact is an outcome-based roadmap with Now/Next/Later columns, each outcome carrying its impact, metrics, and scope. The activity is the continuous, collaborative negotiation that keeps that roadmap alive and useful.

The practice of roadmapping has four main activities:

1. Creation and initial alignment: gather stakeholder input on strategic priorities, market needs, and technical constraints. Involve key team members so scope is realistic and buy-in is real.
2. Regular review and updates: roadmaps are living documents; review at a regular cadence with updates between major revisions.
3. Communication and stakeholder management: share broadly but set clear expectations that roadmaps are forecasts, not commitments. Use them to facilitate conversations about priorities and trade-offs.
4. Integration with team outcomes: the current quarter of the roadmap should furnish your team’s target outcomes, creating tight alignment between strategic planning and tactical execution.

Patterns & Anti-patterns

Good practices: Start simple with Now/Next/Later and add complexity only as needed. Your first roadmap will be wrong, so focus on making it useful rather than perfect. Begin preparing “Next” content about halfway through the current quarter. Commit to shipping something valuable each quarter while maintaining flexibility about what that something is. Use burn-up charts to track scope completion and negotiations.

Anti-patterns: Product-only roadmaps that exclude technical investments. Feature-heavy lists without outcomes explaining intended results. Over-detailed planning for distant horizons. Treating dates as promises. Turning roadmaps into Gantt charts with dependencies and task breakdowns. “Set it and forget it” quarterly roadmaps that never evolve.

Resources

• Outcome-Based Roadmap — the roadmap format we use
• Product Logic Model — the causal model behind outcome-based roadmapping
• NOICE Prioritization — the NOICE framework for ranking outcomes
• Outcome-Based Roadmaps — our full workshop on enabling and adopting an outcome-based roadmapping practice