Hypothesis
A hypothesis is a written, testable prediction that a specific change will move a specific metric by a specific amount.
What it means
A hypothesis is the sentence you write before you run a test. It names the change you intend to make, the metric you expect it to move, the direction of that movement and the reason you believe it will happen. A usable form is: because we observed X, we believe changing Y will cause Z, measured by this metric.
A hypothesis is not the test itself, and it is not an idea. An idea is "try a shorter product page". A hypothesis commits to an outcome you can be wrong about. People often confuse it with an A/B Test, which is the mechanism that checks the hypothesis, and with a Primary Metric, which is only the measuring part of it.
How it is measured
A hypothesis is not calculated, but the prediction inside it is a number and that number decides your test design. State the expected lift as a relative change to the Primary Metric, then use it as your Minimum Detectable Effect to work out Sample Size. The honest version predicts the smallest lift worth shipping, which needs more traffic. The flattering version predicts a large lift, which lets you stop early and call almost any wobble a win. Write the number down before the test starts, not after.
A Shopify example
For A Shopify store selling refillable cleaning kits
Worked example
Their product page converts at 2.4% from 12,000 sessions a month, so 288 orders. Exit surveys show 31% of leavers ask about refill cost. Hypothesis: adding a refill price table lifts conversion rate from 2.4% to 2.8%, a 16.7% relative lift. That is 336 orders, 48 more per month. At a £42 AOV, £2,016 extra monthly revenue if the prediction holds.
See this on your own store
Paste your store URL. The audit takes about a minute, costs nothing, and ends with a welcome flow you can read before anything is sent.