The Test Card turns a critical assumption into a testable claim and specifies in advance which result counts as success.
Product Discovery Canvas
Test Card
Condenses one critical assumption into a testable plan with a clear metric and a success threshold set in advance.
The Test Card is a compact planning artefact for one test. It connects hypothesis, test, metric, and success threshold before execution. This lets the team later determine whether the evidence sufficiently supports the assumption or calls for another learning step.
How will we test this critical assumption with a clear test, a suitable metric, and a success threshold set in advance?
- Participants
- 1-5
- Time
- 20-35 min
Complete and freeze the four fields before execution. Record observations and conclusions in the Learning Card.

Hypothesis
State the critical assumption
Define one specific, falsifiable claim that matters to the next decision.
Test
Choose the smallest meaningful test
Design a responsible procedure that produces evidence specifically for the hypothesis.
Metric
Define the observable signal
Specify which observation or calculation counts as evidence and how it will be captured.
Success threshold
Set the threshold in advance
Define a quantitative or clearly observable boundary at which the result is considered sufficient.
Create a new version for each new hypothesis or materially changed test setup. Evaluate results in a Learning Card after execution.
A good fit when
Useful when a prioritized assumption should be checked with a contained test. Use an Experiment Canvas for broader planning with guardrails, data basis, and decision logic.
Ideal for
- Business model assumptions
- Compact experiment planning
Not good for
- Tests without measurable observations
Outputs

Completed Test Card
A versioned plan with hypothesis, test, metric, and a success threshold set in advance.
Test Card
Fictional worked example
Four fields connect one critical assumption to a test, metric, and success threshold before execution.
Hypothesis
What must be true for the idea?
Project leads activate a weekly risk report when setup takes no more than two minutes.
Test
How will we test the hypothesis?
40 active project leads see a clickable setup dialogue for seven days.
Metric
Which observation counts as evidence?
Share of exposed project leads who complete the setup.
Success threshold
Which boundary applies before launch?
At least 12 completions from 40 valid exposures; stop after one privacy complaint.
First step
Start with a prioritized assumption whose support or rejection affects a concrete product or business decision.
Good to do first
Deep dive
State one hypothesis, select an appropriate test, define the measurement, and set a success threshold before starting.
Four fields connect the assumption to an observable test. Specify the audience, measurement window, numerator, and denominator to make the metric precise. Keep the threshold unchanged during execution. An Experiment Canvas can hold the same information with additional constraints for more complex setups.
Work on one hypothesis per card and review whether it can be measured. Card preparation and test execution have separate time budgets. Reference an existing Experiment Canvas when it already contains the four planning fields.
The method guide walks execution through 4 phases, timing, 4 pitfalls, and clear stop criteria.
Open method guideYour perspective
Does this method help with your work?
Your feedback helps shape the next improvements to methodatlas.
Sources and topics
Test Card: WorksheetPlan one decision-relevant test in a compact session. Execution and evaluation receive separate dates and artefacts.canvas
test-card-working-template.md
Plan one decision-relevant test in a compact session. Execution and evaluation receive separate dates and artefacts.
Test Card: Worksheet
Question
To be confirmed
Desired outcome
To be confirmed
Scope
Complete Test Card Time: 20 to 35 minutes
Complete this worksheet on paper or in your own document during the work.
Preparation for this scope
Method setup
- Materials: Test Card, prioritized assumption, available baseline, audience access, and information about privacy, ethics, and operational risks.
- Roles: Test owner · Product · Research or Analytics · privacy or risk expert where needed
- Advance information: Prepare the prioritized assumption, upcoming decision, available audience, known baseline, and relevant safeguard boundaries.
- Overall time needed: 20 to 35 minutes for planning; execution is separate
- Setup: Arrange the four fields visibly. Work through hypothesis, test, metric, and success threshold in that order, then freeze the card before launch.
Prepare for the work steps
Hypothesis: State the critical assumption
- Prioritized assumption
- Product or business model context
- Upcoming decision
Test: Choose the smallest meaningful test
- Testable hypothesis
- Access to the audience or test environment
- Time, cost, privacy, and risk constraints
Metric: Define the observable signal
- Hypothesis and test procedure
- Available data source
- Relevant observation window
Success threshold: Set the threshold in advance
- Defined metric
- Baseline or justified reference value
- Consequence of the later decision
Test Card
Hypothesis
What must be true for the idea?
...
Test
How will we test the hypothesis?
...
Metric
Which observation counts as evidence?
...
Success threshold
Which boundary applies before launch?
...
Strategyzer: Validate Your Ideas with the Test Card
Hypothesis: State the critical assumption
Expected artifact: Testable hypothesis
Audience · expected behaviour · context
Entry:
...
- Can an observable result clearly weaken the claim?
Test: Choose the smallest meaningful test
Expected artifact: Executable test
Participants · intervention · procedure · duration · safeguards
Entry:
...
- Does the test produce evidence that directly fits the hypothesis?
Metric: Define the observable signal
Expected artifact: Unambiguous metric
Signal · data source · calculation · window
Entry:
...
- Can two people derive the same value from the same raw data?
Success threshold: Set the threshold in advance
Expected artifact: Pre-set success threshold
Boundary · minimum data · pause and stop limits
Entry:
...
- Can the team determine whether the threshold was met without introducing a new interpretation?
Open questions and next steps
...
Method guide: https://methodatlas.meierhoff-systems.de/en/methods/test-card/run-sheet
Alternatives and neighbors
Fitting alternatives with decision guidance, followed by other related methods.

Choose Experiment Canvas for additional decision, risk, data capture, and evaluation fields. Maintain the four test planning fields there once.

Moves customer problem, solution idea, and evidence toward a concrete result through "take over the hypothesis list", "define the risk scale", and "select the top hypotheses for the next tests".

Moves customer problem, solution idea, and evidence toward a concrete result through "list assumptions", "map assumptions to dimensions", and "derive the test plan".

Moves customer problem, solution idea, and evidence toward a concrete result through "collect assumptions explicitly", "rate uncertainty and leverage for each assumption", and "decide to pivot, persevere, or stop".

Separates discovery and delivery so that validated stories only move into implementation after learning loops.

Aligns business problem, users, outcomes, solution ideas, hypotheses, and experiments on one lightweight canvas.
Constraints and origin
Profile
- Method form
- Canvas
- Participants
- 1-5
- Time
- 20-35 min
- Maturity
- Established
- Origin
- Strategyzer


