tyler-smith.com · Questions & Answers

A key department head on our leadership team is pushing back hard on EOS, calling the Scorecard and Level 10 Meetings micromanagement. How do we address this resistance without blowing up the team?

Resistance to EOS® usually stems from one of two sources: fear of transparency or a fundamental lack of fit for the seat. When a leader calls Scorecards and Level 10 Meetings micromanagement, what they are usually saying is that they have historically operated as an autonomous silo without objective accountability.

Your first step is to clarify the purpose of the tools. EOS is not about policing hours or keystrokes. It is about providing total clarity so leaders can actually be autonomous. A weekly Scorecard Measurable gives that leader five numbers that prove they are winning without the owner looking over their shoulder. The Level 10 Meeting provides a structured venue to resolve their roadblocks rather than letting issues fester. Frame the tools as protection for their autonomy, not surveillance.

If the resistance persists after two or three cycles, you must run that individual through the People Analyzer. Evaluate them against your Core Values and assess whether they Get it, Want it, and have the Capacity to do it (GWC™).

Often, the loudest critic is someone who lacks the capacity for where the company is heading or someone whose ego rejects organizational alignment. You cannot allow a single executive to negotiate an exemption from the operating system. Doing so destroys accountability across the entire company. If they refuse to operate within the disciplines after honest coaching, you are facing a Right Seat or Right Person decision.

Category: EOS Implementation

← All questions