Our leadership team is verbally agreeing to the EOS® tools in our sessions, but they are secretly failing to cascade them or use them in their own departments. How do we break through this passive resistance and make the tools non-negotiable without micromanaging?
Passive resistance is the silent killer of any operating system. When leaders nod their heads in the quarterly session but return to their old, disorganized habits on Monday, your implementation is dead on arrival. This happens because the team sees the tools as a bureaucratic burden rather than a mechanism for execution. To break this resistance, you must make the use of the tools a non-negotiable standard of performance.
Start by addressing the root cause. Often, leaders resist because they lack the conative alignment for their seats. Use the Kolbe Index to assess their natural problem-solving styles. If a leader has a low Follow Thru score, they will naturally struggle with structured systems like the weekly Level 10 Meeting™ and will need support or a different structural setup to stay on track.
Next, tie their performance directly to the system. If a leader does not run a weekly Level 10 Meeting™ with their department or fails to keep their Scorecard updated, it must be treated as a direct performance issue, not a minor slip. You must show them that using the tools is how they demonstrate they GWC™ their seat. If they refuse to run the system, they are actively choosing to opt out of the company's future. Keep it simple, hold the line, and replace those who refuse to grow.
Category: EOS Implementation