outcome-roadmap

# Outcome Roadmap — from features to results Converts a feature-focused roadmap into an outcome-focused one. **Core principle:** Teams build features, but customers and businesses care about outcomes. An outcome roadmap communicates WHAT CHANGES, not what gets built. --- ## The transformation formula For every initiative on the roadmap, apply: ``` Enable [customer segment] to [desired customer outcome] so that [business impact] ``` Examples: | Output (old) | Outcome (new) | |---|---| | Q2: Build advanced search filters | Q2: Enable customers to find products 50% faster through intuitive discovery | | Q2: AI recommendations | Q2: Increase average order value 20% through personalised recommendations | | Q3: Dashboard redesign | Q3: Help operators monitor all systems with 80% less time spent on dashboards | | Q3: SSO integration | Q3: Remove auth friction for enterprise admins so we can close 3+ enterprise deals | | Q4: Mobile app | Q4: Enable users to complete core workflows on mobile so 7-day retention increases from 20% to 35% | --- ## How to apply ### Step 1 — Read the existing roadmap If the user provides a roadmap file, read it. If they describe it verbally, extract the initiative list. For each initiative, ask internally: - What feature / project is planned? - **Why** are we building it? What changes for customers or the business? - What metric will improve, and by how much? - Is there a better, different way to achieve the same outcome? ### Step 2 — Rewrite...