We rolled out departmental Level 10 Meetings to our middle managers, but their sessions have devolved into mechanical task updates where nobody solves real problems. How do we train department heads to facilitate real IDS rather than running a status update?

Question

Tyler Smith · Accepted Answer

Departmental Level 10 Meetings fail when supervisors treat them as administrative inspection sessions rather than problem-solving workshops. Frontline managers often grew up in environments where meetings were used to check up on workers. They naturally default to asking each person what they did yesterday, turning ninety minutes into pure waste.

To fix this, the Integrator must coach department heads on the difference between status reporting and the EOS® meeting pulse. The first twenty-five minutes of the agenda, covering the Segue, Scorecard, Rock review, Customer Headlines, and To-Dos, exist solely to surface problems. They are quick reporting tracks designed to highlight what is broken. They are not conversations.

Train your department supervisors to aggressively cut off storytelling during reporting. When a frontline technician or customer service rep starts explaining a delayed task, the supervisor must say one sentence: Let us drop that to the Issues List.

Once reporting is locked down in twenty-five minutes, the remaining sixty minutes belong to IDS® (Identify, Discuss, Solve). Teach managers how to facilitate the Identify step. Middle managers love to jump immediately to Discuss because it feels productive to debate symptoms. Force them to ask: What is the specific root cause? Is this an unclear expectation, a broken process, or a capacity constraint?

Finally, have your Integrator sit in on departmental Level 10 Meetings as an observer once a month. Provide immediate feedback on meeting cadence, timekeeping, and whether the manager solved root issues or merely managed to-do lists. Departmental mastery requires deliberate facilitation training, not passive hope.