Why EOS Stops Working (And What Your Leadership Team Is Telling Itself Instead)
Why EOS Stops Working (And What Your Leadership Team Is Telling Itself Instead)
Let me walk you through some EOS math.
Avoiding a hard conversation with someone on your team? You basically saved everyone time and energy. Leaving the same issue on the Issues List for three quarters? Basically handled. Hiring someone who is not quite right for the seat because you needed to fill it fast? Close enough. Skipping the accountability conversation because things seem fine right now? You definitely did not just make it worse.
Okay, I'm playing. But only a little.
If any of those hit close to home, that's worth paying attention to. Because none of those are productivity strategies. They are what happens when EOS disciplines start slipping quietly and nobody names it.
The Gap Between Knowing EOS and Doing EOS
Most leadership teams that have been running on EOS for a year or more know the tools well. They can tell you what the Issues List is for. They understand the purpose of rocks. They know how a Level 10 Meeting is supposed to run.
Knowing and doing are two different things.
The gap shows up gradually. A Level 10 that runs long and nobody resets the structure. An issue that keeps getting carried over because resolving it requires a conversation nobody wants to have. A rock that gets marked complete even though everyone in the room knows it wasn't really done. Small compromises, each one feeling reasonable in the moment, that add up to a team that is going through the motions of EOS rather than actually running on it.
Why EOS Disciplines Slip
There are a few patterns I see regularly with the leadership teams I work with.
The first is comfort. Early in an EOS journey, everything feels new and intentional. Over time, as the tools become familiar, the rigor quietly loosens. The meeting pulse starts running long. The scorecard gets skimmed instead of reviewed. The IDS process gets shortcut because everyone is tired and wants to move on.
The second is avoidance. Some issues stay on the list for months not because they're complex, but because solving them requires a conversation that feels uncomfortable. A seat that isn't right. A behavior that needs to be addressed. Avoidance masquerades as patience, but it's not the same thing.
The third is inconsistency. The tools only work when you use them every week, not just when it's convenient. A team that runs a tight Level 10 when things are going well but abandons the structure when things get busy is not really running on EOS.
How to Reset When Discipline Has Slipped
If you're recognizing your team in some of this, the answer is not a dramatic overhaul. It's an honest reset.
Name what's happened. In your next Level 10, put the pattern on the Issues List. Acknowledge that discipline has slipped in specific ways, identify what needs to change, and make a concrete commitment to it. Then hold each other to it the following week, and the week after that.
The teams that get the most out of EOS long-term are not the ones who never slip. They're the ones who notice when they have and choose to get back on track instead of rationalizing their way around it.
If you are ready to stop managing around the hard stuff and actually solve it, that is exactly what I help leadership teams do. Visit bethfahey.com to learn more about working together.
