When our leadership team tackles a complex technical or legal issue during IDS, we often lack ground-level details, but having outside experts or junior managers sit through our entire 90-minute Level 10 Meeting wastes their time. How do you bring non-members into IDS cleanly?

Question

Tyler Smith · Accepted Answer

Inviting junior managers, engineers, or external advisors to sit through an entire 90-minute Level 10 Meeting is a massive operational drain. It forces non-members to listen to irrelevant executive discussions, invites conversational bloat, and compromises leadership team confidentiality.

Yet guessing at technical facts or legal nuances during IDS is equally dangerous. It leads to shallow, speculative debates that produce flawed decisions.

To solve this, use the guest injection protocol. Handle the issue using this four-step sequence:
- Triage before inviting: Keep the technical issue on the Issues List until it naturally reaches the top three priorities for that week. Never disrupt the meeting rhythm just because an external expert is waiting.
- The ten-minute facts window: When the issue is selected, text the subject-matter expert to join the room or video call for exactly ten minutes. The Integrator opens the discussion by stating the exact problem and asking the expert to clarify the specific technical or legal facts.
- Zero guest problem-solving: The guest is there solely to supply facts, not to participate in executive decision-making. Prevent the guest from offering operational opinions on company strategy.
- Immediate dismissal: As soon as the leadership team has the required data, the Integrator thanks the guest and dismisses them immediately.

Once the non-member leaves the room, the leadership team conducts the actual discussion and solves the issue cleanly. This protects executive time, preserves room confidentiality, and prevents decision paralysis without dragging extra people into your weekly pulse.