We have successfully cascaded Level 10 Meetings™ down to our frontline departments, but our managers are complaining that a ninety-minute weekly meeting is too heavy a tax on their operational staff. How do we run highly effective departmental Level 10 Meetings™ in a shortened sixty-minute format without breaking the EOS® framework?

Question

Tyler Smith · Accepted Answer

When cascading the Level 10 Meeting™ down to frontline or departmental teams, a ninety-minute block can sometimes feel excessive and lead to meeting fatigue. It is completely acceptable to compress the departmental meeting to sixty minutes, but you must do so by scaling the agenda proportionally, not by skipping sections.

To run a sixty-minute departmental pulse, use a modified schedule. Allocate five minutes to the segue, fifteen minutes to the reporting review (covering the Scorecard, Rock progress, and customer or employee headlines), five minutes to review the previous week's to-dos, thirty minutes for IDS®, and five minutes to wrap up.

The secret to making this shorter format work is aggressive prioritization on the Issues List. Frontline teams should only keep highly tactical, immediate obstacles on their list. If an issue requires a deep strategic debate, it does not belong in a sixty-minute frontline meeting. It should either be solved offline by the department head or escalated to the leadership team's Issues List.

Keep the reporting section crisp. There should be zero storytelling during the scorecard and rock review. If a number is off-track, drop it to the Issues List immediately. By strictly enforcing this discipline, you keep the meeting fast, focused, and high-energy, ensuring your operational teams get the alignment they need without losing precious production hours.