Several members of our leadership team comply with the EOS tools during sessions but privately treat them as administrative chores, ignoring them during the workweek. How do we turn passive compliance into genuine ownership?

Question

Tyler Smith · Accepted Answer

Passive compliance is worse than outright resistance because it masks execution failure until quarter end. When leaders view EOS as extra work on top of their real jobs, it means they do not view EOS as the way work gets done. Start by confronting the behavior directly during your Level 10 Meeting. When someone misses a Rock milestone or a Scorecard number and offers an excuse about being too busy with daily operations, call it out. Remind them that the tools are not a parallel reporting requirement; they are the framework for running their seat.

Next, look at the Accountability Chart. People who treat the operating system as optional administrative overhead often do not truly GWC their seats. They may get it and want it, but they lack the capacity to think systematically. If an executive cannot run their department through five clear measurables and a handful of quarterly Rocks, they are operating as a high-priced technician, not a true departmental leader.

Finally, stop solving their problems outside the system. When a manager comes to the owner with an operational crisis, do not resolve it in an ad-hoc hallway conversation. Direct them to put it on the Level 10 Meeting Issues List and solve it through IDS. Once leaders realize that decisions, budget, and resources only move through the EOS cadence, passive compliance ends. They either step up into genuine ownership or demonstrate they are in the wrong seat.