You can feel it in the all-hands. The VP of Engineering and the VP of Product answer the same question differently. The Director of Infrastructure and the Director of Platform describe the roadmap as if they are building two different companies. The CEO says "we are aligned" with the confidence of someone who has not attended their own staff meeting recently.
Everybody below the leadership team can see it. Nobody below the leadership team can say it. And so the dysfunction cascades.
The Cascade Nobody Talks About
Almost all team dynamics content focuses on IC teams. The assumption is that team dysfunction is a front-line problem: engineers who will not pair, designers who hoard context, product managers who overcommunicate.
Leadership team dysfunction is qualitatively different because it is multiplicative. When two ICs do not collaborate, one project suffers. When two VPs do not collaborate, every project that crosses their domains suffers. When the leadership team is misaligned on priorities, the entire organization operates with contradictory mandates.
Research on behavioral contagion in organizations found that employees "systematically mirror negative behaviors modeled by organizational leaders through psychological processes such as behavioral contagion, moral disengagement, and displaced aggression" (Journal of Business Ethics, 2023). The trickle-down effect is not metaphorical. It is a documented psychological pattern.
The numbers are stark. Trust in immediate managers dropped from 46% in 2022 to 29% in 2024 (Gallup / Inclusion Geeks, 2025). That erosion starts at the top. When leadership teams model dysfunction, it poisons the well for every layer below them.
What Leadership Dysfunction Looks Like From Below
If you are an engineer, product manager, or mid-level manager, you recognize these patterns:
Conflicting priorities: Your VP says Q2 is about platform stability. The VP of Product says Q2 is about feature velocity. You are on a team that reports to both. Your sprint planning meeting is a diplomatic exercise in appearing to satisfy contradictory mandates.
Decision reversals: Your team makes a decision, ships it, and then a leader from another org reverses it because they were not consulted. MIT Sloan research found that only 28% of executives and middle managers could list three of their company's strategic priorities (MIT Sloan). If the leaders cannot articulate shared priorities, the people executing those priorities have no chance.
Turf wars in resource allocation: Headcount requests become political negotiations. Projects get funded based on which leader has more organizational capital, not which projects serve the strategy. Engineers get pulled between competing initiatives without anyone acknowledging the conflict.
Mixed signals on culture: One leader champions psychological safety. Another runs meetings through intimidation. The team learns that "company values" depend on which leader is in the room.
The Three Patterns of Executive Dysfunction
Research based on interviews with over 100 CEOs and senior executives identifies three distinct patterns of failing leadership teams (HBR, 2025):
Shark tanks: Hyper-competitive teams where leaders see each other as rivals. They compete for the CEO's attention, hoard information, and subtly undermine peers. The organization below them mirrors this with inter-team rivalry and knowledge hoarding.
Petting zoos: Overly polite teams that avoid conflict at all costs. Meetings are cordial and unproductive. Hard decisions get deferred. Strategic disagreements get papered over with consensus language that masks genuine misalignment. The organization below them learns that raising concerns is futile.
Mediocracies: Teams that have settled into comfortable underperformance. They hit their metrics, attend their meetings, and produce their slide decks, but they have stopped challenging each other or pushing for better outcomes. The organization below them optimizes for appearing busy rather than creating value.
Each pattern produces a different downstream effect, and each requires a different intervention. Shark tanks need trust-building. Petting zoos need structured conflict. Mediocracies need external disruption.
Why Leadership Teams Are the Last to Admit It
Three structural barriers prevent leadership teams from addressing their own dysfunction:
Seniority bias: There is an implicit assumption that leadership experience equals teamwork skill. People who have been leaders for 20 years believe they know how to work on a team. They may be excellent individual leaders while being terrible teammates at the executive level. The skills are different.
Status protection: Admitting that the leadership team is dysfunctional feels like admitting personal failure. About 4 in 10 stressed-out leaders have considered leaving their leadership roles (HR Dive, 2025), but few discuss it openly because vulnerability at the top feels career-threatening.
No available solutions: Most team-building interventions are designed for IC teams. The idea of a VP of Engineering doing a team-building exercise feels absurd, because the available exercises are absurd for that level. Escape rooms, trust falls, and icebreakers were not built for executive teams.
The Cost of Doing Nothing
Organizations with highly engaged leadership teams see 23% higher profitability and 51% lower executive turnover (Gallup, 2025). The inverse is equally true: leadership misalignment is one of the most expensive problems in an organization because it compounds through every decision, every meeting, and every priority conflict.
The $359 billion annual cost of team dysfunction is not just an IC problem. It starts at the top and flows down. When leadership teams do not practice working together, they produce the same outcome as any other team that does not practice: poor coordination, communication gaps, and trust erosion.
Leadership Teams Need Practice Too
The same principle that applies to IC teams applies to leadership teams: teamwork is a skill that requires deliberate, repeated practice. No coach looks at a struggling basketball team and says "these are experienced players, they should not need practice." The experience is why the practice matters more, not less.
QuestWorks, the flight simulator for team dynamics, works for teams at every level. It runs on its own cinematic, voice-controlled platform. The scenarios create collaboration in a context that is stripped of the political dynamics that make real executive meetings unproductive. Nobody is fighting for budget. Nobody is protecting turf. The team is just solving a problem together, and the behavioral data from QuestDash shows how they actually work together when the stakes are reset.
For leadership teams specifically, this data is invaluable. It reveals patterns that are invisible in the boardroom: who defers to whom, where communication thins under pressure, and which collaboration patterns transfer from the simulation to actual strategic work.
HeroGPT provides private AI coaching that never shares upstream. HeroTypes give the leadership team a shared language for their working styles. Participation is voluntary. Nothing is tied to performance reviews.
The hardest part is not the intervention. The hardest part is the admission that even leadership teams need to practice. The ones that make that admission are the ones that build organizations where trust flows down instead of dysfunction.
Try it free
