outcome-based-roadmaps

# Outcome-Based Roadmaps ## Overview C. Todd Lombardo's "Product Roadmaps Relaunched" redefines roadmaps as strategic communication tools aligned with company vision and goals, not feature timelines. A roadmap communicates WHY you're building, WHAT problems you're solving, and WHEN themes will be addressed—not which features ship by which dates. ## Core Insight Traditional roadmaps (Gantt charts with features and dates) become outdated immediately, create false expectations, and focus teams on output over outcomes. Outcome-based roadmaps shift focus to the impact you want to create, giving teams flexibility in how to achieve it. **Key principle**: Roadmaps answer "Where are we going?" not "What are we shipping?" ## The Roadmap Hierarchy ### Level 1: Vision Long-term (3-5 years): Why does your product exist? What future are you creating? **Example**: "Enable every small business to compete with enterprises through affordable automation" ### Level 2: Strategy Medium-term (1-2 years): How will you achieve vision? What bets are you making? **Example**: "Become the automation solution for service businesses (not retail or tech)" ### Level 3: Roadmap (Outcome Themes) Short-term (6-12 months): What problems will you solve and when? Grouped by themes. **Example**: "Q1: Reduce onboarding friction (50% drop-off) | Q2: Improve retention (30% churn)" ### Level 4: Discovery/Backlog Immediate (sprint level): What specific solutions are we testing/building? **Example**: "Test: Guided setup wizard | Build: Slack integration for notifications" **Roadmap = Level 3, not Level 4** ## Anatomy of Outcome-Based Roadmap ### Component 1: Problem Themes Group related problems into themes. Themes have business outcomes, not feature names. **Format**: [Theme Name]: [Outcome Goal] **Examples**: - "New User Success: Increase 30-day activation from 40% to 60%" - "Enterprise Expansion: Enable teams of 50+ (currently max 20)" ### Component 2: Time Horizons Show WHEN themes will be addressed, but avoid exact dates. Use quarters or "Now/Next/Later." **Now**: Current focus (committed) **Next**: Planned (high confidence) **Later**: Future consideration (low commitment) ### Component 3: Success Metrics Each theme has measurable outcome. How will you know you solved it? **Format**: [Metric] from [current] to [target] **Example**: "Reduce support tickets from 500/month to 200/month" ### Component 4: Context/Rationale Brief explanation of WHY this theme matters strategically. **Example**: "Support costs growing faster than revenue—unsustainable at scale" ## Creating an Outcome-Based Roadmap ### Step 1: Align on Strategy Before roadmap, clarify company strategy. What are top 3-5 strategic priorities? **Action**: Review company OKRs, talk to leadership, understand business goals. ### Step 2: Identify Problem Themes What customer/business problems must be solved to execute strategy? **Sources**: - Customer interviews and feedback - Usage data and drop-off points - Sales/support blockers - Market/competitive gaps **Action**: List 10-15 problems, cluster into 3-5 themes. ### Step 3: Define Outcomes per Theme For each theme, define success metric. Make it measurable. **Good outcome**: "Increase mobile conversion rate from 1.2% to 2.5%" **Bad outcome**: "Improve mobile experience" (vague, unmeasurable) ### Step 4: Sequence by Strategic Priority Order themes by which outcomes matter most to strategy right now. **Factors**: - Business impact (revenue, cost, risk) - Customer pain severity - Strategic timing (market window, competitive pressure) - Dependencies (what must happen first) ### Step 5: Assign to Time Horizons Place themes in Now/Next/Later buckets based on capacity and priority. **Guideline**: 1-2 themes "Now," 2-3 "Next," rest "Later" ### Step 6: Communicate and Update Share roadmap broadly. Explain it's outcome commitments, not feature promises. **Cadence**: Update quarterly. "Now" themes shift, outcomes may evolve based on learning. ## Example Roadmap **Company**: B2B SaaS for project management **Strategy**: Expand from startups to mid-market companies | Time | Theme | Outcome | Context | |------|-------|---------|---------| | **Now** | Team Collaboration | Increase daily active teams from 30% to 50% | Most teams use tool solo; need collaboration to justify price | | **Now** | Mobile Access | Enable 60% of tasks completable on mobile (currently 20%) | Sales blocker: customers demand mobile-first | | **Next** | Enterprise Security | Pass SOC2 audit | Required to sell to companies 500+ employees | | **Next** | Integration Ecosystem | 3rd party apps contribute 40% of value | Reduce switching costs, increase stickiness | | **Later** | AI-Powered Insights | Predictive project risk alerts | Differentiation for competitive positioning | **Note**: No specific features listed. "Team Collaboration" could be chat, notifications, @mentions, activity feeds—team discovers best solution. ## When to Use - Aligning stakeholders on priorities - Communicating product direction to sales/marketing/customers - Saying "no" to feature requests not aligned with themes - Quarterly planning and OKR setting - Fundraising/board updates (show strategic thinking) ## Anti-Patterns - ❌ Listing features with dates (that's a release plan, not roadmap) - ❌ Committing to distant future themes (lose flexibility) - ❌ Creating roadmap before strategy is clear - ❌ Making roadmap internally focused only (customers/sales need to see too) - ❌ Never updating roadmap (it should evolve as you learn) ## Success Metrics - **Stakeholder Alignment Score**: Survey "Do you understand product direction?" (target 8+/10) - **Outcome Achievement Rate**: % of themes where target metric hit - **Roadmap Volatility**: How often themes change (healthy to shift quarterly) - **Feature Request Decline Rate**: % declined because "not aligned with roadmap themes" ## Integration with Other Frameworks **Requires**: - Product Strategy Frameworks: Roadmap executes strategy - OKRs: Outcomes on roadmap = Key Results **Feeds into**: - Product Empowerment: Themes = problems empowered teams solve - Opportunity Solution Trees: Each theme explored via OST - Dual-Track Agile: Discovery focuses on "Next" themes while delivering "Now" ## Common Pitfalls ### Over-Specifying Solutions Roadmap says "Rebuild onboarding flow." That's a solution. Outcome theme: "New User Success: Increase activation." **Fix**: Name theme after outcome, let team discover solution. ### Too Many Themes Trying to do everything = doing nothing well. Focus on 1-2 "Now" themes. **Rule**: If team can't recite current themes from memory, too many. ### Hiding Roadmap from Customers Fear of commitment makes PMs hide roadmap. Outcome-based roadmaps are safe to share (no feature promises). **Action**: Share roadmap in sales calls, customer updates. Builds trust. ### Not Updating as You Learn Roadmap based on assumptions. When assumptions invalidate, update themes. **Example**: "Mobile Access" theme. After testing, learn mobile isn't priority—pivot theme. ## 2025 Roadmap Challenges Modern pressures on roadmapping: - **AI disruption**: Themes must account for rapid AI capability shifts - **Lean constraints**: Smaller teams require ruthless prioritization - **Outcome accountability**: Boards/investors demand measurable results, not feature counts **Response**: Outcome-based roadmaps address all three by forcing strategic focus and measurable impact. ## References - "Product Roadmaps Relaunched" - C. Todd Lombardo, Bruce McCarthy, Evan Ryan, Michael Connors - "Transformed" - Marty Cagan (roadmap as strategic communication) - ProductBoard, ProdPad (outcome-based roadmap tools) ## Related - product-strategy - okr-framework - product-empowerment - dual-track-agile - north-star-framework - opportunity-solution-trees