The null hypothesis (denoted H₀) is the foundational assumption in frequentist inference that any observed difference between a control and treatment group is due purely to random chance. In A/B testing infrastructure, it typically posits that a new personalization model has zero effect on the North Star Metric, providing a falsifiable baseline that must be disproven with sufficient evidence.
Glossary
Null Hypothesis
What is Null Hypothesis?
The null hypothesis is the default statistical assumption that there is no relationship between two measured phenomena or no difference among groups being compared, which experimenters seek to reject through hypothesis testing.
Rejecting the null hypothesis requires calculating a p-value that falls below a predetermined significance threshold (α), conventionally 0.05. Crucially, failing to reject H₀ does not prove it true—it merely indicates insufficient evidence to conclude a difference exists, a distinction that guards against Type I errors and the peeking problem in continuous experimentation platforms.
Key Characteristics of the Null Hypothesis
The null hypothesis (H₀) is the formal statistical assumption of no effect or no difference, serving as the default position that experimentation frameworks attempt to reject through rigorous evidence.
Default Position of Skepticism
The null hypothesis represents the status quo or the assumption that any observed difference is due to random chance. In A/B testing, H₀ typically states that the conversion rate of variant A equals variant B. The experimenter's burden is to gather sufficient evidence to reject this assumption, not to prove the alternative hypothesis directly. This framework protects against confirmation bias by forcing a structured, evidence-based approach to decision-making.
Formal Statistical Statement
Mathematically, the null hypothesis is expressed as an equality statement:
- H₀: μ₁ = μ₂ (no difference between population means)
- H₀: ρ = 0 (no correlation between variables)
- H₀: β = 0 (no effect of a feature in regression)
The alternative hypothesis (H₁ or Hₐ) is the complement, representing the presence of an effect. This binary framing enables the calculation of p-values and test statistics under a known sampling distribution.
Rejection vs. Failure to Reject
A critical nuance: experimenters never accept the null hypothesis. They either:
- Reject H₀: Sufficient evidence exists to conclude a statistically significant effect
- Fail to reject H₀: Insufficient evidence to conclude an effect, but this does not prove the null is true
This distinction prevents the logical fallacy of arguing from ignorance. A non-significant result may indicate a true null, insufficient statistical power, or a poorly designed experiment.
Relationship to Type I Error (α)
The significance level (α) is the pre-specified probability threshold for rejecting H₀ when it is actually true. Common values:
- α = 0.05: 5% risk of a false positive
- α = 0.01: 1% risk for high-stakes decisions
When a p-value falls below α, the result is declared statistically significant. This directly controls the Type I error rate—the probability of claiming a winning variant when no real difference exists. Setting α too high inflates false discoveries; setting it too low increases Type II errors.
Assumption of No Effect
The null hypothesis embodies the principle of parsimony: the simplest explanation (no effect) is preferred until evidence demands otherwise. In frequentist inference, H₀ provides the sampling distribution used to calculate how extreme an observed result is. Without a clearly defined null, there is no baseline for measuring effect size or determining if a metric movement is attributable to the treatment rather than random variation in the data.
Practical vs. Statistical Significance
Rejecting the null hypothesis only confirms that an effect likely exists, not that it is practically meaningful. With large sample sizes, even trivially small differences can produce statistically significant p-values. Experimenters must evaluate:
- Effect size: The magnitude of the difference (e.g., Cohen's d)
- Confidence intervals: The precision of the estimate
- Business impact: Whether the lift justifies engineering cost
A significant result with a 0.01% lift may be statistically valid but operationally irrelevant.
Frequently Asked Questions
Clear, technically precise answers to the most common questions about the null hypothesis in A/B testing and AI experimentation.
A null hypothesis (H₀) is the default statistical assumption that there is no relationship between two measured phenomena or no difference among groups being compared. In A/B testing for AI personalization, the null hypothesis typically states that the new model variant (treatment) produces metrics identical to the current production model (control). The experiment is designed to gather sufficient evidence to reject this assumption, thereby demonstrating that the observed lift in click-through rate or conversion is not due to random chance. Formally, H₀: μ_treatment = μ_control, where μ represents the population mean of the target metric.
Null Hypothesis vs. Related Statistical Concepts
Distinguishing the null hypothesis from core inferential concepts in A/B testing and experimentation.
| Concept | Null Hypothesis (H₀) | Alternative Hypothesis (H₁) | P-Value |
|---|---|---|---|
Definition | The default assumption of no effect, no relationship, or no difference between groups. | The competing claim asserting a statistically significant effect, relationship, or difference exists. | The probability of observing the test statistic, or one more extreme, assuming H₀ is true. |
Core Purpose | Establishes a falsifiable baseline to be challenged by experimental data. | Represents the practical outcome the experimenter hopes to validate. | Quantifies the strength of evidence against H₀; a decision threshold, not a measure of effect magnitude. |
Logical Role | The 'straw man' to be rejected; presumed innocent until proven guilty. | The 'new finding'; accepted only if H₀ is rejected with sufficient evidence. | The 'weighing scale'; does not measure the probability that H₀ is true or false. |
Decision Rule | Rejected if p-value < α (significance level, typically 0.05). | Accepted if H₀ is rejected; otherwise, the test is inconclusive. | Compared directly to the pre-defined alpha level to trigger a binary decision. |
Error Association | Type I Error (α): Incorrectly rejecting a true H₀ (false positive). | Type II Error (β): Incorrectly failing to reject a false H₀ (false negative). | Directly controls the Type I error rate; does not quantify Type II error risk. |
Practical Interpretation | A true null implies observed differences are due to random chance or sampling noise. | A true alternative implies the treatment variant caused a real, non-random shift in the metric. | A small p-value (< 0.05) suggests the data is surprising under H₀, not that H₁ is definitively true. |
Relationship to Sample Size | Becomes easier to reject with larger samples, even for trivial, non-practical effects. | Requires sufficient statistical power to be detected; power increases with sample size. | Decreases as sample size increases for a fixed non-zero effect; does not measure effect size. |
Enabling Efficiency, Speed & Accuracy
Intelligent Analysis, Decision & Execution
We build AI systems for teams that need search across company data, workflow automation across tools, or AI features inside products and internal software.
Talk to Us
Search across company data
Give teams answers from docs, tickets, runbooks, and product data with sources and permissions.
Useful when people spend too long searching or get different answers from different systems.

Automate internal workflows
Use AI to route work, draft outputs, trigger actions, and keep approvals and logs in place.
Useful when repetitive work moves across multiple tools and teams.

Add AI to products and internal tools
Build assistants, guided actions, or decision support into the software your team or customers already use.
Useful when AI needs to be part of the product, not a separate tool.
Related Terms
Master the statistical and methodological concepts that form the foundation of rigorous A/B testing for AI-driven personalization.
P-Value
The probability of observing a test statistic at least as extreme as the one calculated, assuming the null hypothesis is true. It is a continuous measure of compatibility between the observed data and the null hypothesis.
- Common threshold: p < 0.05 for rejecting the null
- Misinterpretation risk: A p-value is not the probability that the null hypothesis is false
- Calculation: Derived from the sampling distribution of the test statistic (e.g., t-distribution)
Type I Error
A false positive error that occurs when the null hypothesis is incorrectly rejected. The experimenter concludes a variant has a significant effect when it actually does not.
- Significance level (α): The pre-specified probability of committing a Type I error, typically set at 0.05
- Impact: Leads to shipping features or models that provide no real improvement
- Control: Managed by setting a strict alpha threshold and adjusting for multiple comparisons
Type II Error
A false negative error that occurs when the null hypothesis is incorrectly retained. A genuine improvement from a treatment variant is missed due to insufficient evidence.
- Beta (β): The probability of committing a Type II error
- Statistical Power (1-β): The probability of correctly rejecting a false null hypothesis
- Common cause: Insufficient sample size or too short an experiment duration
- Mitigation: Conduct a power analysis before launching the experiment
Confidence Interval
A range of values, derived from sample data, that is likely to contain the true population parameter with a specified probability (typically 95%).
- Interpretation: If the experiment were repeated many times, 95% of the calculated intervals would contain the true effect
- Practical use: Provides a measure of precision and uncertainty around the point estimate of the lift
- Decision rule: If the interval for a metric excludes zero, the result is statistically significant at the corresponding alpha level
Statistical Power
The probability that a statistical test will correctly reject a false null hypothesis. It represents the experiment's sensitivity to detect a true effect if one exists.
- Target: Conventionally set at 80% (0.80)
- Key drivers: Sample size, effect size, and significance level (α)
- Trade-off: Increasing power requires more traffic or a longer experiment duration
- Calculation: Performed via power analysis using the minimum detectable effect (MDE)
Effect Size
A quantitative measure of the magnitude of the difference between two groups, providing a standardized assessment of practical significance independent of sample size.
- Cohen's d: Standardized mean difference for continuous metrics
- Relative lift: Percentage change, common for conversion rates and revenue
- Why it matters: A statistically significant result with a negligible effect size may not be worth the engineering cost of deployment

About the author
Prasad Kumkar
CEO & MD, Inference Systems
Prasad Kumkar is the CEO & MD of Inference Systems and writes about AI systems architecture, LLM infrastructure, model serving, evaluation, and production deployment. Over 5+ years, he has worked across computer vision models, L5 autonomous vehicle systems, and LLM research, with a focus on taking complex AI ideas into real-world engineering systems.
His work and writing cover AI systems, large language models, AI agents, multimodal systems, autonomous systems, inference optimization, RAG, evaluation, and production AI engineering.
Partnered with leading AI, data, and software stack.
How We Work
Custom AI workflows for your Business
One-fit-all AI don't work for modern businesses. At Inferensys, we aim to understand your business & custom requirements; which we use to define most efficient agentic workflows, the data, and the tools for your business.
01
Review the use case
We understand the task, the users, and where AI can actually help.
Read more02
Pick the right approach
We define what needs search, automation, or product integration.
Read more03
Build the first useful version
We implement the part that proves the value first.
Read more04
Improve from there
We add the checks and visibility needed to keep it useful.
Read moreThe first call is a practical review of your use case and the right next step.
Talk to Us