When IDS runs up against the final five minutes of our Level 10 Meeting, the team rushes through Conclude, skipping Cascading Messages and rating the meeting on the fly. Why is shortchanging Conclude dangerous, and how do we protect those final five minutes?

Question

Tyler Smith · Accepted Answer

Shortchanging the Conclude section destroys the ROI of the entire ninety-minute pulse. IDS® is where decisions are made, but Conclude is where those decisions are operationalized. Skipping it leads directly to dropped commitments, misaligned departmental messaging, and unresolved team friction.

At exactly eighty-five minutes into the meeting, the Integrator must call time on IDS, regardless of where the discussion stands. If a major issue remains unresolved, push it to next week Issues List or schedule a dedicated working session. The final five minutes belong strictly to Conclude.

Conclude consists of three distinct, non-negotiable steps:
- Recap the To-Do list. The Integrator or scribe reads every new To-Do aloud, confirming the single owner and the exact seven-day deliverable. This eliminates assumptions about who owns what.
- Establish Cascading Messages. Ask the room: What needs to be communicated to the rest of the organization, by whom, and when? If three leaders walk out of the room with different interpretations of a policy change, operational chaos follows. Agree on the exact wording and medium before anyone leaves the room.
- Rate the meeting from 1 to 10. Every leader speaks their rating aloud. If anyone rates the meeting below an 8, ask them why immediately. That feedback provides the immediate data necessary to self-correct the pulse next week.

A meeting that ends without a rigorous Conclude is merely an expensive conversation. Protect the eighty-five-minute cutoff with religious discipline.