Complete guide
Normality Test Guide
Many statistical tools — capability indices, t-tests, control charts — assume your data is normally distributed. A normality test checks that assumption objectively so you know whether to trust those tools or switch to a nonparametric alternative.
What it is
What is a normality test?
A normality test asks whether a sample could plausibly have come from a normal (Gaussian) distribution. The Anderson-Darling test compares the empirical distribution of your data with the theoretical normal CDF, giving more weight to the tails than older tests. A large A² statistic and small p-value mean the data departs from normality.
Calculation logic
How the calculation works
The Anderson-Darling test checks how well your data matches a normal (bell-shaped) curve. It lines your sorted values up against what a perfect normal distribution would predict and measures the gap, paying special attention to the tails where non-normality usually shows. That gap becomes the A² statistic, which is turned into a p-value. A p-value above 0.05 means it is safe to treat the data as normal; below 0.05 means it is not, so you would use a transformation or a rank-based method instead.
Worked example
Worked example: is it safe to calculate Cpk?
Before calculating process capability (Cpk), the team checks whether fill-weight data is normally distributed. They collect 30 measurements and run an Anderson-Darling test. The p-value is 0.08 — above 0.05, so they can't reject normality.
The probability plot confirms it: points stay close to the reference line, no obvious curves or outliers. Safe to proceed with standard Cpk.
What to do with this: Always check normality before using Cpk. If your p-value is below 0.05, use a non-normal capability method or transform the data first — otherwise Cpk will give you the wrong answer.
Why it matters
Operational impact
Capability indices (Cp, Cpk), Shewhart control limits and t-tests all assume normal data. If the assumption is wrong, those numbers can mislead — a process that looks capable may not be. Testing normality first protects you from drawing the wrong conclusion from the right calculation.
Decision making
When to use it
Run a normality test in the Measure and Analyse phases before any analysis that assumes a normal distribution. If the data passes, continue with standard tools. If it fails, transform the data, use a nonnormal capability method, or switch to a rank-based nonparametric test.
Lean Six Sigma
Link to Six Sigma
Checking normality is a routine gate in DMAIC. The Anderson-Darling test is the default normality test in most Six Sigma software because of its sensitivity in the tails, where capability and risk decisions are most affected.
Industry examples
Where normality testing is used
ManufacturingConfirm that dimensional or weight data is normal before running a Cp/Cpk capability study or setting control limits.
HealthcareCheck lab values and turnaround times — often skewed — to choose between parametric and nonparametric comparisons.
Product & R&DValidate the normality assumption before applying t-tests or ANOVA to experimental results.
Software & servicesResponse and handling times are usually right-skewed, so a normality test guides you toward medians and percentiles instead of means.
Common mistakes
Common normality testing mistakes
- Testing normality with a very large dataset — with 500+ data points, even a tiny, irrelevant deviation will fail the test. Use a probability plot instead.
- Testing with very small datasets — with fewer than 20 points, normality tests have almost no power. The test will almost always pass even for clearly non-normal data.
- Confusing 'passes the normality test' with 'is perfectly normal' — most real data is approximately normal, which is good enough for most statistical tools.
- Skipping the probability plot and relying only on the p-value — the plot shows you how the data deviates from normal, which the p-value alone doesn't reveal.
- Running multiple normality tests and using whichever one passes — pick one test before you look at the data and stick to it.
What to do next
After the test
If the data is normal, proceed with capability analysis, control charts or parametric tests with confidence. If it is not normal, first check for outliers or a mixture of two processes (visible as a second peak). Consider a Box-Cox or Johnson transformation, a nonnormal capability method, or a nonparametric test such as Mann-Whitney or Kruskal-Wallis. Always pair the p-value with the probability plot before deciding.
Resources
Templates, videos and learning
Combine the normality test with histograms, capability analysis and a DMAIC project structure to make sound, assumption-checked decisions.
Frequently asked questions
What is the difference between a paired and a 2-sample t-test?
A paired t-test is used when the same items (machines, patients, stations) are measured twice — before and after, or under two conditions. Because each pair shares variability, the test eliminates that source of noise and is more powerful than a 2-sample test. A 2-sample (independent) t-test is used when the two groups are completely separate, with no natural pairing between observations.
What counts as 'paired' data?
Data is paired when there is a natural one-to-one correspondence between each before and after value — the same machine, the same patient, the same workstation. Examples: cycle time on 10 machines before and after a process change; blood pressure in 20 patients before and after treatment; inspection times for the same parts under two methods. If the items in the two groups are different, use a 2-sample t-test.
What are the assumptions of the paired t-test?
The paired t-test assumes: (1) observations are independent of each other (one pair does not influence another); (2) the differences (after minus before) are approximately normally distributed — for small samples use a normality test; (3) there are no extreme outliers in the differences. Violations of normality with small samples suggest using a nonparametric alternative such as the Wilcoxon signed-rank test.
What sample size do I need for a paired t-test?
The minimum recommended is about 10–15 pairs, though the test works with fewer if the differences are normally distributed. The required sample size depends on the expected mean difference, the standard deviation of differences, and the desired power (typically 80%). For a kaizen study where you expect a 10% improvement with moderate variability, 20–30 pairs typically gives adequate power. Use a sample size calculator to plan your study.