Some of our leadership team members are quietly resisting using the EOS tools, treating the weekly meetings and Rock tracking like an administrative chore rather than a way to run the business. How do we handle this passive resistance without causing a blowup that derails our implementation?

Question

Tyler Smith · Accepted Answer

Passive resistance is a silent killer in any EOS® rollout. It usually manifests as leaders showing up to the Level 10 Meeting™ without their numbers updated, ignoring their Rock milestones, or refusing to log issues in the IDS® queue until the last minute. They are hoping if they drag their feet long enough, this will turn into another management fad that simply passes away. You must address this immediately and directly. Start by separating the person from the tool. Sit down with the resisting leader and ask them why they feel the tool is a chore. Often, resistance is driven by fear of exposure. Under the EOS® framework, there is nowhere to hide. A weak leader hates a transparent Scorecard and a clearly defined Rock because their lack of results becomes highly visible to the entire team. Frame the conversation around alignment and core values. Remind them that consistent use of the tools is not optional. It is the one way we run the business. If they refuse to adopt the tools, they do not GWC™ their seat. To build a business ready for a clean exit, you need a leadership team that is completely aligned. If a leader continues to resist the system after clear feedback, they are telling you they do not fit the future of the company. You cannot scale a company or prepare it for a sale with leaders who choose which rules to follow. Address the behavior, call out the passive-aggressive compliance, and make it clear that running on EOS® is a team sport.