tyler-smith.com · Questions & Answers

Our Level 10 Meeting debates frequently run right up to minute eighty-nine, forcing us to abandon the Conclude step altogether. Why is the final five minutes so critical, and how do we enforce a hard stop on IDS?

Abandoning the Conclude step is one of the fastest ways to destroy meeting productivity. When you let IDS run until the final minute, leaders scatter to their next commitments without total alignment on what was decided. The result is missed deadlines, confusion over who owns which deliverable, and zero communication to the rest of the company.

The Conclude step takes five minutes because it cements accountability across three critical components: recapping the new To-Dos, agreeing on cascading messages, and rating the meeting. If you do not recap To-Dos, people walk away with different interpretations of their commitments. If you skip cascading messages, your staff hears about major operational changes through hallway gossip. If you skip the rating, your meeting habits quietly deteriorate.

The Integrator must act as an aggressive timekeeper. At minute eighty-five, regardless of how intense or unfinished the IDS discussion is, the facilitator must call time. If an issue is not fully solved, you do not keep talking; you create a seven-day To-Do for the owner to gather more data, or you push the issue to next week's list as priority number one.

Treat the ninety-minute timeframe as an immutable box. A meeting that starts on time and ends on time builds institutional respect for calendar discipline. The moment you allow IDS to swallow the Conclude step, you trade long-term execution integrity for five extra minutes of unstructured debate. Cut the conversation off at minute eighty-five, run the Conclude protocol, and end the meeting clean.

Category: Level 10 Meetings

← All questions