Several members of our leadership team are quietly resisting the EOS® tools, claiming they are too bureaucratic and slow down our fast-moving culture. How do we handle this passive resistance during our rollout?

Question

Tyler Smith · Accepted Answer

Quiet resistance is a major threat to your rollout. It usually manifests as leaders arriving late to Level 10 Meetings, failing to update their Scorecard numbers on time, or writing vague Rocks that cannot be measured. This behavior is rarely about the tools being bureaucratic. It is almost always about a fear of accountability and exposure.

To break through this resistance, the leadership team must use EOS® tools consistently to avoid breakdowns in implementation. Do not negotiate on the core disciplines. If a leader claims the Scorecard is a waste of time, demand they prove it by showing how they track their department performance without it. They will not be able to do so.

When a leader resists the tools, run them through the GWC™ evaluation. Do they get the tool, do they want the tool, and do they have the capacity to work within a highly transparent, accountable system? If they do not want to work in an environment of complete accountability, they do not GWC™ their seat. You cannot scale a business or build it for a clean exit if key leaders are actively choosing to operate in the dark. Address this directly during your IDS® sessions.