Outcome Discovery Canvas: Validate the Outcome Before the Roadmap
The Outcome Discovery Canvas helps you test whether a user outcome and a business outcome are worth pursuing before you put them on a roadmap. It is a validation structure, not a delivery plan. A finished canvas can conclude go, reshape, or stop.
Framework Card
- Name:
- Outcome Discovery Canvas
- Goal:
- Validate a user outcome and a business outcome with evidence before committing a roadmap, so teams do not sequence solutions for an untested result.
- Flow:
- External opportunity signals → Users and customers → Current versus future state → Risk of inaction → User and business outcomes → Checkable goals → Strategic move
- Best For:
- Screening an initiative before roadmap commitment; Aligning stakeholders on what success would mean; Catching solution bias before development starts
Why it matters
Teams often lock a solution because a stakeholder asked for a feature. Months later, usage is low and nobody can say what was supposed to change for users or for the business.
That failure started before the sprint. The outcome was never tested.
The Outcome Discovery Canvas is a way to put opportunity evidence, users, current versus future state, risk of inaction, and paired outcomes on one page before sequencing work. It does not guarantee that validated work will succeed. It does make an untested outcome harder to hide.
What it is
The Outcome Discovery Canvas is a pre-roadmap structure. A usable pass covers:
- External opportunity signals. Evidence that something is happening, not a slogan.
- Users and customers. Who, specifically enough to be wrong.
- Current versus future state. What would actually change.
- Risk of inaction. Customer and business cost of waiting.
- User outcome and business outcome. Both named, both measurable enough to check.
- Checkable goals. Wording tight enough to test (SMART is a quality bar, not a second canvas).
- Strategic move. What you will do next if this is worth it, including not proceeding.
This canvas is not the Outcome-Based Roadmap. Discovery chooses whether an outcome deserves a slot. The roadmap sequences outcomes that already do.
How it works
A useful canvas can fail. If every section points to "build it," look again.
1. Evidence the opportunity and the user
Write signals from the case (behavior, demand, constraint) and name the user. Vague "users" cannot be falsified.
2. Contrast current and future state; name risk of inaction
State what is true now, what would be true later, and what is lost if you wait. Empty risk language is not a case.
3. Pair user and business outcomes
One change in user behavior or situation, one business result that depends on it. A business metric with no user change, or a user wish with no business reason, is a hole.
4. Make goals checkable and state the move
Tighten wording until you would know if you were wrong. Then choose go, reshape, or stop. Discovery that cannot stop is not discovery.
How it compares
When another lens fits better, or when you need a complementary view, these frameworks do different jobs. They are not interchangeable labels for the same question.
| Framework | What it helps you see | How it differs from ODC |
|---|---|---|
| Outcome-Based Roadmap | How to sequence outcomes over time | Planning horizon after validation |
| Business Model Canvas | How the business creates and captures value | Whole-model mechanics, not initiative validation |
| OKR | Objectives and key results for a cycle | Goal system, not a discovery canvas |
| SMART Goal Framework | Whether a goal is specific and checkable | Wording quality, one part of the canvas |
| Lean Canvas | Problem, solution, and model hypotheses for a startup | Broader model canvas, not this seven-part outcome test |
The Outcome Discovery Canvas is the lens for testing whether an outcome deserves a roadmap slot. Other methods help when the question is sequencing, a business model, or a goal cycle.
When to Use This Framework
- Screening an initiative before roadmap commitment. A feature request needs a testable result first.
- Aligning stakeholders on what success would mean. Rooms disagree because "done" still means "shipped."
- Catching solution bias in a kickoff. The how is already chosen and the why is still a paragraph.
Example
A concrete example makes the structure easier to reuse when you are under uncertainty.
Example: Feature that dies on the canvas
A product team wants an in-app social feed because a competitor launched one.
Opportunity signals: competitor PR, not user behavior. Users: "everyone." Current versus future: more time in app, unmeasured. Risk of inaction: "we will look behind." User outcome: unclear. Business outcome: "engagement."
Implication: The canvas should stop or reshape, not sequence a feed. There is no evidenced user change and no checkable business result. That is a successful use of the method.
Example: Activation outcome that can proceed
A B2B team sees new orgs stall after invite. Support tickets name one setup field. Future state: org admin finishes setup without a ticket. Risk of inaction: trial-to-paid stays flat. User outcome: more orgs complete setup in seven days. Business outcome: more trials convert to paid among completers. Move: a setup experiment, then an outcome-based timebox if the signal holds.
Implication: The canvas supports a go on a narrow outcome. It still does not design the sprint.
Takeaway
What the Outcome Discovery Canvas can help with
- Testing whether an outcome is worth a roadmap slot
- Pairing user change with business result
- Making stop or reshape a legitimate output
- Aligning a kickoff on success before solution lock
What the Outcome Discovery Canvas cannot replace
- Outcome-Based Roadmap. OBR sequences already-chosen outcomes over time.
- Business Model Canvas. BMC maps how the whole business creates and captures value.
- OKR. A goal cycle, not a seven-part validation canvas.
- A delivery plan. Sprints, estimates, and tracking.
- Jobs-to-be-done interviews as a full research method. Related cousin for customer jobs. This canvas is not a substitute for research.
Honest scope: the canvas structures pre-roadmap validation. It does not replace sequencing, a business model, or execution.
Frequently asked questions
It is designed for before commitment. You can still fill it retrospectively to see what was never tested, but that is an audit, not discovery.
Evidence, a specific user, current versus future state, risk of inaction, paired outcomes, checkable goals, and a go / reshape / stop. If the output cannot stop, you do not have discovery yet.
If the canvas says go, the roadmap can timebox that outcome with flexible solutions. If it says stop, nothing is sequenced.
You need checkable wording. SMART is one quality bar. It is not a replacement for the rest of the canvas.
No. A revenue target with no user change is a hole. Pair them.