- Home
- Workshop Tactics
- Hypothesis Statement
Hypothesis Statement
Table of contents
What is Hypothesis Statement?
Hypothesis Statement is a card from the Workshop Tactics deck by Pip Decks.
Take the subjective and political conversation out of the decision-making process, and focus the team towards feedback from users and customers.
Before, collect and prioritise your assumptions with Assumption Collecting and Assumption Map. Afterwards, create a Prototype Persona to give you direction on who to test with.
When to use Hypothesis Statement
- Uncertainty about product-market fit
- High levels of internal debate without resolution
- Need to prioritize features or ideas
- Desire to shift from opinion-based to evidence-based decisions
- Frequent project pivots without clear direction
- Lack of user feedback in decision-making
- Pressure to innovate quickly with limited resources
How to use Hypothesis Statement
-
As a group, put your riskiest and most unproven assumptions into this hypothesis template:
Because we saw **[quantitative/qualitative insight]**,_ we believe [this assumption statement is true]._
We will know we’re **[right/wrong]** when we see the following feedback:
**[Qualitative feedback]** and/or **[quantitative feedback]** and/or **[key performance indicator change]**.
-
Your hypothesis may be too big to test with a single statement, so it can be helpful to use this format to break it down into smaller parts:
We believe that **[doing this/building this feature/creating this experience]** for **[these people/personas]** will achieve **[this outcome]**.
We will know this is true when we see **[this market feedback, quantitative measure, or qualitative insight]**.
-
As a group, Secret Vote on the hypotheses you’d like to commit to.
