David Bauer • February 19, 2026

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.

By David Bauer January 15, 2026
One of the most common leadership challenges we see across organizations is under-communication. It rarely shows up as silence. It shows up as assumptions.
By David Bauer December 22, 2025
If you’ve ever been in the middle of managing something truly urgent and had a team member approach you with what felt like a small concern, you know the tension I’m talking about. You’re triaging an urgent patient situation. A serious operational decision is unfolding. Your brain is fully in Fast Think mode. And suddenly, someone is standing next to you asking about next week’s schedule, a minor process question, or a frustration they want to talk through right now. So you told the truth, you didn’t have time. Later, you find out they felt dismissed. Or unheard. Or confused about why you didn’t seem willing to help. No one did anything “wrong,” but the disconnect still created friction. This is exactly where shared language matters. In earlier blogs , we talked about why a common language on a team is essential and how understanding Slow Think versus Fast Think helps teams work more effectively together. This tool builds on both of those ideas. The reality leaders don’t always say out loud: Many leaders, especially in healthcare, wear multiple hats at the same time. For example, you’re often switching between three distinct roles: Doctor Entrepreneur Leader The challenge is that those hats don’t always change on command. When you’re deep in your doctor role, managing a retinal concern, an acute red eye, or an unexpected complication, it can be genuinely hard to pivot immediately into your leader role and give a team member the time and attention they deserve. That doesn’t mean their concern isn’t important. It means the timing isn’t aligned. Most frustrations on teams come down to misaligned expectations, not bad intentions. I ntroducing the “Now, Soon, Later” language: “Now, Soon, Later” is a simple prioritization tool that gives teams shared language around timing without minimizing importance. The core question is: “Is this a now, a soon, or a later thing?” That’s it. Simple. Powerful. When leaders consistently use this language, a few important things happen. First, it reminds your team that you are balancing multiple roles and responsibilities in real time. If you can’t address something immediately, it’s not because it doesn’t matter. Second, it reassures them that there is a reason you may need to wrap up a conversation quickly or defer it altogether in that moment. Third, it gives them a framework to think through when and how they bring things to you. Over time, people naturally start to self-prioritize before interrupting. What this sounds like in real life: You might say: “I want to hear this. Is this a now, soon, or later thing?” “I’m in a now situation clinically. Can we put this in the soon bucket and circle back?” “This feels like a later conversation. Let’s find a time where we can both be present.” And yes, sometimes you may need to gently recalibrate expectations after the fact. That could sound like, “I’m not sure we’re on the same page yet about what counts as a now versus a soon. Let’s talk through that.” For this tool to work, follow-through matters. If you put something in the “soon” or “later” bucket and never come back to it, trust erodes quickly. The language only works when your actions reinforce it. Circling back doesn’t have to be elaborate. Even a quick: “Hey, you mentioned this earlier. I wanted to make sure we reconnect on it.” This language isn’t just for deflecting interruptions. It’s also a powerful way to show respect for your team’s workload. For example: “Susie, I have a few projects I’ll need from you, but none of them are a now. Let’s find a time that works with your current priorities to talk through them.” This approach acknowledges their capacity, avoids urgency inflation, and sets the tone for thoughtful planning instead of constant reaction.
By KDR Team October 13, 2025
Discover the power of "Slow-Think/Fast-Think" to transform your communication and build trust.
Image of a dictionary page, defining the word dictionary
By KDR Team September 17, 2025
Communication can feel threatening. But what if your team had the same playbook for conversations? That’s the power of a “common language.”
By KDR Team August 15, 2025
What does emotional recovery look like for leaders?
By KDR Team July 16, 2025
Why Fixing Everyone's Problems Is Holding Your Team Back
By KDR Team June 20, 2025
Great leaders schedule what's important; they don't just hope to find time.
By KDR Team May 13, 2025
Ever feel like you're running circles and getting nowhere fast with your team?
By KDR Team April 22, 2025
Hey friends, I want to talk about two words that get tossed around quite a bit, responsibility and accountability.
By KDR Team March 20, 2025
Why Your Onboarding Process is Broken (and How to Fix It)