Our Level 10 Meeting reporting tracks keep bloating, taking 45 to 50 minutes instead of 25, which leaves our leadership team with barely half an hour for IDS. How does the Integrator shut down conversational drift during the reporting phase?

Question

Tyler Smith · Accepted Answer

The first 25 minutes of the Level 10 Meeting are engineered strictly for reporting numbers and progress, not for solving problems. When reporting drags out to 45 or 50 minutes, it is almost always because leaders hear an off-track metric or an incomplete task and immediately jump into defensive explanations or unsolicited advice.

The Integrator must police this boundary with zero hesitation. Run the reporting sections like an audit:

- On the Scorecard, the metric owner reads the label and says on track or off track. No context.
- On Rocks, the owner states on track or off track. No updates on meetings held.
- On Customer and Employee Headlines, share the fact in one sentence. No narrative.
- On To-Dos, answer done or not done. No excuses.

The moment any leader uses the word because, the Integrator cuts in: We are in reporting, not IDS. Drop it to the list. If an off-track item requires discussion, it gets added to the bottom of the Issues List in two to three words and the team moves instantly to the next item.

Protecting the 60-minute IDS block is non-negotiable. If you spend half the meeting reporting on what happened last week, you rob the business of the time required to solve the structural problems blocking next week.