When cascading EOS to departmental teams, managers often complain that weekly Level 10 Meetings create administrative overhead and meeting fatigue. How do we keep lower-tier rollouts lean and effective?

Question

Tyler Smith · Accepted Answer

When departmental teams complain that the Level 10 Meeting™ causes administrative bloat, it is almost always because their managers are running the meeting incorrectly. They are turning a ninety-minute tactical execution session into a meandering status report where people read updates aloud.

The fix is strict adherence to the ninety-minute agenda and aggressive time management. The first twenty-five minutes must be brisk: good news, Scorecard review, Rock review, customer and employee headlines, and the To-Do List. There is zero discussion allowed during these sections. Numbers and Rocks are reported as either on track or off track. Any commentary immediately gets dropped down to the Issues List.

Departmental Level 10s must spend sixty full minutes on IDS. If a team has no real issues to solve, the meeting should not drag out to fill the time. End it early and give people their time back. Furthermore, departmental Scorecards should contain no more than five to ten numbers that directly reflect frontline activity, such as outbound calls, tickets closed, or error rates. Do not burden supervisors with complex corporate metrics they cannot control.

Finally, make it clear that a well-run Level 10 Meeting eliminates the dozens of chaotic hallway interruptions, emergency Slack threads, and unfocused ad-hoc check-ins that consume everyday work. When managers realize the Level 10 actually buys back five hours of fragmented time each week, meeting fatigue disappears.