During the Level 10 Meeting segue, our leaders use their business best news to sneak in project status updates and start debating problems early. How do we keep the segue strictly to wins without bleeding into the business agenda?

Question

Tyler Smith · Accepted Answer

The segue exists for one purpose: transition your leadership team from working in the business to working on the business. It is a psychological gear shift, not an operational update. When leaders sneak project statuses into their business best, they are attempting to justify their week or preempt criticism. That ruins the pulse before it starts.

The Integrator must police the boundary immediately. A business win is a completed milestone, a closed deal, a major operational victory, or positive feedback. It is an outcome, not an ongoing project status. The moment a leader begins narrating a process by detailing phase obstacles or active struggles, cut them off.

Use this standard: state one personal good news and one business good news in thirty seconds total. If a leader tries to unpack an active project or raise a concern, interrupt and ask a simple question: Is that a win, or is that an issue?

If it is a win, acknowledge it in one sentence and move to the next person. If it is an issue, add it directly to the Issues List for IDS® later in the meeting. Do not let them explain the context or debate it during the first five minutes.

Enforce a strict sixty-second limit per person around the table. The entire segue must finish inside five minutes. If your team cannot share a quick win without diving into status reporting, you have an Accountability Chart issue where leaders lack other forums to celebrate wins, or an Integrator who is afraid to cut people off. Set the standard and hold the clock.