The eight dimensions of a healthy team

Everyone wants a healthy team, and almost no one can say what one is. The phrase gets used the way "good culture" gets used — as a feeling everyone recognises and no one can pin down. It sits in performance reviews and board decks and offsite briefs, doing a lot of work while meaning almost nothing specific. The trouble with a feeling is that you cannot improve it. You cannot aim at it, you cannot design for it, and you certainly cannot tell afterwards whether it moved. You can only improve something you can name. So we name it. We read a team across eight dimensions.

They are not a personality test and not a scorecard for individuals. They are the parts of how a group works together, each of which can be strong or weak on its own, and each of which can be observed, worked on, and read again later. Naming them is not an academic exercise. It is the difference between "the team feels off" and "decision-making has stalled and belonging is thin" — and only the second of those is a problem you can do anything about.

Why a vocabulary is the whole point

Consider what happens without one. A leader senses something is wrong with a team. The symptoms are real — meetings drag, good people are quietly checked out, decisions keep reopening — but with no vocabulary to sort them, they all collapse into one undifferentiated worry: morale. And "morale" has no treatment. It sends you to the catalogue of activities, where you pick something plausible, run it, and hope. Sometimes it helps. Usually it does not, because you never established what specifically was broken, so you had no way to choose the right response or to know afterwards whether you chose well.

A vocabulary changes the physics of the problem. The moment "morale" resolves into eight distinct things, the vague worry becomes a set of specific, answerable questions. Is it that people do not trust each other, or that they trust each other fine but are pointed in different directions? Is the team out of energy, or full of energy and unable to convert it into a decision? Those are different problems with different answers, and treating one as if it were the other is how well-meant interventions land in exactly the wrong place. The eight dimensions are that vocabulary. This whole site — the moments we write about, the roles, the functions, the industries — comes back to them, because they are the ground the rest of it stands on.

The eight

Trust

Whether people believe each other's competence and intent enough to depend on one another without checking. It is the quietest dimension and the one everything else rests on. Trust has two layers that are easy to conflate: believing colleagues are good enough at their jobs to rely on, and feeling safe enough to be exposed in front of them — to admit a mistake, ask for help, or disagree in the open. The second is rarer and decides how a team performs under pressure. We treat it as foundational, and we have written about trust inside a team on its own, because when it moves it moves everything above it.

Communication

Not how much a team talks, but how well the important things travel. A team can be in constant contact and still fail to communicate, because the messages that matter — the hard feedback, the early warning, the quiet disagreement — never actually get said or never actually land. Good communication is measured by whether the difficult thing arrives in time to act on, not by the volume of channels or the frequency of stand-ups.

Alignment

Whether people are actually pointed at the same thing. Teams are very often busy and unaligned at the same time, which feels like progress and is not. Alignment is not agreement on everything; it is a shared, specific understanding of what the team is for right now and what winning looks like. Its absence is expensive precisely because it is invisible: everyone is working hard, so no one suspects the work is pulling in slightly different directions until the results fail to add up.

Collaboration

Whether people build on each other's work or run in parallel lanes that happen to share a building. Two functions can be perfectly cordial and still not collaborate — polite, responsive, and fundamentally separate. Real collaboration shows up as work that could not have been done alone, where one person's contribution visibly changed another's. Its absence shows up as handoffs that are technically complete and practically useless.

Decision-making

Whether the team can decide and stay decided. A team that reopens the same decision a week later is not being thorough; it is stuck, and the churn is a hidden tax on everything else. Healthy decision-making is not about speed for its own sake. It is about the team's ability to commit with enough shared understanding that the decision holds when someone outside the room pushes on it.

Energy

Whether the team has the capacity to engage, or is running on empty. Energy is not enthusiasm and not a mood; it is the fuel the other dimensions burn. A depleted team cannot trust, communicate, or decide well no matter how much it wants to, because those things all cost something a tired team does not have. This is why an intervention that ignores energy — a high-intensity day dropped onto an exhausted team — can leave a team worse, not better. Energy is, in our experience, the dimension most often misdiagnosed: read as low motivation and answered with a rousing event that costs the team the very fuel it was already short of.

Belonging

Whether people feel part of the team or adjacent to it. Belonging is the difference between someone who offers a half-formed idea and someone who stays silent to stay safe. It is not about comfort or sameness; it is about whether a person can bring their actual judgement into the room without first calculating the risk. Thin belonging is quiet by nature — the people who feel adjacent are exactly the people who will not tell you they do — which is why it so often goes unread until someone leaves.

