dorianbaroni.com

A Different Way of Thinking About Teams

There is no shortage of team effectiveness frameworks. Most of them describe what high-performing teams look like — they map the features, list the behaviours, name the stages. They are useful as diagnostics.

But they can inadvertently suggest that high-trust, high-performance teaming is something you build by adding components — as if assembling the right parts in the right order will produce the result.

In forty years of working with teams across sectors and geographies — from investment banking to global humanitarian operations, from luxury brands to Ivy League institutions — I have come to understand it differently.

Extraordinary teaming is not assembled. It is grown. And like anything that grows, it requires specific conditions — not as nice-to-haves, not as aspirational qualities, but as genuine prerequisites. When those conditions are present, teams consistently surprise themselves with what they can do. When any one of them is absent or severely underdeveloped, performance becomes extractive rather than generative — it costs more than it gives back.

What follows are not elements of a framework. They are seven necessary conditions for extraordinary teaming.

A team leader's primary job is to establish and tend them.

Purpose: The Center of Everything

Before the seven conditions, a word about how they work.

Most team development models start with Purpose — the influence of Simon Sinek is everywhere. State your why, and everything else follows. In my experience, this gets the relationship between purpose and teaming precisely backwards.

Purpose stated before trust is established is just a slogan. A team that has not yet developed the curiosity to question its own assumptions, the listening capacity to hear what is actually happening around it, or the trust to be honest with each other cannot truly own a shared purpose. They can recite it. They cannot live it.

The model I work with places Purpose at the center — present from the very beginning as an orienting question, but understood as both the starting point and the deepest outcome of everything that surrounds it. As a team grows through the six conditions below, it returns to Purpose repeatedly — and each time, the answer is richer, more owned, more real.

This is the difference between a purpose that lives on a slide and a purpose that sustains a team through genuine difficulty.

The Six Necessary Conditions

These conditions are not sequential steps or a checklist to be completed and set aside. They are interdependent — each one strengthens and is strengthened by the others, and all of them continuously deepen the team's relationship with its shared purpose. Think of them less like building blocks and more like the interlocking root systems of a living forest.

They do have a developmental sequence for teams encountering this work for the first time. That sequence is intentional and has been road-tested across many years and many different team contexts. It begins where change always must begin: with the willingness to see differently.

1. Growth Mindset & Curiosity

The entry point

A team cannot grow what it cannot see. And a team cannot see what its members are not willing to look at honestly.

Growth mindset — the belief that intelligence, skill, and understanding can be developed through effort and reflection rather than being fixed quantities — is the foundational prerequisite for everything that follows. Without it, the other conditions cannot take hold. A team whose members are in self-protection mode, whose leader cannot acknowledge uncertainty, or whose culture treats not-knowing as a weakness will be unable to genuinely engage with any of what comes next.

Curiosity is growth mindset in action. It is the specific quality of being genuinely interested in perspectives that differ from your own, in feedback that is uncomfortable, in the question you haven't thought to ask yet. In a team context, cultivated curiosity is what transforms a group of individually capable people into a collective intelligence.

A team leader's work here:  to surface and model growth mindset explicitly; to establish from the outset that not-knowing, questioning, and being changed by new information are valued here — not signs of weakness.

2. Listening Systemically

Hearing what is actually happening

Most teams operate with a very limited range of listening. They hear the content of what is being said. They miss the system in which it is being said.

Listening Systemically is a practiced capacity that operates at three levels simultaneously, each one making the others more visible:

Individual level: Levels of Listening — moving from listening to reply, through listening to understand, to listening to the field: the unspoken dynamics, the emotional undercurrent, the things everyone knows but no one is saying.

Team and organizational level: Iceberg Analysis — learning to see the assumptions, mental models, and structural forces beneath the surface behaviour of a team or organisation. What shows up in a team meeting is rarely the full story. Iceberg work helps a team develop the habit of asking: what is producing this pattern, not just what is the pattern?

Individual and team level: Stakeholder Power Mapping — understanding who holds formal and informal power in the system surrounding the team; whose voices are centred and whose are marginalised; how power dynamics inside and outside the team shape what gets said, what gets heard, and whose ideas travel furthest.

This third element — power mapping — is the one most often omitted from team development conversations. Its absence explains more team dysfunction than almost anything else. Power dynamics do not disappear because they are unacknowledged. They go underground, shaping who speaks, whose ideas are taken seriously, who feels they truly belong, and who quietly disengages. Extraordinary teaming requires that power be made visible enough to be worked with honestly.

A team leader's work here:   to develop the team's collective listening range; to make the practice of Iceberg Analysis a regular team habit; and to develop the self-awareness to see their own positional power and use it in service of the team's collective intelligence rather than as a substitute for it.

3. Team Culture of Trust

The foundation and the outcome

Patrick Lencioni's research is unambiguous: vulnerability-based trust is the foundational condition for high-performing teams — the one that makes all others possible. In its absence, the energy that should go into the work goes instead into self-protection: managing perceptions, avoiding accountability, and playing the political games that hollow out teams from the inside.

Vulnerability-based trust is not politeness or professional cordiality. It is the specific kind of trust in which team members can genuinely say — and mean — I don't know, I was wrong, I need help, I am struggling — without calculating the cost to their standing.

Psychological safety, in Amy Edmondson's definition, is what emerges from that trust at the team level: the shared belief that the team is a safe place to take interpersonal risks — to speak up, to dissent, to raise problems, to offer unconventional ideas — without fear of humiliation or punishment.

