An Outcome-Based Roadmap organises work around desired customer and business outcomes rather than a feature list. Instead of 'build X by Q3', it frames work as 'achieve outcome Y — and we currently believe X is the best way to do that.'

For mature product teams that have moved beyond 'shipping features' to 'delivering value.' Especially effective in continuous discovery environments.

1. Define the outcomes you want to achieve — for the customer and for the business
2. Articulate why each outcome matters and how you'll measure it
3. List your current best hypotheses for how to achieve each outcome
4. These hypotheses — not features — become the roadmap items
5. Track whether shipped items actually achieved their intended outcome
6. Replace items that don't achieve outcomes with better hypotheses

• Using outcome language without genuinely measuring whether outcomes are achieved
• Stakeholders reverting to feature requests — requires ongoing education
• Not defining upfront how you will measure whether an outcome has been achieved

• Lean UX — Jeff Gothelf & Josh Seiden
• Continuous Discovery Habits — Teresa Torres