What a Nonsignificant Result Says
A test can produce a result that does not cross its prespecified significance threshold. In that case, the decision rule says to fail to reject the null hypothesis. This is a limited conclusion about the evidence in the sample under the chosen test. It is not a declaration that the null hypothesis is true.
The distinction matters whenever a study compares a population value with a benchmark. A sample might be consistent with the benchmark, but also too imprecise to distinguish it from other plausible values. For example, a sample mean close to a target may reflect a population mean at the target, or a different population mean combined with sampling variation. A nonsignificant result alone does not settle which explanation is correct.
A p-value is calculated under the assumption that the null model is correct. It measures how often that model would produce a test statistic at least as extreme as the observed one, using the test’s definition of extremeness. Thus, a p-value above \(\alpha\) says the observation was not sufficiently extreme by that rule. It is not the probability that the null hypothesis is true, nor is it a measure of the probability that the observed difference arose “by chance.”
A Test Model for the Examples
The examples below use a two-sided test for a population mean when the population standard deviation \(\sigma\) is known and the population is normally distributed. Assume the observations are a random, independent sample. Under the null hypothesis \(H_0:\mu=\mu_0\), the sample mean has standard error \(\sigma/\sqrt{n}\), and the test statistic follows the standard normal distribution:
The alternative hypothesis is \(H_a:\mu\ne\mu_0\). For this two-sided test, results far enough in either direction from zero count as extreme. The p-value is \(P(|Z|\ge |z_{\text{obs}}|)\), calculated using the standard normal distribution under \(H_0\). At \(\alpha=0.05\), the rejection region is approximately \(Z<-1.96\) or \(Z>1.96\); equivalently, the two-sided p-value must be at most 0.05 for rejection.
This model is appropriate for the hypothetical examples because each specifies a random, independent sample from a normally distributed population, with its population standard deviation known. Those conditions justify the stated normal test calculation. They are assumptions of the examples, not facts inferred from a nonsignificant result.
Worked Examples: Failing to Reject a Benchmark
Worked Example: A Small Difference From a Target Fill
Suppose a hypothetical packaging line is assessed using a random, independent sample of \(n=9\) containers. The fill amounts are normally distributed with known population standard deviation \(\sigma=12\) grams. The sample mean is \(\bar{x}=496\) grams. Test at \(\alpha=0.05\) whether the population mean differs from the 500-gram target.
The hypotheses are \(H_0:\mu=500\) grams and \(H_a:\mu\ne500\) grams. The sample mean’s standard error under the null is \(SE=12/\sqrt{9}=4\) grams. The standardized result is
For a two-sided test, the p-value is \(P(|Z|\ge1.00)\), which is approximately \(0.3173\). Since \(0.3173>0.05\), we fail to reject \(H_0\).
The sample mean is 4 grams below the target, but the test does not provide sufficiently strong evidence, by its chosen rule, that the population mean differs from 500 grams. It would be incorrect to conclude that the true mean is 500 grams. The result is also compatible with a population mean that differs from 500 grams; this sample has not distinguished those possibilities.
Worked Example: A Higher Sample Mean That Still Does Not Reject
In a hypothetical battery study, a random, independent sample of \(n=16\) batteries has a mean operating time of \(\bar{x}=10.8\) hours. Assume operating times come from a normal population with known standard deviation \(\sigma=2\) hours. Test whether the population mean operating time differs from a benchmark of 10 hours, using \(\alpha=0.05\).
Set \(H_0:\mu=10\) hours and \(H_a:\mu\ne10\) hours. The conditions stated for this hypothetical setting support the normal test model. The standard error is \(SE=2/\sqrt{16}=0.5\) hours, so
The two-sided p-value is \(P(|Z|\ge1.60)\), approximately \(0.1096\). Because \(0.1096>0.05\), the test fails to reject the null hypothesis.
The observed mean is 0.8 hours above the benchmark, and the direction of that difference is positive. But the test does not meet the rule for concluding that the population mean differs from 10 hours. It does not demonstrate that the population mean is exactly 10 hours, either. The decision is about the evidence and threshold, not a proof of equality.
Worked Example: A Result Near the Rejection Threshold
Consider a hypothetical random, independent sample of \(n=25\) laboratory measurements. Suppose the population is normal with known standard deviation \(\sigma=10\) units, and the sample mean is \(\bar{x}=73.6\) units. The benchmark is \(\mu_0=70\) units. Test \(H_0:\mu=70\) against \(H_a:\mu\ne70\) at \(\alpha=0.05\).
The standard error is \(SE=10/\sqrt{25}=2\) units. Therefore,
The two-sided p-value is \(P(|Z|\ge1.80)\), approximately \(0.0719\). This exceeds \(0.05\), so we fail to reject \(H_0\). The result is relatively close to the stated cutoff, but it remains on the non-rejection side of the decision rule.
A suitable conclusion is that this sample does not provide sufficient evidence at the 5% significance level that the population mean differs from 70 units. It is not suitable to say that the test “nearly proved” the benchmark, or that the population mean must be 70. The sample mean differs from the benchmark, while the test’s evidence does not cross its prespecified threshold.
Why Non-Rejection Cannot Prove Equality
A test is designed to reject \(H_0\) when the data would be unusually extreme if the null model were true. But samples vary. Even if the population value differs from the benchmark, a particular sample can land near the null value and produce a nonsignificant result. This possibility is not a contradiction: the test’s rule is about how extreme the observed data are, not whether the population value has been proven equal or unequal.
The first example gives a direct illustration. Its null model has \(\mu_0=500\) grams, \(SE=4\) grams, and a two-sided 5% rejection region of approximately \(|Z|>1.96\). Now suppose, for illustration, that the true population mean were 504 grams instead. Under the same normal sampling model, the statistic \(Z=(\bar{x}-500)/4\) would have mean \((504-500)/4=1\) and standard deviation 1.
A failure to reject would occur when \(-1.96\le Z\le1.96\). Under the illustrative alternative mean of 504 grams, this probability is
Here \(\Phi\) is the cumulative distribution function of the standard normal distribution. Under those assumptions, a sample would fail to reject the 500-gram null in about 83% of repeated samples even though the hypothetical true mean is 504 grams. This calculation shows why non-rejection is not equivalent to establishing the null: a population value different from the benchmark can still often produce data inside the non-rejection region.
The calculation does not say that the mean in the packaging example is 504 grams. It describes what could happen under a particular alternative value and sampling model. Its purpose is to show that non-rejection can occur when the null is false. The observed p-value by itself cannot tell us the probability that this alternative—or any other particular value—is true.
Common Mistake: Treating “Not Significant” as “No Difference”
A common error is to reason: “The p-value is above 0.05, so the population value equals the benchmark.” The conclusion does not follow. The test has not rejected the equality stated in \(H_0\), but it has not shown that equality is correct. In particular, “no statistically significant evidence of a difference” is not interchangeable with “evidence that there is no difference.”
A better report states the decision and its limits: name the population quantity and benchmark, give the direction of the sample estimate if relevant, report the p-value or decision, and say that the sample did not provide sufficient evidence to reject the null at the chosen level. Do not turn a failure to reject into a claim of exact equality or certainty.
If the question is specifically whether a population value is close enough to a benchmark for a defined purpose, ordinary failure to reject a difference is not, by itself, an answer. Such a claim needs an explicit definition of what counts as close enough and an appropriate method for assessing that claim. A nonsignificant difference test does not supply that definition.
Check Your Understanding
Use the distinction between a test decision and a claim about the population to answer these questions.
- A two-sided test at \(\alpha=0.05\) gives \(p=0.18\). What is the test decision, and what does that decision not establish?
- A sample mean is below its benchmark, but its two-sided test is nonsignificant. Which part of the result describes direction, and which part describes the decision threshold?
- Explain why a sample drawn from a population that differs from the null value can still produce a nonsignificant result.
- Rewrite this conclusion accurately: “The test was nonsignificant, so the population mean equals the target.”
- Why is “no statistically significant evidence of a difference” a more defensible statement than “there is no difference” after a nonsignificant test?