Skip to content
BENIBIX Learn

Design Hypothesis

Design🚀 Product DevelopmentDesign Validation

Also known as Hypothesis Statement, UX Hypothesis

A written guess about a design change and what result would prove it. It is made to be tested.

Think of it like

It is like guessing which paper plane will fly the farthest. Then you throw them all to see.

Example

Leo writes: we believe a progress bar on sign-up will help new users finish. We will know when sign-ups rise by 10%.

Why it matters

Without a clear guess, any result can be read as success. A hypothesis says up front what winning looks like.

Definition

A design hypothesis is a guess a team writes down to test. It names the change, who it is for and what result would prove it right. A common form is: we believe this change for these people will lead to this result. We will know when we see this sign. Writing it first keeps the team honest when the results come in.
The guess is written down in the think step, before anything is built.

Common mistake

Writing a guess with no way to measure it, like users will love it. If you cannot check it, you cannot learn from it.

Key takeaways

  1. 1
    Change, people, result. Name all three.
  2. 2
    Say how you will know. A sign you can measure.
  3. 3
    Write it first. Before the results come in.