tyler-smith.com · Questions & Answers

Our weekly Level 10 Meeting™ is routinely stretching past the ninety-minute mark because our team gets bogged down in storytelling and status updates during the scorecard and rock reviews. How do we ruthlessly trim the fat to guarantee we protect our ninety-minute limit while reserving bulk time for actual IDS®?

A Level 10 Meeting™ that routinely runs over ninety minutes is a symptom of poor discipline and a lack of respect for the team's time. The solution is not to extend the meeting, but to ruthlessly enforce the timeline and cut out the storytelling.

To fix this, the Integrator must act as a strict timekeeper. The first three agendas on the docket, the check-in, scorecard review, and rock review, must take no more than fifteen minutes combined. This is a reporting section, not a discussion section. If a scorecard metric is off-track or a Rock is behind, the only acceptable response is to drop it to the Issues List. Do not allow anyone to explain why a number was missed or how they plan to fix it. Simply say, drop it, and move on.

The same applies to the people headlines and the to-do list. Spend five minutes here, reporting only. This leaves you with a solid sixty minutes for actual IDS®.

When you reach the IDS® portion, prioritize the list immediately. Only solve the top three most critical issues first. Never start from the top of the list just because it is there. If the team starts telling long-winded stories during the discussion, the facilitator must interrupt and ask for the specific issue. Keep the conversation focused on identifying the root cause, discussing options, and solving the issue permanently. Keep it tight, keep it moving, and end on time every single week.

Category: EOS Implementation

← All questions