When we invite a technical specialist or external vendor into our Level 10 Meeting to help with IDS on a complex problem, they often blow past time limits and derail the agenda. What rules govern guest participants?

Question

Tyler Smith · Accepted Answer

Technical experts and external partners frequently lack exposure to the speed and discipline of EOS®. Left unguided, they will turn a 15-minute problem-solving exercise into an hour-long technical tutorial or product demonstration, wrecking your meeting pulse.

The Integrator must enforce four operational rules whenever a guest enters the Level 10 Meeting™ room:
- Seat them only for IDS®. Never allow guests into the reporting section. The Scorecard, Rock review, Headlines, and To-Do reviews contain confidential leadership data and must move at lightning speed without outside commentary. Have the guest wait outside until the specific issue is up next.
- Frame the problem before they enter. The leadership team must define the issue in two sentences or less before calling the specialist into the room. If the leadership team cannot articulate the core problem, bringing in a specialist will only generate confusion.
- Assign a strict timebox. Inform the guest ahead of time that they have precisely 15 or 20 minutes to answer questions, provide technical context, and help identify potential solutions. When the timer expires, the Integrator dismisses the guest regardless of where the conversation sits.
- Keep the decision inside the leadership team. Guests provide operational intelligence and technical context; they do not vote, decide, or assign To-Dos. Once the specialist leaves the room, the leadership team decides on the final solution, identifies the owner, and assigns a seven-day To-Do.

Protecting the pulse requires strict boundary management. Bring outside experts in for specific insight, keep them contained within the IDS® boundary, and usher them out as soon as the team has the facts required to solve the issue.