Our Level 10 Meeting regularly blows past the 90-minute cap because updates and reporting eat up 45 minutes before we even get to IDS. How do we compress the first half of the agenda to protect 60 full minutes for problem-solving?

Question

Tyler Smith · Accepted Answer

The first 25 minutes of a Level 10 Meeting™ exist purely to report status, not to explain, justify, or solve problems. When reporting creeps past 25 minutes, it is almost always because the Integrator allows storytelling during the Scorecard, Rock Review, or Headlines.

Enforce strict conversational boundaries to protect your 60-minute IDS® window. On the Scorecard, a leader says only two things: their metric and whether it is on track or off track. No context, no backstory, no excuses. If the number is off track, the Integrator directs it straight to the Issues List with a single phrase: drop it down. The same rule applies to the Rock Review. Each owner states their Rock and announces on track or off track. If it is off track, drop it down.

Customer and employee headlines must follow the same constraint. Good news or bad news gets stated in one sentence. If it requires action or discussion, drop it down. The To-Do List review should take five minutes maximum. You read each task and ask done or not done. If a task is not done, leave it for one more week or push the root bottleneck to the Issues List.

By cutting all commentary from the first 25 minutes, your team will arrive at IDS with a full 60 minutes remaining. If the Integrator refuses to tolerate side conversations or defenses during the reporting track, the meeting will naturally finish under 90 minutes every single week.