Outcome Based Roadmap
An outcome-based roadmap commits the team to measurable customer or business outcomes (e.g., 'reduce time-to-first-value from 14 days to 5') instead of features (e.g., 'ship onboarding wizard v2'). Marty Cagan and Teresa Torres both push outcome roadmaps as the only honest format because features are an answer to a hypothesis, not a commitment. Outcome roadmaps free the team to discover the right solution while still committing to results. The catch: outcome roadmaps require executive air cover. The moment a CEO asks 'so when are you shipping the wizard?' and the PM doesn't have backing to say 'we're committing to time-to-value, not the wizard,' the roadmap collapses back to a feature list. Outcome roadmaps are political artifacts as much as planning artifacts.
The Trap
The trap is adopting outcome language while still operating on feature commitments. Teams write 'Increase activation 20%' on the roadmap, then immediately have a Q3 commitment to ship 5 specific features 'in service of' that outcome. When the features ship and the outcome doesn't move, no one is accountable because the team 'did what was on the roadmap.' This is outcome theater. Real outcome roadmaps lack feature commitments by design — that's the point.
What to Do
List 3–5 outcomes per quarter, each with a baseline, target, and owner. Do NOT list features. In the 'how' column, list the discovery activities and bets being explored, with explicit kill criteria. Brief executives on the format change before the first review — and rehearse the response to 'where's the feature list?' Set a calendar reminder for week 6 of the quarter to review whether the team is making outcome progress vs. activity progress; the difference is where outcome roadmaps die.
In Practice
At Atlassian, several internal teams shifted to outcome-based quarterly cadence under the 'Goal Cadence' framework. Teams committed to outcomes like 'reduce setup time for new Jira projects' rather than 'ship the new project wizard.' The shift required CEO Mike Cannon-Brookes to publicly back the format in all-hands meetings — without that air cover, the first quarter's outcome commitments would have been overridden by feature requests from sales. Source: Atlassian Team Playbook, 'Goals, Signals, and Measures.'
Pro Tips
- 01
Marty Cagan: 'If your roadmap has features and dates, you have a release plan, not a roadmap. A real roadmap commits to outcomes the customer will experience.'
- 02
Pre-negotiate with sales and marketing. Outcome roadmaps break their commit-by-date workflows. The fix: a separate 'launch readiness' artifact for sales/marketing that gets created as features approach ship-readiness — not at the start of the quarter.
- 03
Add 'no commit' explicitly. For some outcomes, you're committing to discovery, not delivery. Saying so up front prevents the executive 'where's the feature?' moment from becoming a credibility crisis.
Myth vs Reality
Myth
“Outcome roadmaps mean no dates”
Reality
Outcome roadmaps still have time horizons (typically the quarter or half). What they lack is feature ship dates. The outcome is committed to a quarter; the features that produce it are not pre-committed.
Myth
“Outcome roadmaps are PM-friendly because they remove pressure”
Reality
Outcome roadmaps put MORE pressure on PMs. Shipping 5 features lets you blame execution. Failing to move an outcome leaves no hiding place — your hypotheses were wrong, your discovery was weak, or your prioritization was poor. The format is brutal.
Try it
Run the numbers.
Pressure-test the concept against your own knowledge — answer the challenge or try the live scenario.
Knowledge Check
Your CEO sees the new outcome roadmap and asks, 'where's the feature list?' What's the most disciplined response?
Real-world cases
Companies that lived this.
Verified narratives with the numbers that prove (or break) the concept.
Atlassian
2018–2021
Atlassian's Goal Cadence framework moved several internal product teams to outcome-based quarterly commitments. Teams owned outcomes like 'reduce mean-time-to-resolution for Jira tickets' rather than 'ship the SLA dashboard.' CEO Mike Cannon-Brookes publicly backed the format in company-wide meetings. The teams that adopted it cleanly outperformed teams still on feature roadmaps on their owned outcome metrics by 30–40% over 4 quarters. The teams that adopted it badly (outcome labels, feature commitments) showed no improvement.
Format
Quarterly outcome commitments
Adopted Cleanly — Outcome Lift
30–40% over 4Q
Adopted As Theater — Outcome Lift
≈ 0%
The framework only works with executive air cover. Without the CEO publicly defending the format, the gravitational pull back to feature commitments overwhelms PM discipline.
Hypothetical: A Series B SaaS
2024
A Series B SaaS adopted 'outcome-based roadmaps' under a new VP of Product. Each quarter listed 4 outcomes — but each outcome had a sub-list of 'features in service of this outcome' with ship dates. Sales used the sub-list as the real roadmap. When outcomes weren't hit at quarter-end, the team pointed at shipped features ('we did what was promised'). Three quarters in, the format was indistinguishable from a feature roadmap with extra labels. The VP of Product left.
Stated Format
Outcome-based
Actual Format
Feature roadmap with outcome labels
Outcomes Hit (3 quarters)
2 of 12
Outcome roadmaps without removing feature commitments are theater. The discipline is what's NOT on the page, not what's added to it.
Decision scenario
Defending the Outcome Format
You are the new VP of Product. You've replaced a feature-based quarterly roadmap with an outcome-based one. The first quarterly review is in 2 weeks. The CEO has not yet seen the new format. The Head of Sales has already asked when the 'new onboarding wizard' will ship — a feature that was on the prior roadmap.
Roadmap Format
Outcomes (4 per Q)
Executive Buy-In
Implicit, not explicit
Sales Commitment Pressure
High (3 customers expecting wizard)
Decision 1
You have 2 weeks. The first quarterly review will set the precedent. Your VP of Engineering is supportive. Sales is skeptical. The CEO is busy and has not engaged.
Add a feature appendix to the new roadmap to satisfy sales, present cleanly to the CEO, and hope the format holds over timeReveal
Get a 30-min CEO meeting BEFORE the review. Walk through why the format exists, the 3 questions execs will ask, and the answers. Request explicit air cover in the review. Then handle sales separately with a 'launch readiness' artifact created as features near ship.✓ OptimalReveal
Related concepts
Keep connecting.
The concepts that orbit this one — each one sharpens the others.
Beyond the concept
Turn Outcome Based Roadmap into a live operating decision.
Use this concept as the framing layer, then move into a diagnostic if it maps directly to a current bottleneck.
Typical response time: 24h · No retainer required
Turn Outcome Based Roadmap into a live operating decision.
Use Outcome Based Roadmap as the framing layer, then move into diagnostics or advisory if this maps directly to a current business bottleneck.