Our leadership team checks the boxes during our sessions, but they treat the EOS® tools as a separate administrative chore rather than our actual operating system. How do we break this compliance-only resistance?

Question

Tyler Smith · Accepted Answer

When a leadership team treats EOS® as an administrative chore rather than their actual operating system, you have a compliance problem. They are filling out their Rocks and updating the Scorecard just to avoid getting in trouble, but they are still running their departments using their old, chaotic habits.

To break this resistance, you must tie the tools directly to their daily relief. Stop allowing duplicate work. If a leader brings up an operational problem outside of the Level 10 Meeting™, refuse to solve it. Tell them to drop it on the Issues List.

Show them that the tools are designed to make their lives easier, not harder.

- Use the Scorecard to eliminate subjective guessing about department performance.

- Use the Accountability Chart to stop people from stepping on each other's toes.

- Use IDS® to solve chronic issues once and for all so they do not keep resurfacing.

If they continue to resist, use the People Analyzer™ to evaluate their fit. A leader who refuses to adopt the operating system is a core values or GWC™ issue. You cannot allow a double standard where some leaders run on EOS® and others run on their own rules.