We installed the weekly Level 10 Meeting for our leadership team, but department heads are still holding their old weekly status meetings and one-on-ones, claiming the L10 does not give them enough operational detail. How do we eliminate these duplicate meetings?

Question

Tyler Smith · Accepted Answer

Holding legacy status meetings alongside the Level 10 Meeting is a classic symptom of poor meeting discipline and a lack of trust in the EOS process. Leaders keep their old meetings on the calendar as safety blankets because they do not yet believe the weekly pulse will resolve their operational headaches. The result is severe calendar bloat, meeting fatigue, and fragmented decision-making.

The Integrator must establish a hard operational mandate: the Level 10 Meeting is the exclusive venue for weekly cross-functional problem solving. Give the team permission to kill every recurring status meeting for thirty days. Inform department heads that if an operational issue needs cross-departmental coordination, it belongs on the Level 10 Issues List, not in a separate thirty-minute ad hoc sync.

Next, examine why your department heads feel the L10 lacks operational detail. Often, it is because the leadership team is hoarding low-level operational weeds on the executive Issues List instead of cascading the Level 10 format down to departmental teams. Department heads need their own localized Level 10 Meetings where their front-line supervisors can IDS tactical problems specific to their functional areas.

One-on-one meetings should never be used for status reporting. If a manager holds a one-on-one, it must focus on quarterly coaching, GWC alignment, and personal development, not reviewing project task lists. When you force all operational problem-solving through the disciplined rhythm of the Meeting Pulse, duplicate meetings disappear naturally, freeing up hours of executive capacity.