tyler-smith.com · Questions & Answers

During the IDS portion of our Level 10 Meeting, two leaders frequently dive into granular technical weeds that alienate the rest of the room. How should the facilitator intervene and pull them out of the weeds?

It is common for an issue to involve deep functional technicalities, such as software architecture, complex legal wording, or specific accounting mechanics. When two leaders debate these granular mechanics for twenty minutes, the rest of the leadership team checks out and your meeting velocity dies.

The facilitator must step in using the core discipline of IDS: Identify, Discuss, Solve.

- Identify whether this is an executive issue or a functional execution issue. Does the leadership team need to decide the policy, budget, or strategy, or are two leaders trying to engineer the solution live in the room?
- If the issue requires detailed technical work, the solve is not the technical blueprint. The solve is assigning a single owner a To-Do to build the solution offline with their team and report back.
- Keep debate focused on business impact. Ask the arguing leaders: What decision does this team need to make today to clear your path?

If no company-wide decision is needed, the facilitator immediately cuts the discussion: You two have the expertise to solve this. Owner X, will you take the To-Do to finalize the architecture by next Tuesday? Once captured, move directly to the next issue. Never let technical rabbit holes consume your precious meeting pulse.

Category: Level 10 Meetings

← All questions