methodatlas
Session Builder

Plan my session

Plan a concrete work block with agenda, roles, preparation, and a copyable result artifact.

Method session1-2 h initial, then 30-60 min weeklyWorkshop or asyncOpportunity Solution Tree

Session: Opportunity Solution Tree

The plan translates the method into a concrete facilitated work block. Your inputs flow directly into the session brief and work artifact.

Derived automatically

Method session with 2-6. The plan uses the existing method logic and the runsheet.

Runsheet
Participation logic
Team round, shared work and alignment

Use the session for shared understanding. Contributions are collected visibly, assumptions are aligned, and open differences remain traceable in the artifact.

Outcome logic
Finish artifact

The session works directly toward Opportunity Solution Tree. After the session, the artifact should be shareable, reviewable, or reusable.

  1. 1

    Phase 1: Outcome anchor

    10 min

    Place the outcome at top of tree as a clear measurable statement with baseline and target. Make time window explicit (for example, next 12 weeks). Hint: Outcome must be a user or business metric, not an output ("launch feature X"). A wrong outcome creates wrong opportunities.

    FacilitatorOpportunity Solution Tree
  2. 2

    Phase 2: Opportunities from interview data

    30-45 min

    Distill customer needs, pain points, and desires from interview highlights. Phrase each opportunity as a user-view sentence ("I want ... so that ..."). De-duplicate and cluster into 3-5 lanes. Hint: Opportunities are not solutions. "Faster checkout" is solution language, "I lose trust when checkout takes too long" is opportunity language.

    FacilitatorExperiment Backlog
  3. 3

    Phase 3: Pick one opportunity

    10 min

    Team selects ONE opportunity to deepen. Selection criteria: outcome impact, number of mentions in interviews, addressability. Hint: Focusing on more than one at a time fragments focus. The tree grows over time, not in one session.

    FacilitatorLearning Log
  4. 4

    Phase 4: Diverge solutions

    20-30 min

    For each selected opportunity, collect 3-5 solutions. First divergent ideation (including outlandish ideas), then convergence. Keep solutions short as actions ("inline validation," "hide optional fields"). Hint: If only one solution appears, team bias is too strong. Force at least three solutions, otherwise the best option is missed.

    FacilitatorOpportunity Solution Tree
  5. 5

    Phase 5: Experiments under solutions

    20-30 min

    Define at least one experiment per solution that tests the riskiest assumption. For each experiment: hypothesis, method, success criterion, estimated effort, owner. Hint: An experiment is not "build the solution and watch." It is a targeted assumption test (prototype test, fake door, interview). Otherwise it is delivery.

    OwnerExperiment Backlog
  6. 6

    Publish artifact

    10 min

    Check the artifact for completeness, define location, set version or status, and name review recipients.

    OwnerOpportunity Solution Tree
Usable artifact

Session Brief

For invitations, boards, tickets, PR descriptions, or workshop notes.

session-brief.md

Session Brief: Opportunity Solution Tree

Goal

Artifact: Opportunity Solution Tree

Working Question

Which opportunity should the team address next with which solution, and which experiment provides the next learning signal?

Context

Current outcome with target value and baseline; raw interview notes or highlights from recent interviews; existing solutions/features in backlog; learning status from ongoing experiments.

Setup

  • Format: Method session
  • Duration: 1-2 h initial, then 30-60 min weekly
  • Mode: Workshop or async
  • Participants: Product trio (Product Manager, Designer, Engineering Lead) as core; optional researcher; one owner for the tree, updated across sessions.
  • Owner: Product trio (Product Manager, Designer, Engineering Lead) as core
  • Participation mode: Team round, shared work and alignment
  • Outcome logic: Finish artifact

Participation Logic

Use the session for shared understanding. Contributions are collected visibly, assumptions are aligned, and open differences remain traceable in the artifact.

Outcome Logic

The session works directly toward Opportunity Solution Tree. After the session, the artifact should be shareable, reviewable, or reusable.

Input

Visual board (Miro, FigJam, Mural) with hierarchical tree structure; sticky note colors for outcome (top), opportunities (middle), solutions (bottom), experiments (floor); link to interview data repository.

Preparation

Set outcome at the top of the tree and make it bold. Prepare three to five opportunity lanes. Define sticky-note convention. Set tree owner and review cadence (for example Tuesday weekly).

