We have highly skilled technical leaders on our team who GWC their seats perfectly but remain completely silent during the IDS portion of our Level 10 Meeting, especially when we are trying to extract their critical Tribal Knowledge for our exit-readiness documentation. How do we draw out these silent subject-matter experts without making them feel cornered or defensive?

Question

Tyler Smith · Accepted Answer

To extract Tribal Knowledge from quiet technical leaders during the Level 10 Meeting, you must change how you queue up issues. Quiet, analytical minds often do not speak because they are processing information or waiting for a break in the conversation that never comes. Do not put them on the spot by asking what they think in front of everyone. Instead, use a structured approach during the Identify step of IDS.

First, when an issue regarding system documentation or operational bottlenecks is raised, the facilitator should explicitly name the silent leader as the owner of the context. State clearly that the team will need their perspective once the issue is defined. This gives their analytical brain a few minutes to prepare their thoughts while the team defines the actual problem.

Second, implement a silent-writing exercise before opening the floor. Give the entire team two minutes of silence to write down their top three thoughts or solutions on the shared document. This levels the playing field between verbal processors and analytical thinkers. The facilitator then reads the input, allowing the silent leader's written words to drive the discussion.

Third, ensure your Integrator is actively managing the airtime. If dominant voices hijack the meeting, the Integrator must politely pause them and say they want to hear the technical perspective next. This creates a safe runway for quiet leaders to speak. Over time, this predictable cadence builds their confidence and ensures your critical exit-planning data is captured.