Session Brief: Hypothesis Prioritization Canvas

Goal

Artifact: Priorisierungs-Canvas

Working Question

Which hypotheses combine high risk, low evidence, and low testing effort, and which of them should be tested in the next iterations?

Context

Hypothesis list distributed 1-2 days before; scale definitions (risk 1-5, evidence 1-5, effort 1-5); existing evidence from analytics, interviews, or prior tests; test tool options with rough effort estimates.

Setup

• Format: Method session
• Duration: 60-90 min
• Mode: Workshop
• Participants: A facilitator who holds scales and moderates consensus; one Product Lead as hypothesis owner; 3-6 participants from Discovery, Engineering, Design, Data; a scribe for ratings.
• Owner: A facilitator who holds scales and moderates consensus
• 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 Priorisierungs-Canvas. After the session, the artifact should be shareable, reviewable, or reusable.

Input

Canvas with three axes (risk, evidence, effort) or a quadrant; hypothesis list as cards; visible scale definitions; pens; timer; voting tool (Miro, FigJam).

Preparation

Canvas with three axes or quadrants. Scale banners on the wall: risk (consequence if hypothesis is wrong), evidence (degree of support), effort (test cost). Keep hypothesis cards ready.

Agenda

1. Phase 1: Calibrate scales (10 min) Owner: Facilitator Action: Review scale definitions with examples. At least one example per level (for example, "Risk 5: business model at stake without confirmation"). Record consensus. Hint: Without scale calibration, rating falls back to gut feel. If no shared scale definition exists, the team has no baseline for prioritization. Output: Priorisierungs-Canvas

2. Phase 2: Rate hypotheses individually (30-40 min) Owner: Facilitator Action: Assign three values per hypothesis: risk, evidence, effort. Vote anonymously first, then reach consensus. If disagreement occurs, ask for underlying assumptions, do not enforce consensus. Hint: Max 3 min per hypothesis. If discussion is long, document the assumption and park it for follow-up. Hypothesis evaluation is triage, not deep analysis. Output: Hypothesen-Backlog

3. Phase 3: Position on canvas (10 min) Owner: Facilitator Action: Place hypotheses on the canvas. Top-right quadrant: high risk, low evidence, low effort. These are top test candidates. Hint: If top-right is empty, hypotheses are either too generic or tests are too large. Re-scope hypotheses or split tests. Output: Priorisierungs-Canvas

4. Phase 4: Test backlog and owners (10-20 min) Owner: Owner Action: Select the top 3 hypotheses for next tests. Set owner and start date per hypothesis. Document follow-up hypotheses as backlog. Fix pipeline order. Hint: Maximum three parallel tests for small teams. For discovery teams with more than five people, more tests may be possible. Pipeline discipline: do not start everything at once. Output: Hypothesen-Backlog

5. Publish artifact (10 min) Owner: Owner Action: Check the artifact for completeness, define location, set version or status, and name review recipients. Output: Priorisierungs-Canvas

Closeout

• Update result artifact: Priorisierungs-Canvas
• Define location, version, and review recipients.
• Define owner, next step, and review date.

Priorisierungs-Canvas: Hypothesis Prioritization Canvas

Working Question

Which hypotheses combine high risk, low evidence, and low testing effort, and which of them should be tested in the next iterations?

Context

Hypothesis list distributed 1-2 days before; scale definitions (risk 1-5, evidence 1-5, effort 1-5); existing evidence from analytics, interviews, or prior tests; test tool options with rough effort estimates.

Participants

• Owner: A facilitator who holds scales and moderates consensus
• Participants: A facilitator who holds scales and moderates consensus; one Product Lead as hypothesis owner; 3-6 participants from Discovery, Engineering, Design, Data; a scribe for ratings.

Input

Canvas with three axes (risk, evidence, effort) or a quadrant; hypothesis list as cards; visible scale definitions; pens; timer; voting tool (Miro, FigJam).

Template

Hypothesis Prioritization Canvas Canvas

Context

What is this method used for?

Core question

Which question should be answered at the end?

Input

Which data, observations, or materials are available?

Working area

• Area 1:
• Area 2:
• Area 3:
• Relationships / patterns:

Output artifacts

• Prioritization Canvas:
• Hypothesis backlog:

Open questions

• ...

Next step

Owner, date, success signal.

Completion Check

• Priorisierungs-Canvas is complete enough for review:
• Location:
• Version / status:
• Review by:
• Next step:

Next Step

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