Session Brief: Experiment Canvas

Goal

Artifact: Ausgefülltes Experiment Canvas

Working Question

Which assumption are we testing with which experiment, at what threshold is the hypothesis confirmed, and what decision follows from the result?

Context

Assumption list; known customer or user-segment data; available test tools (landing page, fake-door, prototype); budget and timeframe; existing analytics metrics.

Setup

• Format: Method session
• Duration: 30-60 min
• Mode: Workshop or async
• Participants: A Discovery lead or Product Manager as canvas owner; a designer for test setup; an engineer for technical feasibility; optionally a Data Analyst for metrics sources.
• Owner: A Discovery lead or Product Manager as canvas owner
• 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 Ausgefülltes Experiment Canvas. After the session, the artifact should be shareable, reviewable, or reusable.

Input

Canvas template (Strategyzer, Lean UX, or custom); pens and stickies; shared document or Miro board; list of assumptions to test; examples of metrics and thresholds from prior experiments.

Preparation

Use canvas as printout or board. Visible fields: hypothesis, riskiest assumption, test design, metric, success threshold, learning goal, decision rule, prerequisites. Use a previous experiment canvas as reference.

Agenda

1. Section 1: Learning goal and assumption (10 min) Owner: Facilitator Action: Formulate learning goal as a question ("Do we want users to buy Feature X?"). Name the riskiest assumption behind it. Fill both fields. Hint: If the learning goal is stated as "we want to build feature," it is an implementation intent, not a learning goal. The canvas is the wrong tool; use roadmap item instead. Output: Ausgefülltes Experiment Canvas

2. Section 2: Hypothesis and success metric (10 min) Owner: Facilitator Action: Write hypothesis as an if-then statement. Name success metric with source (analytics tool, survey, manual analysis). Define success threshold. Hint: A hypothesis without threshold is wishful thinking. Set threshold before test, not after. Without source, a metric is not measurable. Output: Erfolgsmetrik

3. Section 3: Test design and setup (15 min) Owner: Facilitator Action: Choose test type (landing page, fake-door, prototype, concierge, Wizard of Oz). Describe setup: what is built, target group, distribution. Estimate effort and duration. Hint: Prefer smallest working test. If a prototype is built where a landing page is enough, time is wasted. Effort should match assumption size. Output: Ausgefülltes Experiment Canvas

4. Section 4: Decision rule (10 min) Owner: Facilitator Action: Define before test: what happens on success, what on failure. Options: Pivot, Persevere, Stop, next experiment. List risks and prerequisites. Hint: Without a decision rule, results are interpreted instead of applied. Define success and failure path before test, this is methodological protection. Output: Erfolgsmetrik

5. Section 5: Review and approval (5-10 min) Owner: Owner Action: Align canvas with stakeholder or sponsor. Confirm budget and owner. Set test start date. Hint: If a sponsor does not accept threshold, clarify beforehand. Threshold changes after the test start devalue the experiment. Output: Ausgefülltes Experiment Canvas

6. Publish artifact (10 min) Owner: Owner Action: Check the artifact for completeness, define location, set version or status, and name review recipients. Output: Ausgefülltes Experiment Canvas

Closeout

• Update result artifact: Ausgefülltes Experiment Canvas
• Define location, version, and review recipients.
• Define owner, next step, and review date.

Ausgefülltes Experiment Canvas: Experiment Canvas

Working Question

Which assumption are we testing with which experiment, at what threshold is the hypothesis confirmed, and what decision follows from the result?

Context

Assumption list; known customer or user-segment data; available test tools (landing page, fake-door, prototype); budget and timeframe; existing analytics metrics.

Participants

• Owner: A Discovery lead or Product Manager as canvas owner
• Participants: A Discovery lead or Product Manager as canvas owner; a designer for test setup; an engineer for technical feasibility; optionally a Data Analyst for metrics sources.

Input

Canvas template (Strategyzer, Lean UX, or custom); pens and stickies; shared document or Miro board; list of assumptions to test; examples of metrics and thresholds from prior experiments.

Template

Experiment 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

• Filled Experiment Canvas:
• Success metric:

Open questions

• ...

Next step

Owner, date, success signal.

Completion Check

• Ausgefülltes Experiment Canvas is complete enough for review:
• Location:
• Version / status:
• Review by:
• Next step:

Next Step

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