A few members of our leadership team are pushing back on the rigid structure of EOS®, calling the Level 10 Meeting™ and weekly Scorecards bureaucratic overhead that slows down their creative process. How do we handle this internal resistance without forcing compliance?

Question

Tyler Smith · Accepted Answer

Resistance to the EOS® tools almost always stems from a fear of transparency or a misunderstanding of what creative freedom actually requires. When high performers or creative leaders complain about bureaucracy, they are usually reacting to a feeling of being micromanaged.

To handle this, do not pull rank and demand compliance. Instead, run the IDS® process on the resistance itself. Ask them specifically which tool is slowing them down and why. If they object to the weekly Scorecard, ask them how they propose to prove they are succeeding in their seat without objective data. Often, they will realize that the alternative to a Scorecard is subjective management, which actually leads to more micromanagement and constant oversight.

You must reframe these tools. Explain that the Level 10 Meeting™ is not an administrative chore, but a tool of liberation. By dedicating ninety minutes of tight, structured focus once a week, you eliminate hours of ad-hoc meetings, disruptive emails, and alignment checks throughout the week. Structure creates the sandbox where creativity can safely happen.

If a leader continues to resist after you have addressed their concerns, you are likely looking at a GWC™ issue or a lack of alignment with your Core Values. A leader who refuses to be accountable to the team through data and structured meeting rhythms is often protecting a silo. You must decide if you want to run a collaborative, scalable business or a collection of individual kingdoms.