tyler-smith.com · Questions & Answers

During our weekly IDS sessions, two department heads frequently hijack the conversation with deep technical debates that only apply to their specific departments, leaving the rest of the room disengaged. How does the facilitator shut down these two-person rabbit holes?

When two leaders turn IDS® into a private technical consulting session, the rest of the leadership team shuts down. They open their phones, review emails, and stop paying attention. That is how sixty minutes of collaborative problem-solving gets reduced to two people arguing over implementation minutiae while four high-priced executives sit idle.

The facilitator must intervene the second an issue shifts from strategic direction to departmental mechanics.

Use this three-step protocol:

- Identify the boundary of the room. The leadership team exists to define the what and the who, not work through line-by-line technical execution. If the root cause is clear and the remaining debate is merely how the two departments will configure the workflow, the issue is effectively solved for the leadership room.
- Force an offline to-do. Cut off the debate and say, the direction is clear, but the technical execution belongs between the two of you outside this room. Assign a single, accountable To-Do to one of them with a seven-day deadline. For example, have the operations leader meet with the sales leader by Thursday to finalize the intake form.
- Demand a headline next week. Tell both leaders to report the agreed workflow as an operational headline in next week's meeting. If they cannot resolve it between themselves, they must bring the specific impasse back to the Issues List as a fresh topic.

Protecting the team from two-person sidebars is what keeps your Level 10 Meeting™ focused on high-leverage issues that require the collective brainpower of the entire room.

Category: Level 10 Meetings

← All questions