We have run our leadership Level 10 Meetings successfully for six months and now want to roll the meeting down to our frontline departments. What mistakes should we avoid to prevent our managers from turning it into a status report?

Question

Tyler Smith · Accepted Answer

The biggest danger when cascading the Level 10 Meeting down to departmental tiers is allowing managers to treat the ninety minutes as a routine status update. The power of a Level 10 Meeting lies in IDS, where sixty of the ninety minutes are dedicated to solving root problems. When departmental managers fail to grasp this, the meeting degenerates into people reading their to-do lists aloud.

To avoid this failure mode, train your departmental managers thoroughly before their first meeting. Ensure each department has its own localized Scorecard with numbers that reflect their direct daily outputs, not high-level company revenue. If a customer service team looks at the company-wide net profit margin, they have zero control over the number. Give them first-response time, ticket resolution volume, and customer satisfaction scores.

Second, insist on absolute adherence to the agenda and timing. Managers often abandon the Segue, speed-read the Scorecard, and spend forty minutes debating a non-issue without officially dropping it to the Issues List. Require them to report Scorecard metrics and Rock statuses as strictly on track or off track, with zero editorial comment. If a metric is off track, it goes straight to the bottom of the list.

Finally, sit in on their first few sessions as an observer. Do not run the meeting for them, but provide direct feedback afterward on whether they spent their time solving systemic issues or just talking about work.