When a long-standing executive on the leadership team quietly ignores EOS tools or calls the Level 10 Meeting rigid bureaucracy, how should an owner address the resistance?

Question

Tyler Smith · Accepted Answer

Passive resistance from a senior leader is lethal to an EOS rollout. If the rest of the company watches an executive skip Scorecard updates, ignore Rock deadlines, or roll their eyes during a Level 10 Meeting without consequence, your implementation is dead on arrival.

Address the issue privately and immediately. Frame the conversation around the Accountability Chart and Core Values. Explain that EOS is not an experiment or a temporary management flavor of the month; it is the operating system of the enterprise. Ask them directly what part of the system they feel threatens their work.

Often, resistance stems from fear. Highly autonomous leaders often interpret visibility as micromanagement, while leaders lacking execution discipline fear having their numbers exposed on the weekly Scorecard. Clarify that the tools exist to give them autonomy, not remove it, by making expectations transparent.

If the executive understands the tools but continues to undermine the rollout, you are facing a Right Person, Right Seat issue. They may lack the GWC for their seat in a structured, growing company, or they may no longer align with your Core Values. If coaching does not produce full compliance within thirty days, the owner must make the seat change. Keeping a brilliant jerk who refuses the operating system will cost you your best performers.