Null Hypothesis

The null hypothesis is the default assumption in a hypothesis test — typically that there's no effect, no difference between groups, or no relationship between variables — which the entire test is structured to argue against using observed data. A new drug's null hypothesis would typically be "this drug has no effect on the condition compared to a placebo," and the test's entire logic is built around assessing whether the observed data is surprising enough under that specific assumption to justify abandoning it in favor of an alternative hypothesis instead.

The null hypothesis occupies a specific, deliberately conservative logical role that's easy to misunderstand: hypothesis testing is structured to require strong evidence to reject the null hypothesis, but it never allows a test to actually prove the null hypothesis true — a result that fails to reject the null hypothesis only means the evidence wasn't strong enough to rule it out, not that "no effect" has been confirmed, a distinction formally summarized as "failing to reject" rather than "accepting" the null hypothesis, precise but frequently blurred terminology in casual discussion of statistical results. This asymmetry is a deliberate feature of the framework's design, modeled closely on the logic of a legal trial: a defendant is presumed innocent (the null hypothesis) unless the prosecution's evidence is strong enough to overcome that presumption beyond a reasonable doubt, and a not-guilty verdict means the evidence wasn't sufficient to convict, not that innocence was definitively proven.

Null hypothesis: the default, conservative assumption
no effect, no difference, no relationship
Legal trial analogy
Presumed innocent
unless evidence is strong enough to overcome that presumption
Two possible test outcomes — asymmetric by design
Reject the null hypothesis
evidence was strong enough
Fail to reject the null hypothesis
NOT the same as proving it true — just insufficient evidence against it
"Fail to reject" is precise, deliberate language
a test never confirms the null hypothesis, it can only fail to overturn it

Choosing what the null hypothesis actually states is a substantive, consequential decision, not a mechanical formality, and it's always formulated as the specific, precise claim the data is tested against — a null hypothesis of "no difference in conversion rate between A and B" is a specific numerical claim (the true difference is exactly zero), distinct from a vague claim like "the two variants aren't very different," and the entire mathematical machinery of the test (the p-value calculation specifically) depends on the null hypothesis being stated as a precise, testable claim rather than a loose qualitative one. This precision also explains why a non-significant result (failing to reject the null hypothesis) is a genuinely weaker and more limited claim than it's often informally treated as — it specifically means the test didn't find strong enough evidence against that exact null hypothesis, which is a narrower statement than "there is definitely no effect," especially when a study's sample size was small enough that even a real, meaningful effect might not have produced statistically significant evidence against the null.

Ronald Fisher, who formalized much of modern hypothesis testing's structure in the 1920s and 1930s, originally conceived of the null hypothesis test as producing a single continuous p-value meant to inform judgment rather than trigger an automatic accept-or-reject decision, a more nuanced original framing that later got merged, somewhat uneasily, with Jerzy Neyman and Egon Pearson's separate decision-theoretic framework (which did explicitly define accept/reject decisions based on a fixed significance threshold) — the hybrid version of hypothesis testing taught and used today blends elements of both approaches, a historical merger that statisticians and methodologists have periodically revisited and critiqued as blending two genuinely different original philosophies.

Read the null hypothesis as the deliberately conservative default position a statistical test is built to argue against, not simply "the boring answer" being set up to fail: the "fail to reject" versus "accept" distinction is precise, intentional language reflecting the test's actual logical structure, modeled closely on a legal trial's presumption of innocence, and understanding that a non-significant result never proves the null hypothesis true — it only reflects insufficient evidence against it — is essential to correctly interpreting what a hypothesis test's outcome actually does and doesn't establish.

Take null hypothesis further

Ask the copilot about this term, or have our engineers assess it against your process.