What it is
A structured, falsifiable statement of a belief and the outcome you expect if it is true, typically “We believe [change] will result in [outcome], and we will know when [signal].” It turns an opinion into something you can test.
When to use it
During Initiate and Ideate, whenever the team is about to invest in an idea whose value is uncertain.
Why (value)
Forces clarity about what you believe and what evidence would change your mind. Enables cheap experiments before expensive builds.
How to run it
- Surface the belief driving a proposed solution.
- Rewrite it as: we believe X will cause Y, measured by Z.
- Define the smallest test that could disprove it.
- Run the test and compare results against the predicted signal.
- Persevere, pivot, or drop based on evidence.
Inputs and outputs
- Inputs: Assumptions, a proposed change, a measurable signal.
- Outputs: Testable hypotheses with defined success signals and next experiments.
Time and effort
Low to write; the cost is in the experiments that follow.
Evidence and limitations
A hypothesis is a claim, not proof. Its value comes from the test that follows; an untested hypothesis carries no evidentiary weight. Match the test’s evidence type (direct-user vs. proxy) to the decision at stake. See Evidence and limitations.
Tips and pitfalls
- Make it falsifiable, if nothing could disprove it, it is not a hypothesis.
- Define the measurable signal before running the test.
- Do not treat a plausible hypothesis as validated.
Variations
Assumption-to-hypothesis mapping, experiment cards, riskiest-assumption tests.
Related methods
Need help choosing and applying a method?
Gumshoe helps teams connect research, collaborative workshops and service design to the decisions they need to make.
Sources and further reading
- UX Tigers, “100 UX methods.”
- 18F Methods (US government, public domain).
Explore related methods
- Assumption mapping — Surface the beliefs a plan depends on and sort them by risk so you test the scariest ones first.
- Design hypothesis — Pair a proposed design change with the user outcome you expect, so the design itself becomes testable.
- Concept testing — Put an early idea in front of users to gauge value and comprehension before building it.
