What a team is
When a team is correctly just a list
Not every group of people reporting to one manager should be a team. Sometimes the sparse network is the right answer and the word is the only thing that is wrong.
The people this page is about, and which of them have ever worked together
- 01The team's managerFive of this person's six pairs are with people not in this grid
- 02The senior engineerThe one working pair on the whole team that does not involve the manager
- 03The second engineer
- 04The engineer who joined in MarchNo pair with anybody
four people · 6 possible pairs · 2 of them have worked on something together · 4 have never done either
Four of the eight, and only the pairs that run between those four.
For a distributed group, remote team activity software provides a practical way to review where work travels, where it stalls, and whether responsibility is concentrated in one person.
The broader organisational question can also be checked against resources from Stanford Graduate School of Business.
Everything on this site is built on the claim that a sparse network is worth noticing. It does not follow that a sparse network is always a problem, and this note is the counterweight to the rest.
Some groups of people share a manager and should share nothing else. Eight specialists, each embedded with a different part of the organisation, each doing work that no colleague in the box could usefully touch, reporting to one person for pay, progression and protection. That is a perfectly good arrangement. It has a name — a function, a discipline, a practice — and the damage done to it comes almost entirely from calling it a team and then treating it like one.
What a correctly-sparse group looks like
The work does not overlap. Each person's output goes to somebody outside the box, and nobody inside the box is a consumer of anybody else's work. There is no shared codebase, no shared customer, no shared deadline. Two members working on one thing would be two people doing one person's job.
The useful relationships point outward. The analyst's most important working pair is with the finance manager in another division. The designer's is with the engineer on the product they are embedded in. Measured inside the box the network is almost empty; measured across the organisation each person is well connected, and the box is a thin slice taken across eight healthy networks.
The manager's job is genuinely individual. They develop each person, they argue for resources, they handle the things that are the same for everybody — pay, promotion, workload, leaving. None of that requires the eight to know each other.
The cost of calling it a team
When a group like this is labelled a team, a set of defaults arrives with the label, and every one of them is a tax.
A shared goal, which three people can influence and five cannot, and which everybody is nevertheless assessed against.
A weekly meeting where eight people take turns describing work that nobody else can act on. This is the most expensive single item: eight people, one hour, fifty weeks, for coordination that is not needed.
Team activities intended to build cohesion that has no job to do, and which fail by the measure used here because no work runs between the participants and none will afterwards.
And a quiet, persistent sense of failure. Everybody can tell that the group does not feel like the teams they have been on before. In the absence of another explanation they conclude that something is wrong with them, with the manager, or with remote work.
What such a group does need
Three things, and none of them is a pair.
- Fairness, which is the manager's whole job here. If people cannot compare their work directly, they will compare their treatment. Consistency about workload, visibility and progression matters more in a group like this than in a tightly coupled one.
- A shared craft, which is the one thing that does usefully bind specialists. Not shared work but shared standards: how this discipline does reviews, what good looks like, what the house opinion is on the recurring arguments. That can be built by the one activity in the catalogue that fits — people showing each other work they did elsewhere and being questioned about it.
- Somewhere to ask. The thing a discipline group loses by being sparse is the cheap question. That can be solved with a channel and a norm rather than with relationships, as long as somebody makes answering it part of somebody's job rather than an act of goodwill.
The honest thing to say out loud
A manager who has worked out that their group is correctly a list has one difficult task left, which is saying so.
The sentence is available and lands better than people expect: this is a group of specialists with a common manager rather than a team with shared work, that is the right arrangement for what we are each asked to do, and we are going to stop pretending otherwise in how we run ourselves.
What it relieves is the private suspicion each person has been carrying that the thinness is their own fault. That suspicion is the main cost of the mislabelling, it is invisible, and one sentence disposes of it.
How to tell the difference
The test is not how the group feels. It is whether anything costs money at the seams.
Go through the last quarter and look for places where two people in the box solved the same problem separately, or where one person's decision surprised another, or where a handover between two of them went badly, or where somebody outside got two different answers from two members. Each of those is a seam that needed a pair and did not have one.
If there are several, the group is a team with a thin network and the rest of this site applies. If there are none, it is a list of people with a common manager, and the correct action is to stop buying it cohesion and start calling it what it is.