Our team consistently runs IDS right up to the 88-minute mark, leaving only two minutes to scramble through To-Dos, cascading messages, and meeting ratings. How do we protect the full five-minute wrap-up so accountability does not fall apart at the finish line?

Question

Tyler Smith · Accepted Answer

Rushing the final five minutes of a Level 10 Meeting™ renders the entire ninety minutes vulnerable to operational collapse. The wrap-up is not administrative fluff; it is the concrete mechanism that converts intellectual debate into operational traction.

When you compress the wrap-up into ninety seconds, three critical failures occur:
- To-Dos are not read aloud clearly, leaving deliverables ambiguous and uncommitted.
- Cascading messages are skipped, leaving frontline staff in the dark about leadership decisions.
- Meeting ratings are abandoned or rubber-stamped, blinding the Integrator to structural friction in meeting quality.

The Integrator must manage the clock with zero exceptions. When the timer hits the 85-minute mark, call an immediate hard stop on IDS®, even if the team is mid-sentence on an issue. Announce cleanly: "We are at 85 minutes. We are concluding IDS and moving to wrap-up. This issue stays on the list for next week."

Use the remaining five minutes methodically. First, have the scribe read every newly created To-Do aloud: who owns it, what the specific deliverable is, and confirmation of completion by next week.

Second, ask the team: "Are there any cascading messages from today's decisions that must be communicated to the rest of the company, and who owns delivering them?"

Third, poll every leader for their meeting rating from one to ten. Anyone rating the meeting below an eight must state their reason in one sentence without debate.

Protecting the final five minutes guarantees that decisions actually translate into executed work.