Product validation workshop worksheet
Plan a test that could change your mind about a proposed solution. This is an experiment planning tool, not evidence that your idea has been validated.
Print or save as PDF Read the workshop guide
The writing lines are real borders, so they appear in print even if browser background graphics are disabled.
Worked example: testing a setup assistant Illustrative experiment plan, not test results. Proposed solution: a guided setup assistant. Risky assumption: it makes account connection easier to understand. Test: compare a clickable assistant prototype with the existing flow in moderated task sessions. Predefine evidence: observe completion, hesitation, comprehension of requested permissions and any new confusion. Decision: revise or stop the concept if participants still misunderstand the connection or if the assistant introduces new friction.
Use the blank form below for your own hypothesis and decision criteria.
1. Frame the customer problem and proposed solution Who is the customer, and what problem is supported by evidence?
Proposed solution, desired outcome and decision boundary
Facilitator, team, decision owner and date
2. List solution assumptions that must be true Think about desirability, usability, feasibility and viability. Record facts separately from beliefs.
Critical assumption Category Evidence we already have Consequence if false
3. Select the riskiest assumption The assumption with the highest consequence and weakest relevant evidence
Why this is the next assumption worth testing
4. Write a falsifiable hypothesis We believe that, for these people, this solution will cause this observable change
Evidence that would make us reject or revise the belief
5. Design the experiment Experiment method and why it addresses this assumption
Who participates, what they do, and the realistic context
Primary measures, confounders and comparison where appropriate
Safety, accessibility, privacy, consent and disclosure safeguards
6. Predefine evidence and next decisions Evidence threshold or pattern we would consider useful
What would lead us to continue, revise or stop?
Experiment owner, recruiting or setup tasks, deadline and review date
7. Record results after running the experiment What actually happened, sample details and limitations
Decision and next learning question
Where the research evidence and experiment log are saved