Control Charts and Process Capability — the Math That Makes Six Sigma Work

Strip away the belts, the project charters and the workshop jargon, and Six Sigma rests on a surprisingly small mathematical core: the statistics of variation. Two tools carry most of that weight — control charts, which tell you whether a process is stable, and capability indices, which tell you whether a stable process is actually good enough. Understanding how they work, and in which order to apply them, separates practitioners who genuinely improve processes from those who merely decorate reports with Greek letters.

Variation is the enemy, but it comes in two kinds

Every process varies. The insight that launched statistical process control is that variation has two fundamentally different sources. Common cause variation is the background noise inherent to the process — small fluctuations in material, temperature, operator technique — that produces a stable, predictable spread. Special cause variation comes from something outside the system: a tool wearing out, a bad batch of raw material, a new untrained operator. The distinction matters because the correct responses are opposite. Reacting to common cause variation as if it were special (adjusting the machine after every slightly-off measurement) actually increases variation, a phenomenon known as tampering. Ignoring special causes, meanwhile, lets real problems hide inside the noise.

How a control chart separates signal from noise

A control chart plots a statistic — a sample mean, a range, a proportion of defects — over time, against three lines: the center line at the process average and control limits placed three standard deviations above and below it. The limits are not specifications and not wishes; they are calculated from the process’s own historical behaviour. If the process is subject only to common causes, roughly 99.7 percent of points will fall within the limits, and the pattern will look random. A point beyond a limit, or a non-random pattern inside them — seven points on one side of the center line, a steady trend, a repeating cycle — signals a special cause worth investigating. The mathematics here is essentially the logic of hypothesis testing run continuously: each point asks whether the process has changed, with the three-sigma limits chosen to balance false alarms against missed signals.

Capability: comparing the voice of the process to the voice of the customer

A stable process is predictable — but predictability alone satisfies nobody. Capability analysis asks the second question: does the process spread fit within the specification limits the customer requires? The classic indices compress this into single numbers:

• Cp compares the specification width to six standard deviations of process spread — a measure of potential capability if the process were perfectly centered,
• Cpk penalises off-center processes by measuring the distance from the mean to the nearer specification limit,
• Pp and Ppk do the same using long-term variation, capturing drift between samples that short-term studies miss.

A Cpk of 1.0 means the process just barely fits; the Six Sigma ideal of near-zero defects corresponds to a Cpk of about 1.5 once typical process drift is accounted for. The crucial rule: capability numbers are meaningless for an unstable process. Control first, capability second — always in that order.

Why the math needs method around it

None of these calculations is difficult in isolation; a spreadsheet handles them easily. The hard part is judgment: choosing rational subgroups so the chart measures the right variation, recognising which out-of-control patterns point to which causes, and knowing when data violate the assumptions behind the indices. That judgment is exactly what structured Lean Six Sigma training is designed to build — the statistics embedded in a problem-solving method, practised on real processes rather than textbook exercises. The formulas make Six Sigma rigorous; knowing when and how to apply them is what makes it work.