What should I do when my leadership team actively resists using the EOS tools and claims the process is too rigid?

Question

Tyler Smith · Accepted Answer

When your leadership team resists, you must diagnose the root cause of the friction. Resistance rarely stems from laziness. Usually, it is a mismatch between how a person is naturally wired to take action and how the tool is being introduced.

To solve this, leverage the Kolbe A Index. This tool measures innate conative strengths, revealing whether a team member is a high Fact Finder who needs deep data, a high Follow Thru who needs structured systems, or a high Quick Start who thrives on chaos and resists structure. If you force a high Quick Start to build highly detailed processes without support, they will fight it. If you ask a high Fact Finder to jump into a new tool without explanation, they will freeze.

Identify where the friction lies. If the resistance is purely behavioral, review their alignment with your Core Values. If they do not share your Core Values, they are the wrong person on the bus. But if they share your values and GWC their seat, use their conative profiles to adapt how you implement the tools.

You must also hold the line as the owner. EOS is not optional. Explain that the tools are there to create freedom, not restriction. Once the team experiences the efficiency of a properly run Level 10 Meeting, the resistance usually dissolves. Focus on small, early wins to build momentum.