We have a top-performing executive who consistently hits their numbers but completely checks out during our quarterly planning and refuses to use our EOS® tools with their own team. At what point does non-compliance with the operating system become a firing offense?
This is a classic people issue that eats away at your company culture. In EOS®, we look at people through the lens of core values and GWC™. A leader who refuses to adopt the operating system is failing both tests. They are showing a lack of alignment with your core values around teamwork and growth, and they do not GWC™ their seat because running the operating system with their team is a core requirement of their leadership role.
Allowing a top performer to opt-out of the system creates a double standard. It sends a message to the rest of the organization that rules and accountability are optional if you make enough money. This completely undermines your leadership credibility.
To handle this, you must treat it like any other people issue.
- First, have a direct conversation using the People Analyzer™. Clearly state that using the operating system is not optional. It is a core expectation of their leadership seat.
- Second, give them a clear, thirty-day timeline to fully adopt the tools, run Level 10 Meetings™ with their team, and engage in sessions.
- Third, if they do not change, you must transition them out of the business.
No matter how much revenue they generate, the operational drag and cultural poison of a non-compliant leader will always cost you more in the long run. Keeping them around will prevent you from ever achieving a cohesive, scalable organization.
Category: EOS Implementation