It is worth being precise about what psychological safety is not. It is not the absence of high expectations, nor the avoidance of difficult feedback, nor a culture where anything goes. The teams with the highest psychological safety are often the ones with the clearest and most demanding shared standards. Safety and rigour are not opposites. They are, in fact, what each other requires.

A team leader's work here:  to model vulnerability-based trust first and most visibly. Teams take their cues from leaders. When a leader cannot say I don't know or I made a mistake, neither can anyone else — regardless of what the culture deck says.

4. Welcome Divergence

The generative power of difference

Every team contains a diversity of perspectives, experiences, and mental models. That diversity is one of the most valuable assets a team possesses — and one of the most routinely suppressed.

The suppression happens for understandable reasons: disagreement is uncomfortable, conflict feels risky, and harmony feels more efficient in the short run. But teams that cannot engage productively with their differences are teams that have quietly eliminated one of their greatest sources of intelligence and innovation. The smoothest-running team in the room is often the one producing the most conventional thinking.

Welcoming Divergence is not about tolerating conflict for its own sake. It is about developing the specific skills — and the cultural permission — to engage with differences of opinion as a generative act rather than a threatening one. It is the capacity to hold the tension between different views long enough for something genuinely new to emerge, rather than collapsing prematurely to consensus or avoiding the conversation altogether.

A team leader's work here:  to actively invite dissent; to protect the person who raises the uncomfortable question; to distinguish between the productive friction of genuine inquiry and the unproductive friction of ego or positional defensiveness — and to model the difference clearly.

5. Processes for Collective Commitment

Pragmatics as a doorway into something deeper

Ambiguity about how a team makes decisions — who has input, who has authority, what counts as a real commitment versus a polite agreement — is one of the most reliable sources of team dysfunction. It generates confusion, resentment, the particular exhaustion of effort that goes unacknowledged, and the slow erosion of trust that comes from repeated experiences of being consulted but not heard.

Clear, agreed processes for decision-making are the pragmatic entry point into this condition. They matter in themselves. But they are also a doorway into something deeper: the ethos of genuine collective commitment, in which team members feel genuinely co-responsible for the decisions they make together — not just compliant with decisions made above them.

The difference between a team that is collectively committed and a team that is merely compliant shows up most clearly under pressure. Compliant teams execute when supervised. Collectively committed teams find the solution when no one is watching.

A team leader's work here:  to create clarity about how decisions are actually made in this team — and to be honest about the gap between the espoused process and the lived reality. That gap, once named, is often where the most important team development work begins.

6. Right Structures for Mutual Accountability

From structure into culture

Just as clear decision-making processes provide the pragmatic entry point into collective commitment, clear structures for delegation and accountability provide the pragmatic entry point into the culture and behaviours of mutual accountability.

Ambiguity about who is responsible for what — and about how individual contributions connect to the whole — generates duplication, gaps, resentment, and the particular exhaustion of effort that disappears without acknowledgment. The right structures eliminate that ambiguity without imposing rigidity. They define roles and interdependencies clearly enough to eliminate confusion, while leaving the flexibility for the team to adapt as circumstances change.

But structures alone are not the destination. The destination is a team in which accountability is genuinely mutual — not top-down compliance with authority, but the shared ownership that comes from people who are truly committed to each other's success as well as their own.

A team that has moved through the five preceding conditions — that is curious, listening deeply, trusting each other, welcoming divergence, and collectively committed — will experience accountability very differently from a team that has not. The structures become the scaffolding for something that the team actually wants to sustain, rather than a mechanism of control imposed from above.

A team leader's work here:  to design structures that are clear enough to eliminate confusion and flexible enough to serve the work — and to distinguish between accountability as compliance and accountability as mutual ownership. The latter is the goal.

And So, Back to Purpose

A team that has genuinely worked through these six conditions — that has grown its curiosity, deepened its listening, built real trust, learned to welcome divergence, and developed the processes and structures that allow collective commitment and mutual accountability to flourish — will return to its shared purpose and find it transformed.

It will be clearer. More owned. More honest about what the team is actually for, as distinct from what it has been told to say it is for. And it will be more resilient — capable of sustaining itself through the difficulty and disruption that any meaningful work inevitably encounters.

This is the arc of the model. Purpose at the center — orienting the work from the start, and being continuously deepened and made real as the team grows.

A team that has genuinely arrived at its shared purpose through the conditions — rather than been handed it at the beginning — will hold it differently.

That purpose becomes the thing the team protects, not the thing the organization displays.

How I Work With Teams

I work with team leaders and their teams to assess which of the seven conditions are strong, which are underdeveloped, and what specific interventions will build them most effectively in their particular context.

This is not a generic team-building program. It is a tailored, iterative process — grounded in your team's actual dynamics, your organizational culture, and the specific challenges you are navigating. It draws on the research of Amy Edmondson, Patrick Lencioni, and Otto Scharmer, road-tested across forty years and dozens of organisations in multiple sectors and geographies.

The work takes different forms depending on what a team needs:

•         A diagnostic assessment of where the team currently is across all seven conditions

•         A facilitated team offsite designed around the conditions most in need of development

•         An ongoing consulting relationship that supports the team through a sustained period of growth or change

•         Executive coaching for the team leader, linked directly to the team's development process

What it always begins with is a genuine conversation about where this team actually is — not where it would like to be perceived to be. That honesty, at the start, is itself the first practice of the work.

Schedule a confidential discovery conversation

We begin with an honest conversation about where your team actually is.

email me at dorian@dorianbaroni.com