Common Language Tool: Common-Cause vs. Special-Cause
Let’s talk about something that quietly drains a lot of time and energy in organizations.
Have you ever watched your team spend 20 minutes building a solution for a scenario that happens twice a year? Or seen one unhappy patient cause everyone to question a system that works beautifully for the other 99 percent?
That’s where this tool comes in.
Before we go further, let’s quickly define what we mean by a system. A system is simply a consistent, agreed-upon way to perform a task. It’s the “this is how we do it here” method. When a system is clear, anyone can follow it, it reduces variation and it improves reliability. And I’ll say it again because it matters: you can’t have quality without consistency, and you can’t have consistency without standards.
Now here’s the important distinction.
Common-cause refers to what happens most of the time. Think 95 percent of your day. The regular check-in process. The way phones are answered. The way a handoff happens between departments. These are predictable patterns. When something falls into this category, it deserves a thoughtful, well-designed system.
Special-cause, on the other hand, is the rare exception. The unusual request. The once-a-year scheduling nightmare. The unique complaint that doesn’t reflect the broader experience. These situations are real, but they are not the norm.
Where teams get stuck is when a special-cause event feels big and urgent, and we react by redesigning the entire system.
That’s when it’s helpful to pause and ask one simple question: Is this common-cause or special-cause?
If it’s common-cause, it probably needs refinement. If it’s special-cause, it probably needs flexibility.
Try weaving this language into your meetings. When a discussion starts to spiral, gently bring it back to that distinction. Over time, your team will get better at recognizing when a system truly needs work and when you’re simply reacting to an outlier.
This small shift saves time, reduces frustration, and protects the integrity of your systems. And that’s the whole point.









