Here is a leadership team whose Level 10 Meeting is close to flawless. Segue, Scorecard, Rock review, headlines, to-do list at ninety percent. IDS gets a real hearing every week. The meeting starts on time, ends on time, and everyone in it would rate it an eight or a nine. It has run this way for four quarters.
The business is not meaningfully different than it was a year ago.
Read that team's Issues List and you'd find nothing wrong with it. Every item is legitimate. Pricing inconsistency in the Midwest. The hiring backlog. A software migration that keeps sliding. But nothing on that list is the issue — because the actual issue is that the CFO and the VP of Sales have not trusted each other in two years, and neither of them is going to write that on a whiteboard on a Tuesday morning.
This is the most common way EOS quietly underdelivers. It is not a failure of the tools.
Three promises, unequal tooling
EOS makes three promises: Vision, Traction, and Healthy. Look at what backs each one.
Vision has the Vision/Traction Organizer — eight questions, two pages, shared by the whole leadership team. Traction has Rocks, the Scorecard, the Accountability Chart, and the Meeting Pulse. Both are supported by specific, teachable, repeatable instruments that work the same way in any company.
Healthy has the Issues List, IDS, quarterly conversations, and a general expectation that people will be straight with one another.
Notice what IDS actually is. Identify, Discuss, Solve is a conflict resolution protocol, and an excellent one — it takes a named conflict and drives it to a decision with an owner and a date. It has almost nothing to say about how a team becomes willing to name the conflict in the first place. EOS assumes that willingness is already in the room. When it isn't, nothing fails loudly. Everything just degrades quietly.
A team without trust doesn't stop doing IDS. It does IDS beautifully, on the wrong issues, indefinitely.
The pyramid EOS builds on but doesn't build
Patrick Lencioni's five behaviours of a cohesive team stack in a specific order, each one resting on the layer beneath it. Lay the EOS toolkit over the top and the pattern is unmistakable.
Results
Collective outcomes over individual ones. EOS: Company Rocks take precedence over departmental Rocks. Reviewed quarterly.
Accountability
Peers holding peers to standards. EOS: Scorecard, Rock completion, to-do percentage. Measured weekly.
Commitment
Disagree and commit, with clarity on what was decided. EOS: every IDS terminates in a to-do with an owner and a date. Tracked.
Conflict
Unfiltered debate about ideas. EOS: the "D" in IDS. Assumed.
Trust
Vulnerability-based; willingness to be wrong in front of your peers. EOS: Assumed.
EOS instruments the top three layers with real precision and assumes the bottom two. That is a defensible design decision rather than an oversight — Gino Wickman set out to build an execution system, not a therapy practice, and the discipline of that focus is a large part of why EOS travels so well. But it does mean the system's output is governed by a variable it does not manage.
What the gap looks like from inside
Three symptoms recur, and all three arrive disguised as execution problems.
| Symptom | What's actually happening |
|---|---|
| The sanitised Issues List | Real items, none of them the real one. The team solves genuine problems every week and the business doesn't move, because the constraint was never eligible for the list. |
| Rocks nobody believes in | False commitment, produced by a team that never had the argument. Everyone nods in the quarterly. The slippage shows up in week seven and gets explained as capacity. |
| Accountability that defaults upward | Nobody will challenge a peer directly, so every difficult conversation routes through the Integrator — who becomes a bottleneck for a function the team was designed to perform on itself. |
No amount of sharper Rock-setting fixes any of these. They are trust failures wearing execution costumes, and they will absorb an unlimited quantity of process improvement without responding to it.
Sequencing, not stacking
The practical answer is not to bolt team-health work on top of a running implementation as a wellbeing initiative. It is to do it early — before or alongside the Focus Day — so the tools arrive at a team already capable of using them honestly.
In practice that means a few specific things: personal histories, so the team knows each other as people before they have to disagree as executives; behavioural profiling, so difference reads as data rather than deficiency; an explicit working agreement about what productive conflict looks like on this team; and enough low-stakes practice at saying the awkward thing that the first high-stakes instance isn't the first attempt.
None of that is soft work, and teams who skip it don't save the time. They spend it later at a considerably worse exchange rate, wondering why a system that demonstrably works for thousands of other companies isn't working for theirs.
The honest summary
Nothing here is an argument against EOS. The tools are sound, the discipline is real, and the results for healthy teams are well documented. This is an argument about a precondition.
EOS is the operating system. A cohesive leadership team is what makes a group of people capable of running it. Install the first without the second and you get a beautifully instrumented machine that reports, accurately and every single week, on a business that isn't changing.
The five behaviours of a cohesive team are described in The Five Dysfunctions of a Team and The Advantage by Patrick Lencioni. EOS®, the Vision/Traction Organizer™, the Accountability Chart, IDS™, Rocks, and the Level 10 Meeting™ are tools of EOS Worldwide, described in Traction by Gino Wickman. The two bodies of work are independent; neither organisation endorses the other.
← Back to all articles