What is the correct way to handle a critical leadership team member who actively resists adopting the EOS tools and claims the disciplines are slowing down the business?
Resistance to EOS tools usually comes in two forms: genuine misunderstanding or a defense mechanism against accountability. When an executive claims that weekly Scorecards, Level 10 Meetings, and Rocks are corporate bureaucracy that slows them down, what they are usually saying is that they prefer operating in the shadows where their performance cannot be measured.
Start by addressing the resistance directly in your next quarterly conversation or one-on-one. Walk through the tools and explain the standard: EOS is the operating system of this company, not an optional experiment. It is not up for debate whether we run Level 10 Meetings or report weekly numbers. If they struggle with the mechanics, offer coaching. Often, high performers who resist the tools simply feel micromanaged because their seat accountabilities or Scorecard measurables were poorly defined.
However, if the coaching is provided and the executive continues to skip weekly disciplines, bad-mouth the process to their department, or refuse transparency, you have a People Analyzer issue. They are either violating your Core Values or refusing to accept the requirements of their seat. You cannot permit an executive to opt out of the system while holding everyone else accountable. If they refuse to run on the system after sixty days of clear expectations, you must execute the three-strike rule and replace them.
Category: EOS Implementation