During the first twenty minutes of our Level 10 Meeting, leaders constantly interrupt Scorecard, Rocks, and Headlines to explain context, turning quick reporting into unstructured discussion. How does the Integrator eliminate agenda drift and protect the reporting block?

Question

Tyler Smith · Accepted Answer

The first twenty minutes of a Level 10 Meeting exist exclusively for data verification, not discussion. When leaders begin explaining why a Scorecard metric dropped or why a customer headline occurred, they steal time directly from the sixty-minute IDS block. By the time the team reaches actual problem-solving, mental energy is depleted and the agenda has unraveled.

The Integrator must police this boundary mechanically. When a leader starts offering backstory on a red metric, cut them off mid-sentence with a single phrase: Drop it to the list. Do not allow apologies, justifications, or side commentary. The reporting cadence must be binary: on track or off track, done or not done. If a metric is off track, the only acceptable response from the seat owner is off track, followed immediately by the Integrator asking if it needs to be added to the Issues List.

Eliminating agenda drift requires teaching the team that logging an issue is not a punishment. It is simply parking the topic so the entire leadership team can focus on it collaboratively during IDS. Remind the room that solving problems without prioritizing them first creates chaos. If an issue is critical, it will get voted into the top three during the sixty-minute block. If it is not in the top three, spending reporting time debating it is pure operational waste.