During our leadership Level 10 Meeting, an issue frequently turns into a hyper-detailed technical debate between two department heads, forcing the other five leaders to sit in silence for twenty minutes. How should the facilitator cut off these two-person rabbit holes?

Question

Tyler Smith · Accepted Answer

A Level 10 Meeting exists to solve issues requiring the collective brainpower of the leadership team. When an issue degrades into two leaders negotiating technical specifications, software settings, or interpersonal friction, you are burning thousands of dollars of executive payroll for spectatorship.

The facilitator must intervene the second an exchange becomes a two-way ping-pong match. Watch the room. If the other five leaders are checking their phones, slumping back, or looking out the window, the meeting has left the collective leadership level.

Step in and ask one simple question: Does this issue require the input of the rest of the room to make a decision, or does it just require the two of you to sit down and work it out?

If the decision impacts overall strategy, budget, or cross-functional accountability, keep it on the floor, but force the two leaders to present their distinct points to the whole team so everyone can weigh in.

If the issue is merely technical coordination or an isolated tactical disagreement, kill the discussion immediately. The resolution is not to keep talking; the resolution is a To-Do. Assign a single To-Do to one of the leaders: Meet with Sarah before Thursday to finalize the integration protocol and report back next week.

Push the item off the Issues List, mark it solved for today, and move to the next collective priority.