Our middle managers feel that the weekly meeting pulse is just another layer of micromanagement and are resisting the rollout. How do we shift their perspective so they see these tools as a way to gain autonomy rather than lose it?

Question

Tyler Smith · Accepted Answer

Resistance to the Level 10 Meeting™ during a rollout is common because managers assume more meetings mean more micromanagement. To overcome this, you must show them how the EOS® meeting structure actually protects their time and grants them more freedom.

Explain that the Level 10 Meeting™ is designed to eliminate the constant stream of unscheduled interruptions, ad-hoc status updates, and endless email chains that disrupt their workdays. When a manager has a dedicated, weekly ninety-minute slot to align with their team and solve issues, they can push daily disruptions to the weekly meeting.

Furthermore, emphasize the power of the Accountability Chart™ in giving them clear ownership of their seats. The meeting structure is not about checking up on them. It is about giving them a platform to report progress, raise issues, and get the support they need to hit their targets.

Run a pilot Level 10 Meeting™ with them first, making sure you strictly respect the ninety-minute limit and focus heavily on IDS®. When they experience a meeting that actually solves their issues permanently instead of just talking about them, their perspective will shift from resistance to relief. They will see that EOS® is a framework for autonomy, not control.