Our weekly segue is supposed to kick off the meeting with positive energy, but our leaders use their good news as a launching pad to brag about new operational processes or software they built, which instantly sparks an unscheduled, ten-minute technical debate. How do we keep the segue strictly about quick connection without letting operational updates eat our meeting time?

Question

Tyler Smith · Accepted Answer

The purpose of the Level 10 Meeting™ segue is to transition your team from working in the business to working on the business. It is a quick tool to share personal and professional good news, build connection, and bring energy into the room. It is not an invitation to deliver a project status report or pitch a new operational workflow. When a leader uses their good news to launch into a technical monologue, the facilitator must step in immediately. If a leader says, "My good news is we finally deployed the new customer portal, and let me tell you how we configured the API," the facilitator must say, "Great win. That belongs on the Issues List. Next." Do not let them explain the details. Keep the transition moving. Every leader has exactly thirty seconds to share their good news. If the news sparks curiosity or raises a technical question, it must be captured as an issue to be addressed during IDS®. Training your team to respect the boundaries of the segue maintains the tight, seventy-five or ninety-minute cadence of your weekly pulse. It protects the operational rhythm and prevents early-meeting drift from hijacking your problem-solving time.