One of our co-founders attends our weekly Level 10 Meeting™ and technically participates, but they use passive-aggressive silence or subtle body language to signal disagreement instead of openly raising issues. How do we break this deadlock?

Question

Tyler Smith · Accepted Answer

Passive-aggressive silence is a silent killer of leadership team alignment and business value. When a co-founder or senior leader uses closed body language, sighs, or deliberate silence to signal disagreement instead of speaking up, they are violating the foundational pillar of Trust. In our framework, Trust means open and honest communication where nothing is left unsaid. This behavior can lead to a breakdown in team dynamics, similar to other forms of [leadership team conflict](/qa/leadership-team-trust-healthy-conflict).

To break this deadlock, you must address the behavior directly.

Addressing the Issue Outside the Meeting

The first step is to schedule a private conversation with the co-founder. During this discussion, clarify expectations regarding their participation and communication style.

Key points to cover:

• Remind them of your operational covenant, which requires everyone to speak their minds openly and honestly.
• Explain that staying silent during the Level 10 Meeting™ but expressing disagreement through body language is detrimental to the team's health and productivity.
• Emphasize that this behavior is "toxic" and erodes Trust within the leadership team.

Handling Silence During Level 10 Meetings

During the Level 10 Meeting™ itself, the facilitator plays a crucial role. They must be prepared to call out the silence in real-time.

If you notice the co-founder exhibiting signs of disagreement, such as folding their arms or shaking their head silently:

1. Stop the conversation immediately.
2. Ask them directly what they are thinking. Do not allow the discussion to proceed until they have articulated their position.
3. Ensure their concerns are brought to the table and processed, rather than letting the meeting continue with unaddressed tension. This proactive approach helps prevent [issues from being dropped to IDS](/qa/using-accountability-chart-to-stop-blame-in-ids) later due to unspoken disagreements.

This direct approach ensures issues are surfaced and addressed, preventing them from festering. For more tips on effective meeting facilitation, consider how an [Integrator might facilitate Level 10 Meetings](/qa/should-integrator-facilitate-level-10-meetings).

Long-Term Implications: The GWC™ Filter

If the co-founder consistently refuses to engage or continues with passive resistance, this becomes a deeper GWC™ (Gets it, Wants it, Has the Capacity) issue.

The co-founder must ultimately:

• Get on the same page with the team's vision and operational structure.
• Or, they do not belong in that leadership seat.

A clean exit and scalable operations require a leadership team that operates with complete transparency, especially during weekly IDS® (Identify, Discuss, Solve) sessions. This kind of behavior can impact the team's ability to maintain high [accountability and effectiveness](/qa/how-can-ai-optimize-the-accountability-chart-for-eos-organizations-undergoing-exit-planning).

AI, in this context, never sits in the room. It works before the Level 10 Meeting to prep data and after the meeting to capture and track decisions.

Related questions

• [How do the Visionary and Integrator handle a disagreement when they are completely deadlocked on a major strategic decision?](/qa/visionary-integrator-deadlock-resolution)
• [Our leadership team is starting to form quiet alliances and cliques behind closed doors, especially when we debate resource allocation during our quarterly sessions. It feels like passive-aggressive political maneuvering rather than direct, healthy disagreement. How do we break up these executive factions?](/qa/breaking-up-executive-factions-cliques)
• [Our leadership meetings look fine on paper, but we never have real breakthrough debates. How do I know if my team actually trusts each other, or if they are just playing nice to avoid conflict?](/qa/leadership-team-trust-healthy-conflict)
• [When an issue is dropped to IDS, my leadership team immediately starts pointing fingers at other departments rather than taking ownership. How do we use the Accountability Chart to stop the blame game during meetings?](/qa/using-accountability-chart-to-stop-blame-in-ids)
• [Our Integrator acts as the Level 10 Meeting facilitator but struggles to participate objectively because they are busy managing the timer and the agenda. Should we rotate the facilitator role or hire an outside moderator?](/qa/should-integrator-facilitate-level-10-meetings)