Bell Statistics

What is the normal distribution?

The normal distribution is the symmetric bell-shaped curve defined by a mean and a standard deviation. Most statistical tests assume it applies to the sampling distribution of an estimate, not to the raw data — a distinction that decides when non-normal data actually matters.

Also called
Gaussian distribution, bell curve, normality
Allon Korem

Written by Allon Korem

Chief Executive Officer

Last updated

In plain English

The normal distribution is the symmetric bell curve, defined entirely by its mean and its standard deviation. It is symmetric about the mean, has thin tails, and follows the familiar rule that about 68% of values fall within one standard deviation, 95% within two and 99.7% within three. Its prominence is not because natural quantities are usually normal — many are not — but because of what happens to averages.

That is the central limit theorem, and it is the single most useful fact in applied statistics. Averages of many independent observations tend towards a normal distribution regardless of the shape of the original data. So a t-test does not require your data to be normal; it requires the *sampling distribution of the mean* to be approximately normal, which the central limit theorem usually delivers at experiment-scale sample sizes even when the raw data are wildly skewed.

This resolves the anxiety that surrounds normality testing in practice. Revenue per user is heavily right-skewed — most users spend nothing, a few spend a great deal — and a normality test on it will reject decisively at any reasonable sample size. That rejection is almost always irrelevant. With tens of thousands of observations per arm, the mean is close enough to normal for a t-test to behave correctly, and formal normality tests are actively unhelpful here: they reject trivial departures in large samples and lack the power to detect real ones in small samples, which is precisely backwards.

Where non-normality does bite is worth knowing precisely. Small samples, where the central limit theorem has not had enough observations to work with — under about thirty, and more for heavily skewed data. Extreme skew combined with a heavy tail, where the mean itself is dominated by a few outliers and estimates become unstable between samples. Statistics that are not averages, such as a maximum or a ratio of two random quantities, which the theorem says nothing about. And prediction intervals for individual values rather than for a mean, which do depend on the shape of the raw data.

When it genuinely is a problem, the responses are ordered by how much they change the question. Trim or winsorise the tail, which keeps the metric interpretable. Transform — a log is standard for right-skewed revenue — while remembering that you are now testing a difference in log means, which is a different quantity. Use a rank-based test such as Wilcoxon, which drops the normality assumption and tests a shifted distribution rather than a mean. Or bootstrap the interval, which makes no distributional assumption at all and is the cleanest option when compute is not a constraint. We cover the practical sequence in what to do when data is not normally distributed.

The formula

The density, the standardisation that makes every normal comparable, and the quantiles every test uses.

Density
f(x) = 1/(σ√(2π)) · e^{ −(x − μ)² / (2σ²) }

Two parameters and nothing else: the mean sets the location, the standard deviation sets the width.

Standardisation
z = (x − μ) / σ

Converts any normal to the standard normal with mean 0 and SD 1, which is what makes one table of quantiles serve every problem.

The empirical rule
P(|z| < 1) ≈ 0.68, P(|z| < 2) ≈ 0.95, P(|z| < 3) ≈ 0.997

Holds for normal data and fails badly for skewed data — applying it to revenue produces intervals extending below zero.

The quantiles tests use
z₀.₉₇₅ = 1.960, z₀.₉₅ = 1.645, z₀.₉₉₅ = 2.576

The 1.96 in every 95% confidence interval — see the two-sample t-test calculator, which uses the t quantile in small samples.

Worked example

Revenue per user in an experiment: 71% of users spend nothing, the mean is £6.80, the median is £0, and the standard deviation is £91. A Shapiro-Wilk test rejects normality at p < 0.0001. An analyst asks whether a t-test is valid at 40,000 users per arm.

Share of users spending zero
71%
Mean / median
£6.80 / £0.00
Skewness
14.2
Normality test on raw data
rejected, p < 0.0001
Bootstrap 95% CI on the difference
£0.18 to £1.31
t-test 95% CI on the difference
£0.19 to £1.30

The raw data are emphatically not normal, and the t-test interval matches the assumption-free bootstrap interval to within a penny.

The normality test is answering a question nobody asked. It is testing whether the raw revenue values are normal — they obviously are not, with 71% zeros and a skewness of 14 — while the t-test only requires the *difference in means* to be approximately normal, and at 40,000 users per arm the central limit theorem has delivered that comfortably. The bootstrap is the check that settles it: it makes no distributional assumption whatsoever, and it agrees. Where this would break down is at a few hundred users per arm, or if a single £40,000 order were driving the mean — so the diagnostic worth running is not a normality test but a look at how much the estimate moves when the largest few observations are removed.

Common misconceptions

My data are not normally distributed, so I cannot use a t-test.
The t-test assumes the sampling distribution of the mean is approximately normal, not the raw data. At experiment-scale sample sizes the central limit theorem usually delivers that even for heavily skewed data. Check by bootstrapping the interval and comparing — agreement means the assumption is fine.
A normality test tells me whether my data are normal enough.
It tells you whether you have enough data to detect a departure, which is nearly the opposite of what you want. Large samples reject trivial deviations that do not matter; small samples fail to detect serious ones that do. Look at a histogram and a Q-Q plot, and judge whether the departure is large enough to affect the specific statistic you are computing.
Log-transforming skewed data fixes the problem cleanly.
It changes the question. A test on log revenue compares geometric means, so a significant result says the typical multiplicative difference is non-zero — not that mean revenue differs, which is what the business case is denominated in. It also cannot handle zeros without an arbitrary offset, and revenue data is mostly zeros.

Frequently asked questions

How do I check whether my data are normal enough?
Plot rather than test. A histogram shows skew and multiple modes; a Q-Q plot shows tail behaviour, which is what actually matters. Then ask the right question — not whether the raw data are normal, but whether the statistic you are computing has an approximately normal sampling distribution. The most direct check is to bootstrap the interval and compare it against the parametric one: close agreement means the assumption is doing no harm.
How large does the sample need to be for the central limit theorem to apply?
The old rule of thirty is far too optimistic for skewed data. For roughly symmetric distributions, thirty is genuinely fine. For revenue-style data with heavy right skew and many zeros, hundreds or thousands may be needed before the mean behaves normally, and a metric dominated by a handful of very large values may never converge usefully at all. Sample size and skewness have to be judged together.
What should I use when normality genuinely fails?
In increasing order of how much they change the question: winsorise or cap the tail, which keeps the metric interpretable; bootstrap the interval, which assumes nothing about the distribution; or use a rank-based test such as Wilcoxon, which is robust but tests a shifted distribution rather than a difference in means. Bootstrapping is usually the best default because it answers the original question without a distributional assumption.

Related terms

  • Central limit theorem

    Why averages go bell-shaped even when the data do not — the result that makes ordinary tests work.

  • Outlier

    The extreme value that decides your result — and why the rule for handling it must precede the data.

  • Standard deviation

    How spread out the data are, in the data's own units — and the reason some metrics need vastly more sample.

  • Standard error

    How much your estimate would move if you ran the study again — precision, not spread.

  • Variance

    Spread in squared units — awkward to read, and the quantity every sample-size formula is built on.

Calculate it

  • Wilcoxon test

    Rank-sum (Mann-Whitney) and signed-rank tests, with the exact distribution for small samples.

  • Two-sample t-test

    Compare the average of two independent groups — plan the sample size, then test the result.

  • Paired t-test

    Before-and-after or matched pairs — size the study on the difference SD, then test it.

Knowing the term is the easy part

Applying it to a live measurement problem is the part that goes wrong. If you are designing an experiment, reading a result you do not trust, or trying to work out what your marketing actually caused, that is the work we do.