Our Level 10 Meeting™ is consistently bleeding past the ninety-minute mark because my team treats the reporting sections like an updates session rather than a hard data check. How do we claw back our calendar and protect the seventy percent of the meeting that belongs to IDS®?
The Level 10 Meeting™ is ninety minutes for a reason. If your meeting is routinely running long, it is almost always because your team is dragging out the reporting sections. Reporting is meant to be a rapid-fire check, not a narrative storytelling hour.
To fix this, enforce a strict time limit on the first thirty minutes of the agenda. The Segue is five minutes. The Scorecard is five minutes. Rock review is five minutes. Customer and employee headlines are five minutes. The To-Do list is five minutes.
During the Scorecard, Rock, and To-Do reviews, there is absolutely no discussion allowed. If a metric is red, or a Rock is off track, or a To-Do is not done, you do not explain why. You simply say off track or not done, and the Integrator immediately drops that item down to the IDS® list.
By cutting out the explanations, defensive maneuvering, and status updates, you will easily preserve sixty minutes for IDS®. This is where the real work happens. If a team member starts telling a story during the reporting phase, the meeting leader must politely but firmly cut them off and say, let us drop that to IDS®. Keep the discipline tight, and your meetings will consistently finish on time.
Category: EOS Implementation