We have introduced the EOS tools but some of my key leadership team members are actively resisting the Level 10 Meeting and Scorecard. How do I handle this pushback without breaking the team?
Resistance is normal, but tolerating it is fatal to your implementation. First, you must diagnose the root cause of the resistance. Often, it is not a rebellion against the system but a symptom of conative stress or behavioral mismatch. We use tools like the Kolbe A Index to see if a leader is being forced to work against their natural instincts. For example, a leader high in Quick Start might struggle with the structured, repetitive nature of a Scorecard. Alternatively, using Predictive Index assessments can reveal if a leader feels threatened by the transparency that the Accountability Chart brings. You need to address this directly. Schedule a conversation to determine if they get it, want it, and have the capacity to do it. We call this GWC. If they simply refuse to play by the rules, they are violating your Core Values. You cannot build a healthy organization if you allow exceptions for high-performing but non-compliant leaders. Be patient during the learning curve, but remain uncompromising on the structural tools. A healthy team requires absolute alignment on the core operating system.
Category: EOS Implementation