Driving Team Performance from the Inside Out

Team performance rarely stalls because of missing structure. Most excos and their direct leadership teams have done the work. They’ve established clear priorities, defined roles and decision rights, and built disciplined meeting cadences. Their outer operating system is solid. And yet, many still underperform. The reason is almost always the same: deeper team dynamics that have never been addressed. 

When leadership teams struggle, the instinct is to look at the structure. That’s a reasonable place to start, but it only explains so much. What structure rarely captures is the quality of what actually happens between people when they’re in that room together.  

This is because leadership teams operate on two levels at once: 

• The outer operating system of a team is everything visible, such as who owns what and how decisions get made. Leaders invest heavily in it, especially during transitions or moments of difficulty, because it’s tangible and provides a sense of progress. And it matters. Research by McKinsey shows that teams that make fast, high-quality decisions are twice as likely to report superior financial returns, yet only 20% of executives say their organizations excel at decision making. 
• The inner operating system, however, is something harder to see. It’s the collective awareness a team has of itself: how each person shows up, manages tension, and understands what is or isn’t safe to say in a room. It’s what determines how people behave when pressure rises.  

When that inner system is weak, the outer one doesn’t hold. As soon as real tension arises, people start protecting themselves, and decisions stop sticking. This is something we see with our clients and is well documented by researchers. In the book “Noise: A Flaw in Human Judgment,” authors Daniel Kahneman, Cass Sunstein, and Olivier Sibony argue that even experienced executives systematically confuse confidence and consensus, and speed with rigor. In “Immunity to Change,”Robert Kegan and Lisa Lahey help explain why: many leaders lack the developmental capacity to observe both themselves and the team, and act in service of the enterprise rather than personal comfort, reputation, or politics.

When leaders hesitate to speak, quietly agree to decisions to avoid dissent, or stay on the sidelines in debates, it signals a deeper breakdown in the team’s inner operating system. Senior teams can adopt three practices to address these core challenges:

Most teams agree on priorities but almost never name what they will stop doing. Too often, leaders nod and continue protecting their peace. Think of it this way: a team has 100 units of energy and 150 units of work. Something has to go, but that requires someone to say in front of the room: “I hear the decision. I’m frustrated by it. My area will take a hit, and I need you to understand what that means.” That moment of public acknowledgment may feel uncomfortable, yet it is exactly what makes a decision reasonable. Most teams avoid it because it requires trusting the room enough, something that can only be built deliberately through psychological safety.

In meeting rooms, a handful of people typically dominate the conversation and decision-making while others stay silent. This limits collective intelligence and richness of discussion, reducing decision quality and often leading to resistance after the meeting if participants disagree with the direction. Conversely, when every leader is required to state a view before a decision is finalized, teams collect the actual intelligence in the room, surface real objections while there’s still time, and build genuine buy-in. Over time, participation patterns also reveal something useful: who rarely engages and who only speaks when their function is at stake. That’s information worth paying attention to. 

When the CEO runs every meeting, the team organizes itself around that person rather than the work. Rotating facilitation or assigning it to others changes who speaks, who owns outcomes, and often raises the level at which the team operates. It also builds accountability across the group, as more leaders step into shaping how the work gets done. It’s a small shift that signals something larger: this team is capable of leading itself, even when the team leader is not present. 

When assessing your leadership team’s inner operating system, these questions can be helpful: 

“Which decision did we say we made—but didn’t actually hold?” 

• What personal, functional, or political cost made this decision hard to stand behind? 
• Did we reopen it openly or let it unravel quietly? 
• What behavior did the system reward in that moment? 

“Where are we asking process to do the job of courage?” 

• Which forums feel heavy because real disagreement is delayed or avoided? 
• Where do we rely on escalation instead of ownership? 
• If leaders were more explicit about trade offs, what process could we remove tomorrow? 

“In this team, what is currently harder: saying ‘I disagree’ or changing my mind?” 

• Who speaks last, or not at all, when stakes rise? 
• When was the last time someone publicly reversed their view? 
• What would make dissent both safer and more consequential here? 

Helping leaders become more self-aware is now a key way to improve team performance, essential to navigating today’s pressures and growing complexity. It also requires something more fundamental: the ability of the team to be honest with itself, without which no framework can hold.