I’ve spent a percentage of my career in Agile coaching, where one idea gets repeated often enough that it almost becomes doctrine:

The primary unit of performance is the team.

And in many ways, that holds. Outcomes are rarely delivered by individuals working in isolation. They emerge from how people collaborate, align, challenge each other, and ultimately execute together.

So over time, the focus shifts.
From individuals → to teams
From output → to outcomes
From activity → to interaction

That shift makes sense when we’re talking about performance.

But recently, working more in the space of wellbeing at work, I’ve found myself questioning whether the same logic fully applies.

Where wellbeing sits differently

Wellbeing doesn’t behave like performance.

You can have:

• A high-performing team with individuals quietly struggling
• A well-designed system where people still experience work very differently
• The same environment, producing completely different lived experiences

So while performance aggregates at the team level…
Wellbeing doesn’t quite work that way.

It remains deeply individual — shaped by meaning, values, motivation, and personal context.

But here’s the part that’s become clearer:

At work, wellbeing is experienced individually… but shaped collectively.

And that’s where the team comes in.

The team as a wellbeing amplifier (or drain)

The team doesn’t own wellbeing — but it has an outsized influence on it.

Day-to-day experience of work is not driven by policies or strategy decks.
It’s shaped in conversations, behaviours, and interactions.

In other words:

• Not the organisation chart
• Not the HR programme
• But what happens between people

So rather than saying “the team is the unit of wellbeing”…
It’s more useful to think of the team as:

The environment where wellbeing shows up — or breaks down.

Five practical areas of team wellbeing

If you were to make this real with a team, these are five areas worth focusing on:

1. Fairness (Perceived, not declared)
Not just whether things are fair — but whether they feel fair.
Workload, recognition, airtime, opportunities.
Small imbalances compound quickly if left unspoken.

2. Psychological Safety (Can I speak here?)
Can people challenge, admit mistakes, or ask for help without consequences?
This is often the difference between surface-level collaboration and real teamwork.

3. Clarity & Shared Understanding
Confusion creates friction.
When priorities, roles, or expectations are unclear, it shows up as stress — not just inefficiency.

4. Relational Quality (How we treat each other)
Tone, respect, listening, patience.
The basics sound simple, but this is where most teams quietly succeed or fail.

5. Load & Support Balance
Pressure is not the problem.
Unmanaged pressure is.
Teams that openly balance workload and support each other handle stress far better.

Bringing the two worlds together

Agile got one thing absolutely right:

If you want better outcomes, you have to look at the team.

Wellbeing brings a useful counterbalance:

If you want better experiences, you have to look at the individual.

The interesting space sits in the overlap.

Because in reality:

• The system shapes the conditions
• The team shapes the day-to-day experience
• The individual determines how it’s ultimately felt

Most organisations focus on the system.
Most wellbeing approaches focus on the individual.

Very few spend time in the middle.

Final thought

If the primary unit of performance is the team,
then the primary environment of wellbeing at work is also the team.

Not as the owner of wellbeing —
but as the place where it becomes real.

And if you ignore that layer,
you end up trying to fix people… or fix the system…
while missing the thing that sits in between.