We have a highly competent but highly defensive leadership team member who resists using the EOS tools because they feel the radical transparency of the Scorecard and Accountability Chart is a personal attack. How do we handle this specific resistance without letting one defensive executive derail the rollout?

Question

Tyler Smith · Accepted Answer

Resistance born of fear is common when introducing radical transparency. When an executive pushes back, it is usually because they are terrified that the numbers and clear boundaries of the Accountability Chart will expose their perceived shortcomings.

First, address the behavior directly outside of the group sessions. The Integrator must have a private conversation to explain that the tools are not designed to be a weapon, but an objective mirror. Frame the transition as a shift from subjective blame to objective management. Make it clear that tracking numbers is a tool for support, not a system for micromanagement.

Second, hold the line on the tools during your Level 10 Meeting™ sessions. Do not make exceptions for their department or allow them to skip reporting their weekly metrics. If you allow one person to opt out, you compromise the integrity of the entire operating system and create resentment among the rest of the team.

Third, evaluate the situation using the GWC™ framework. Does this person truly get, want, and have the capacity to operate in a highly accountable culture?

If their defensiveness turns into active sabotage, gossip, or passive-aggressive resistance, you have a People Issue. A leadership team member who refuses to embrace accountability cannot remain in their seat. You must protect the healthy culture of the rest of your team. Use your implementer to help run a clean process, but be prepared to make the hard decision if the defensive behavior does not change.