We have an introverted technical leader who provides great insight in one-on-one conversations but sits completely silent during our 90-minute Level 10 Meeting unless directly called upon. How does our Integrator draw them into IDS without putting them on the defensive?

Question

Tyler Smith · Accepted Answer

Silence in a Level 10 Meeting is often mistaken for agreement or disengagement, but with introverted technical leaders, it is usually a processing delay. Highly analytical leaders do not think out loud. When extroverted peers jump straight into debate, the technical leader steps back to analyze data and risk. If your Integrator does not intentionally pull them into the discussion, you lose their best judgment and end up solving symptoms instead of root causes.

Fixing this requires structural adjustments during the Identify phase of IDS. When an issue involves their domain, the facilitator should explicitly direct the first question to the quiet leader before the floor opens up to general debate. Ask specific, diagnostic questions such as: What is the underlying mechanical failure here, or what blind spot are the rest of us missing?

Another effective tactic is leveraging the Issues List before the meeting starts. If the technical leader owns an issue, require them to state the issue in one clear sentence when it is added to the list. That gives them ownership of the frame before the meeting begins.

During the Solve phase, never close an issue with silent consensus. Before confirming a to-do, the facilitator should run a quick round-robin check and specifically ask the quiet leader: Are you fully bought into this solution, and does your team have the capacity to execute it?

This is not about calling someone out to make them uncomfortable. It is about creating structured airtime so the whole team benefits from the quietest brain in the room.