We are ready to roll Level 10 Meetings down to our department managers and frontline teams. What is the right sequence to roll this out so it does not turn into unproductive venting sessions?

Question

Tyler Smith · Accepted Answer

Rolling Level 10 Meetings down to your departmental teams is where the real leverage of EOS begins, but doing it prematurely or without structure creates operational chaos. Frontline teams do not have the context that the leadership team possesses. If you simply give them ninety minutes and tell them to solve problems, the meeting turns into a complaint session.

Follow this sequence to ensure a disciplined rollout:

First, verify that your leadership team has run pure Level 10 Meetings for at least two full quarters. If your senior leaders are still bleeding past ninety minutes or arguing during reporting, you have no business cascading the tool downward. Department heads must master the discipline as participants before they can lead it as facilitators.

Second, build departmental Scorecards and Accountability Charts before launching the meeting. A frontline Level 10 Meeting cannot function without measurable data. Every department needs five to ten measurable numbers that reflect daily execution, clear seats with five defined roles, and departmental Rocks. Without those rails, there is nothing objective to ground the meeting.

Third, have an executive sit in on the first four departmental meetings as an observer and timekeeper. Their job is not to solve problems for the team. Their job is to coach the department head on meeting discipline: cutting off storytelling, forcing issues to the list, and managing the clock.

Teach them that IDS is not venting. An issue must be tied to a process, a metric, or a Rock, and every solved issue must produce a binary to-do assigned to one person.