Our weekly Level 10 Meeting™ routinely runs long because my leadership team drags out the scorecard and headlines, leaving us fifteen minutes for real problem-solving. How do we hard-cap this under ninety minutes without cutting corners?

Question

Tyler Smith · Accepted Answer

When a Level 10 Meeting™ runs over ninety minutes, it is because your team is treating the reporting section like a status update. This kills your meeting efficiency and steals valuable time from your IDS® session, which is where real value is created. To fix this, you must enforce a strict, non-negotiable time limit on the first thirty minutes of the meeting. The scorecard, Rock review, customer/employee headlines, and to-do list are for reporting only. If a number is red, a Rock is off track, or an update requires more than thirty seconds of explanation, do not discuss it. Drop it to the issues list. The Integrator must act as a firm timekeeper. When a leader starts explaining why a scorecard metric is off, the Integrator must cut them off immediately and say, drop it to the issues list. This keeps the reporting phase fast, objective, and quiet. By protecting your sixty minutes of IDS® time, your team can focus on solving the root causes of your biggest issues rather than listening to narrative updates. Keep the reporting tight, put the details on the issues list, and end the meeting exactly at ninety minutes every single week.