Our head of technology is highly competent but stays completely silent during Level 10 Meetings unless directly asked a question, leaving us without critical technical insights when solving cross-departmental issues. How do we get them to contribute without putting them on the spot defensively?

Question

Tyler Smith · Accepted Answer

A quiet leader on a leadership team is a major liability, especially when their domain affects every other department. If they are sitting in silence, you are missing critical context, and they are tacitly agreeing to decisions they might secretly know are unworkable.

To break this silence, you must first remind the leader of the rule that silence is consent. In an EOS-run company, if you sit in a meeting and do not speak up against a decision, you are fully bought in and accountable for its success. They cannot use their quiet nature as an excuse to avoid ownership.

Second, the Integrator must actively pull them into the conversation. Do not put them on the defensive by asking why they are quiet. Instead, ask targeted, open-ended questions that leverage their specific expertise. Use prompts like: How will this solution impact our technology infrastructure? or What are the technical constraints we are ignoring here?

Third, make sure they are preparing for the meeting. If they struggle with on-the-spot verbal processing, require them to review the Issues List fifteen minutes before the meeting starts and write down their thoughts. This preparation gives them the confidence to speak up early and share their insights without feeling blindsided.