Self-implementing EOS can absolutely work.
I’ve seen leadership teams get real traction on their own. They read the books, commit to the tools, & genuinely want to build a better business.
But I’ve also seen something else.
Teams that look like they’re “doing EOS”…
but aren’t getting the results they expected.
The tools are there.
The language is there.
The intent is there.
What’s missing is how the tools are actually being used.
Here are five mistakes I see self-implementing teams make all the time, often without even realising it.
1. Rocks Become Business-As-Usual
Rocks are meant to create focus & drive meaningful progress over 90 days.
But I often see teams using Rocks as a to-do list.
“Hire a new team member.”
“Update the website.”
“Improve customer service.”
Those aren’t Rocks. That’s BAU.
When the Rocks tool is misused like this, it loses its power. Instead of forcing prioritisation & trade-offs, it simply tracks activity.
The result?
The team stays busy, but nothing really changes.
2. IDS Turns Into Discussion Instead of Resolution (IDS Tool Misused)
IDS is one of the most powerful tools in EOS when used properly.
But many self-implementing teams skip the most important part: Identify.
They jump straight into discussion.
The conversation sounds productive. Ideas get shared. Everyone contributes. But the real issue never gets clearly defined, so the solution is weak.
The same issue comes back next week.
That’s not an issue problem.
That’s an IDS problem.
If your Issues List isn’t getting shorter, your team isn’t solving issues, they’re just talking about them.
3. The Scorecard Becomes a Dashboard, Not a Decision Tool
Most teams I meet have a Scorecard.
The numbers are there.
They’re updated weekly.
They’re even colour-coded.
But then nothing happens.
When a number is red, it should trigger a question:
“Why is this off, and do we need to IDS it?”
Instead, teams note it and move on.
That’s not using the Scorecard. That’s observing it.
A properly used Scorecard drives behaviour. It creates early warning signals & feeds directly into the Issues List.
Without that, it’s just a dashboard.
4. The Weekly Meeting Becomes a Reporting Session
EOS meetings are designed to solve issues, not share updates.
But over time, I see meetings drift.
Updates get longer.
Reporting takes over.
IDS gets squeezed at the end.
The meeting still happens, but the purpose has changed.
When the Level 10 Meeting is misused like this, it feels heavy & unproductive. People leave knowing what’s going on, but nothing has actually moved forward.
Strong teams protect IDS time.
That’s where traction happens.
5. Accountability Is Assigned… But Not Enforced
On paper, accountability looks clear.
Roles are defined.
People have responsibilities.
Everyone “owns” something.
But in practice, it’s softer.
Missed commitments get explained instead of addressed.
Leaders step in and rescue.
Ownership gets blurred when things get hard.
The Accountability Chart is meant to create clarity and ownership. But if leaders don’t hold the line, it becomes a diagram, not a discipline.
Clear accountability isn’t about being harsh.
It’s about being consistent.
The Real Pattern
Self-implementing teams don’t fail because they don’t understand EOS.
They struggle because the tools are used partially, not properly.
- Rocks are set, but not sharpened
- IDS is done, but not completed
- Scorecards are reviewed, but not acted on
- Meetings happen, but don’t drive outcomes
- Accountability is defined, but not enforced
That gap is where traction gets lost.
Why This Matters
EOS is simple by design.
But simple doesn’t mean easy.
The real work is in how consistently & correctly the tools are used.
When they’re used properly, everything starts to click:
- Rocks get finished
- Issues get solved
- Meetings feel productive
- Leaders trust the system
When they’re not, it feels like hard work with limited progress.
If you’re self-implementing EOS and it feels like you’re doing everything right but not getting the traction you expected, it might not be what you’re doing… it’s how the tools are being used.
Because sometimes the biggest shift comes from tightening the basics.