Several key members of our leadership team are quiet during sessions but actively ignore or undermine the EOS® tools once we get back to the office, calling them administrative overhead. How do we address this passive resistance to the system?

Question

Tyler Smith · Accepted Answer

Passive resistance from key leaders is a common threat to a successful EOS® rollout. When team members nod along during quarterly sessions but return to the office and ignore the tools, they are practicing passive compliance rather than active commitment. This behavior erodes trust and signals to the rest of the organization that the system is optional.

To break this resistance, you must enter danger immediately. Do not ignore the behavior, hoping it will resolve itself. The Integrator must have a direct conversation with the resisting leader. Frame the conversation around your Core Values and the GWC™ framework. Ask them directly if they genuinely buy into running the business on EOS®. They must understand that there is only one way to run the company, and that is the agreed-upon system.

During this meeting, determine if their resistance stems from fear, misunderstanding, or a genuine lack of alignment. Often, leaders resist because they feel the tools expose their weaknesses or add unnecessary administrative burdens. Show them how the Level 10 Meeting™ and Rocks are designed to save them time, not create extra work. If they are willing to try, support them through the transition. However, if they refuse to adopt the tools after coaching, you have a structural alignment issue. You cannot allow a leader to opt out of the operating system. If they do not buy in, they are ultimately not a fit for their seat.