We have successfully run EOS® at our leadership level for six months, but our middle managers are highly resistant to cascading the system to their teams because they view it as extra administrative homework. How do we overcome this resistance and make the cascade feel like a relief rather than a burden?

Question

Tyler Smith · Accepted Answer

Middle-management resistance to cascading EOS® is incredibly common and almost always stems from a misunderstanding of the system's purpose. If your managers view the Level 10 Meeting™ and Scorecard as extra homework, it means they see them as reporting tools for leadership rather than management tools for themselves.

To overcome this, you must change how you introduce the cascade. Do not frame it as a top-down mandate to track more metrics. Instead, show your middle managers how running on EOS® will solve their biggest daily frustrations.

A proper Level 10 Meeting™ is designed to save time, not waste it. Explain that by committing to a highly structured ninety-minute meeting once a week, they can eliminate the constant stream of ad-hoc status updates, endless email chains, and unproductive meetings that disrupt their days.

Start the cascade process slowly. Do not expect them to master every tool overnight. Introduce the Level 10 Meeting™ first. Let them experience the relief of a structured, problem-solving environment. Once they see how much faster they can resolve team issues, introduce the weekly Scorecard with just three to five critical metrics.

Show them that the Scorecard gives them immediate visibility into their department, allowing them to manage by exception rather than micro-managing. When middle managers realize that EOS® gives them more control, better results, and less daily firefighting, the resistance will evaporate.