Leadership

Whether the people leading create the conditions the other seven need — safety to speak, clarity of direction, and the example that sets the team's weather. Leadership here is not a personality or a title; it is a set of conditions a leader either establishes or fails to. The leader who goes first — who admits the mistake, names the hard thing, holds the direction steady — makes the other seven dimensions possible. The one who does not caps them, however capable the team. We treat this as its own force, and have written about how the leadership team sets the weather for everyone below it.

The dimensions are a stack, not a list

Presenting them as a list makes them look equal and independent. They are neither. They sit in a rough dependency order, and trust is at the bottom of it. This is not our invention — it echoes Patrick Lencioni's long-standing observation that an absence of trust is the root dysfunction from which the others follow, and Amy Edmondson's research on psychological safety as the precondition for teams that learn. What we have done is turn that insight into a working set a practitioner can read and design against.

The practical consequence of the stack is that the same visible symptom can have very different roots. A team that cannot make decisions might have a decision-making problem — or it might have a trust problem wearing a decision-making costume, because people who do not feel safe will keep reopening decisions rather than commit to something they cannot later be blamed for. Treat the symptom and nothing changes. Read the stack, find the load-bearing dimension underneath, and a single well-aimed intervention can lift several dimensions at once. Fix trust and communication often improves on its own, decisions start to hold, and bad news begins arriving early enough to be useful.

A worked example

Take a real-feeling case. A product team is missing deadlines and the leader assumes the problem is focus, so the plan is a goal-setting offsite. Read across the eight, though, and a different picture appears. Alignment is strong — everyone can state the goal clearly and agrees with it. Energy is fine. Communication is even good. What is thin is decision-making, and underneath it, trust. The team keeps missing deadlines because it cannot commit to a single approach; every decision stays provisional, quietly reopened in side conversations, because no one feels safe enough to be the person who backed the call that failed. A goal-setting offsite would have been a confident answer to a question this team was not asking. They already know the goal. What they cannot do is decide how to reach it and stay decided, and that is a trust problem before it is a decision problem.

The value of the eight is exactly this: they stop a leader from treating the loudest symptom as the disease. The missed deadlines were real, but they were the smoke. The fire was two dimensions down. An experience aimed at the smoke would have produced a pleasant day and the same missed deadline the following month. An experience aimed at the fire — safe, repeated instances of committing together and living with the outcome — has a chance of actually changing the pattern. You cannot make that distinction without a vocabulary that separates the symptom from the source, which is what the dimensions give you.

Why eight, and not one number

The temptation is always to collapse these into a single score, because one number is easy to report and easy to compare across teams and quarters. We resist it, for a reason that matters more than convenience. A team is almost never uniformly healthy or unhealthy. It is strong on several dimensions and quietly hollow on one or two, and the hollow ones are doing most of the damage while the strong ones hide it.

A team can communicate constantly and not trust each other. It can be full of energy and completely unaligned. It can be close and warm and unable to make a decision. Average those into one figure and the specific failure — the thing actually costing the team — vanishes into a middling number that tells you nothing about what to do. A composite score is comfortable and useless in the same motion: it feels like measurement and prevents the one thing measurement is for, which is knowing where to aim. The point of the dimensions is not to grade the team. It is to find the one that is broken.

This is also why we are wary of dashboards that reduce culture to a single trend line. A rising line is reassuring and directs no action. Eight readings that show trust flat, energy falling, and alignment climbing tell a leader exactly what to protect and what to address next. The resolution is the value.

Team level and organisation level

The same eight dimensions work at two scales, and they do not always agree. A single team can be healthy inside itself while the organisation around it is fractured, and a company can look aligned at the top while individual teams quietly are not. Trust within a team is a different thing from trust between teams. Belonging to your immediate group is different from belonging to the company. Alignment inside a squad can be perfect while the squad is aligned to the wrong goal because the organisation above it never made the goal clear.

We read both, because fixing a team and fixing the organisation it sits in are related but separate jobs, and confusing them is how good interventions land in the wrong place. This distinction matters most in large, distributed structures — a global capability centre, for instance, where a team in one country belongs strongly to its floor and weakly to a headquarters it has never visited. We have written about that specific case in GCCs: one company, two continents, because the gap between team-level and organisation-level health is where a lot of distributed companies quietly lose people.

