What it is
A statement linking a specific design decision to an expected, observable change in user behavior or outcome, used to keep design intentional and evaluable. 18F frames it as connecting a problem, a proposed solution, and the result you predict.
When to use it
During Initiate and Ideate, as you commit to a design direction you will later evaluate.
Why (value)
Keeps design decisions purposeful and accountable, and sets up a clear yardstick for whether the design worked.
How to run it
- State the user problem you are addressing.
- Describe the design change you propose.
- Predict the observable outcome if the design succeeds.
- Define how you will observe that outcome.
- Test and compare against the prediction.
Inputs and outputs
- Inputs: A user problem, a proposed design, a way to observe results.
- Outputs: A testable design hypothesis with a defined success signal.
Time and effort
Low. Minutes to write; cost is in testing.
Evidence and limitations
Like any hypothesis, it holds no evidentiary weight until tested. Choose an evaluation with the right evidence type for the decision. See Evidence and limitations.
Tips and pitfalls
- Tie the change to an observable outcome, not a feeling.
- Keep one hypothesis per decision so results are attributable.
- Do not skip the observation step.
Variations
Lean hypotheses, experiment cards, evidence-based design statements.
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
- 18F Methods (US government, public domain).
Explore related methods
- Lean hypotheses — State beliefs as testable predictions so you can learn quickly instead of debating opinions.
- Assumption mapping — Surface the beliefs a plan depends on and sort them by risk so you test the scariest ones first.
- Concept testing — Put an early idea in front of users to gauge value and comprehension before building it.
