Understanding Variation: Common vs. Special Cause

Variation is the heartbeat of Six Sigma. It’s the reason the methodology exists and the lens through which practitioners understand process behavior. Yet variation is often misunderstood. Teams react to every fluctuation as if it were a crisis, or they ignore meaningful signals because they assume everything is “normal.” Understanding variation—specifically the difference between common‑cause and special‑cause variation—is essential for effective improvement. 

Common‑cause variation is the natural, built‑in variation of a stable process. It’s the predictable range of outcomes that occur when a process is functioning as designed. For example, if a call center typically answers calls in 45–55 seconds, that range represents common‑cause variation. It’s not a sign of a problem. It’s simply how the process behaves. 

Special‑cause variation, on the other hand, is unexpected. It occurs when something unusual disrupts the process—an equipment failure, a sudden spike in demand, a new employee learning the job, or a supplier delivering inconsistent materials. Special causes create outcomes that fall outside the normal range. They are signals that something has changed. 

The challenge is that many organizations treat all variation as special cause. They react to every fluctuation, adjusting processes constantly in an attempt to “fix” what isn’t broken. This creates instability and increases variation. Conversely, some organizations treat all variation as common cause, ignoring meaningful signals that indicate a real problem. Both extremes lead to poor decisions. 

Control charts are the primary tool for distinguishing between common and special causes, but the underlying principle is simple: don’t react to noise, and don’t ignore signals. When practitioners understand variation, they make better decisions. They know when to investigate and when to leave the process alone. 

Understanding variation also helps teams identify opportunities for improvement. If a process shows only common‑cause variation but still fails to meet customer requirements, the process needs to be redesigned. If a process shows special‑cause variation, the team needs to identify and eliminate the source of the disruption. 

Variation is not the enemy. It’s information. It tells practitioners how the process behaves, how stable it is, and where to focus improvement efforts. When teams learn to read variation correctly, they stop firefighting and start improving.