How the dimensions get misread

Because the dimensions overlap in how they show up, each one is regularly mistaken for another, and the mistakes are predictable enough to name. Low trust is read as a communication problem, because the visible symptom is that important things go unsaid — so a team gets communication training when what it needs is the safety to say the hard thing. Thin alignment is read as poor collaboration, because people are not building on each other's work — but they cannot build toward a shared thing they were never pointed at. Low energy is read as low engagement or a motivation problem, and gets answered with a rousing event that costs energy the team did not have to spend. Weak decision-making is read as slowness, and gets a process fix — more meetings, tighter agendas — when the real issue is that people will not commit.

The pattern in all of these is the same: the treatment is aimed at the symptom's costume rather than at the dimension underneath. This is not a failure of care. It is a failure of resolution — trying to fix a specific thing with a general word. Reading across all eight, rather than reacting to the one that is shouting, is what prevents the confident wrong answer. It is slower at the start and far faster over the life of the problem, because it is the difference between one well-aimed intervention and a year of pleasant days that changed nothing.

Reading the dimensions is what makes design possible

Naming the eight does one practical thing above all: it turns "the team feels off" into a specific finding you can design for and measure against. That is the whole use of them. But the naming only pays off if you actually read the team before you act, rather than guessing which dimension is the problem. Reading first is the heart of what we call diagnostic-first design — the discipline of understanding where a team actually sits before choosing what to do, so the experience is aimed at the real gap rather than at whatever was available in a catalogue.

We are deliberately not going to describe here how the reading is taken. The value is in the discipline, not in the mechanics, and the craft belongs in the work. What matters for understanding the dimensions is only this: each of them can be observed, and observed again, which is what makes a team's health a thing you can change on purpose rather than hope about. If you want the fuller picture of how we approach the reading, we have written about how to read a team before you design.

The dimensions over time

A single reading is a snapshot, and a snapshot can mislead. Teams have good weeks and bad weeks, and a reading taken the morning after a launch will not look like one taken mid-quarter. The dimensions earn their value when they are read more than once — before an experience, after it, and again weeks later, once normal work has resumed and the glow has worn off.

That last reading is the one most people skip and the one that matters most. A team can love an afternoon and be exactly as stuck on Monday. A team can have a quieter, more pointed session and be measurably better at disagreeing well a month on. Only reading the dimensions over time can tell those two apart. This is why our follow-up is structured rather than casual, and why we read again at intervals rather than asking once whether people enjoyed the day. We have written about what those later readings reveal in what Day 14, 30 and 60 tell you. The short version: the result of a team experience is not what is true that evening. It is what is still true two months later.

What all eight holding actually looks like

It helps to describe the target, because "healthy" is easier to recognise than to define. When the eight dimensions hold together, a team has a particular texture. Hard things get said early, in the room, to the person who needs to hear them, and the team is better for it rather than bruised. People rely on each other's work without re-checking it, which frees an enormous amount of quiet effort that low-trust teams spend on self-protection. The team can point at what it is for and agree on what winning looks like this quarter, so the daily work compounds instead of scattering. Decisions get made and stay made, which means the team is not paying the churn tax of relitigating last week. And there is enough energy in the system to absorb a setback without the whole thing seizing up.

None of that requires people to be similar, or comfortable, or endlessly positive. Healthy teams disagree hard; the difference is that the disagreement is safe and productive rather than hidden and corrosive. That texture is what we are aiming an experience at, and what we read for afterwards. It is not a mood. It is a set of conditions, and conditions can be built.

What the dimensions are for

It is worth being blunt about what these are and are not. They are not a philosophy of teamwork, and they are not a maturity model to be climbed for its own sake. They are the vocabulary that lets you find what is wrong, aim an experience at it, and check afterwards whether it moved. Naming them makes the problem specific. Reading them makes the design targeted. Reading them again makes the result provable. Those three moves — specific, targeted, provable — are the entire reason we work the way we do, and they are why measurement changes the conversation from "was it fun" to "did it work."

Everything else we write about — the moments, the roles, the functions, the industries, the occasions — comes back to these eight. A sales kickoff, a post-merger integration, an onboarding cohort, a leadership offsite: each is a specific situation, and each resolves into the same question of which dimensions are strong, which are hollow, and which one is doing the damage. Learn to see a team as eight things rather than one, and the whole problem of team health stops being a mood you manage and becomes a set of conditions you can actually improve.