Agenda

  1. Phase 1: Outcome anchor (10 min) Owner: Facilitator Action: Place the outcome at top of tree as a clear measurable statement with baseline and target. Make time window explicit (for example, next 12 weeks). Hint: Outcome must be a user or business metric, not an output ("launch feature X"). A wrong outcome creates wrong opportunities. Output: Opportunity Solution Tree

  2. Phase 2: Opportunities from interview data (30-45 min) Owner: Facilitator Action: Distill customer needs, pain points, and desires from interview highlights. Phrase each opportunity as a user-view sentence ("I want ... so that ..."). De-duplicate and cluster into 3-5 lanes. Hint: Opportunities are not solutions. "Faster checkout" is solution language, "I lose trust when checkout takes too long" is opportunity language. Output: Experiment Backlog

  3. Phase 3: Pick one opportunity (10 min) Owner: Facilitator Action: Team selects ONE opportunity to deepen. Selection criteria: outcome impact, number of mentions in interviews, addressability. Hint: Focusing on more than one at a time fragments focus. The tree grows over time, not in one session. Output: Learning Log

  4. Phase 4: Diverge solutions (20-30 min) Owner: Facilitator Action: For each selected opportunity, collect 3-5 solutions. First divergent ideation (including outlandish ideas), then convergence. Keep solutions short as actions ("inline validation," "hide optional fields"). Hint: If only one solution appears, team bias is too strong. Force at least three solutions, otherwise the best option is missed. Output: Opportunity Solution Tree

  5. Phase 5: Experiments under solutions (20-30 min) Owner: Owner Action: Define at least one experiment per solution that tests the riskiest assumption. For each experiment: hypothesis, method, success criterion, estimated effort, owner. Hint: An experiment is not "build the solution and watch." It is a targeted assumption test (prototype test, fake door, interview). Otherwise it is delivery. Output: Experiment Backlog

  6. Publish artifact (10 min) Owner: Owner Action: Check the artifact for completeness, define location, set version or status, and name review recipients. Output: Opportunity Solution Tree

Closeout

  • Update result artifact: Opportunity Solution Tree
  • Define location, version, and review recipients.
  • Define owner, next step, and review date.
Usable artifact

Work artifact

Pre-filled starting point based on the matching template.

work-artifact.md

Opportunity Solution Tree: Opportunity Solution Tree

Working Question

Which opportunity should the team address next with which solution, and which experiment provides the next learning signal?

Context

Current outcome with target value and baseline; raw interview notes or highlights from recent interviews; existing solutions/features in backlog; learning status from ongoing experiments.

Participants

  • Owner: Product trio (Product Manager, Designer, Engineering Lead) as core
  • Participants: Product trio (Product Manager, Designer, Engineering Lead) as core; optional researcher; one owner for the tree, updated across sessions.

Input

Visual board (Miro, FigJam, Mural) with hierarchical tree structure; sticky note colors for outcome (top), opportunities (middle), solutions (bottom), experiments (floor); link to interview data repository.

Template

Outcome

  • Measurable result:

Opportunities

  • Opportunity 1:
  • Opportunity 2:
  • Opportunity 3:

Solutions

  • Solution idea per opportunity:

Experiments

  • Test:
  • Success criterion:
  • Owner:
  • Date:

Completion Check

  • Opportunity Solution Tree is complete enough for review:
  • Location:
  • Version / status:
  • Review by:
  • Next step:

Next Step

  • Review result
  • Mark open questions
  • Schedule review or decision
Template base

Opportunity Solution Tree Outline

View templateStructure for outcome, opportunities, solutions, and experiments.
canvas

opportunity-solution-tree-outline.md

Structure for outcome, opportunities, solutions, and experiments.

Outcome

  • Measurable result:

Opportunities

  • Opportunity 1:
  • Opportunity 2:
  • Opportunity 3:

Solutions

  • Solution idea per opportunity:

Experiments

  • Test:
  • Success criterion:
  • Owner:
  • Date:
Ready to use when
  • Working question, owner, and target artifact are visible.
  • The result fits Opportunity Solution Tree.
  • Tree is a living document; take monthly snapshots as photo export for history. Mark discarded opportunities and solutions as "discarded because ...", rather than deleting them. This prevents repeated debates.
  • Open questions are noted as follow-ups.
  • The next review or decision point is scheduled.
ProfileRunsheet