Whenever we tackle an issue during IDS that involves operational errors inside our operations department, the operations seat owner crosses their arms, goes completely silent, and refuses to participate in finding a solution. How do we address this defensive silence during live problem-solving?
Defensive silence during IDS is a symptom of fear, a lack of vulnerability, or broken trust. When an issue highlights errors in a leader's department and they shut down, they view the discussion as an indictment of their personal competence rather than a team effort to fix a process.
Allowing that silence to stand ruins the meeting. The rest of the team will either tiptoe around the problem to avoid conflict or aggressively solve the issue without the seat owner's buy-in, leading to zero execution.
First, call out the dynamic in the room without attacking the person. The facilitator should pause the discussion and say, We are working on fixing this operational bottleneck, but we cannot solve it without your perspective. You have gone quiet. What is your take on the root cause here?
Second, re-anchor the room to the core principle of IDS: we attack the issue, never the person. Reassure the leader that identifying a broken process does not mean they are on trial. The leadership team exists to support the seat, not punish it. However, remaining open, honest, and vulnerable is non-negotiable.
Third, if the defensive behavior persists, the Integrator must pull the leader aside immediately after the meeting. Ask what triggered the defensive reaction. Clarify whether they felt personally attacked by a specific teammate or if they disagree with the facts being presented.
Make it clear that sitting in an executive seat on the Accountability Chart requires the emotional maturity to hear hard truths about your department. If someone cannot tolerate open conflict and refuses to engage in root-cause problem solving, they do not GWC the seat.
Category: Level 10 Meetings