When we roll the Level 10 Meeting down to departmental teams, their meetings constantly degenerate into administrative status reports where nobody brings real problems to the Issues List. How do we teach managers to run a true departmental Level 10?

Question

Tyler Smith · Accepted Answer

Departmental Level 10 Meetings fail because managers default to what they know: status reporting. They use the meeting to justify their existence instead of solving friction. When supervisors spend eighty minutes explaining what their teams are working on, they have turned an accountability pulse into an expensive update session.

To fix this, you must train managers on the 25/65/10 time allocation. The first twenty-five minutes are pure reporting: good news, Scorecard, Rocks, customer and employee headlines, and the To-Do list. No discussion is permitted. A metric is either on track or off track. A Rock is either on track or off track. If an item is off track, it drops directly to the Issues List. The next sixty-five minutes are dedicated exclusively to IDS. The final five minutes are for Conclude.

Managers often claim their departments do not have enough issues to fill sixty-five minutes. That is a leadership failure, not operational perfection. Friction exists every day in handoffs, quality errors, client complaints, and missed deadlines. Train managers to look at their departmental Scorecard: any metric that misses its goal two weeks in a row is an automatic issue. Any blocked Rock milestone is an issue. Any process breakdown is an issue.

Have the Integrator attend departmental Level 10 Meetings once per quarter as an observer, not a participant. Score the meeting on strict adherence to the Level 10 Meeting Agenda. If the team spends more than twenty-five minutes before reaching IDS, or if they talk about status instead of solving root causes, step in and reset the standard. A well-run departmental pulse produces solved problems and clear seven-day To-Dos, not lengthy verbal reports.