Responsibility Diffusion

Category: Team dynamics When everyone is responsible, no one truly is.

A new starter joins the team on a Monday. The offer was signed weeks ago, the start date confirmed, the welcome email sent. And on the morning they arrive, there is no laptop, no building pass, no desk, and nobody who is quite sure who they report to for the first hour.

Afterwards, when someone asks how this happened to a person whose arrival had been known about for a month, the answer is the same from everyone, which is that they each assumed it was being handled. HR assumed the manager had raised the IT ticket, because the manager knows what software the role needs. The manager assumed HR raised it, because onboarding is an HR process and there is a checklist somewhere with HR’s name on it. IT had no ticket, so as far as IT was concerned there was no new starter at all. Facilities allocate desks when IT tells them to provision one, and IT never told them. Each link in the chain behaved entirely reasonably given what it believed the others were doing.

Nobody decided not to set up the laptop. That is the part that catches people out. There was no moment where a named person looked at the task, weighed it, and let it drop. The task was never anyone’s in particular, so there was no person to drop it. It simply sat in the space between four functions, each of which could see it, none of which owned it, all of which assumed the gravity of the obvious would pull someone else toward it. The work was visible to everyone and assigned to no one, and visible-to-everyone is a far weaker thing than it sounds.

What makes this maddening is how avoidable it looks in hindsight. This was not a hard problem. Ordering a laptop is not a feat of coordination. The difficulty was never the work itself. The difficulty was that responsibility had been spread so thinly across the group that it had stopped being load-bearing anywhere, and the most ordinary task in the world fell straight through the gap that thinness created.

The Principle

Responsibility does not divide cleanly. When a duty is spread across a whole group rather than placed on a named person, it does not become four people each carrying a quarter — it becomes four people each carrying nothing, because each one can see the others and assume the weight is being held over there. A responsibility owned by everyone is, in practice, a responsibility owned by no one.

This is the close cousin of diffusion in oversight — the way a crowd of reviewers each checks less because the others are watching — but it is a distinct and in some ways more dangerous failure, because it is not about scrutiny of work that exists. It is about work that never gets done at all. Nobody misses the error in the report; there is no report, because the person who was meant to write it was a committee, and committees do not write reports. The gap is not in the checking. The gap is in the doing.

The mechanism is simple and almost impossible to switch off. A named owner experiences a task as theirs, with all the discomfort that implies — if it fails, it is unambiguously their failure, and that discomfort is exactly what makes them act. A group member experiences the same task as partly theirs and partly several other people’s, and that fractional ownership comes with a fractional discomfort, and a fractional discomfort is one you can live with. You can tell yourself a completely true story in which someone else had it. Everyone in the group tells themselves the same true story at the same time, and the task quietly starves.

Why It Is Inevitable

Spreading responsibility feels like the safe, generous, modern thing to do. We are suspicious of single points of failure and fond of shared ownership, collective accountability, the team owning the outcome together. It sounds robust. It sounds like nobody is a bottleneck and nobody is left exposed. So we say “the team will handle it,” or “we’re all responsible for quality,” or “this is a shared priority,” and we feel we have made the thing more likely to happen, when we have very often made it less.

It is inevitable for three reasons that compound.

The first is that diffusion is invisible at the moment it occurs. Nobody stands up in the meeting and says, “I am assigning this to no one.” They say, “Great, so we’re all aligned on this,” and everyone nods, and the absence of an owner looks exactly like the presence of a shared one. You cannot see the gap until something falls through it, and by then the falling has already happened.

The second is that the felt stake genuinely falls as the group grows, and it falls for everyone simultaneously. This is not a story about lazy people. The most conscientious person on the team relaxes slightly when they can see five capable colleagues who could equally pick the task up. That relaxation is rational. The problem is that it is universal, so the slack that each person reasonably takes up is slack that nobody else is taking up either.

The third is that ambiguous ownership is socially comfortable and explicit ownership is not. Naming an owner means telling a specific human being that this is on them, which feels like a burden you are placing on a colleague, and like an exposure you are accepting if it is you. “Let’s all own it” spares everyone that conversation. It is the path of least resistance, and it gets chosen for the same reason most comfortable defaults get chosen — because in the room, in the moment, it is the version that nobody pushes back on.

How It Shows Up

• “I thought you were doing that.” “No, I thought you were.”
• Tasks owned by “the team,” a function, or a meeting, rather than by a person with a name.
• Action points in minutes with no owner against them, or with several owners against them, which amounts to the same thing.
• The obvious, un-clever work — the booking, the follow-up email, the ticket, the chasing — being precisely what falls through, while the hard interesting work, which someone wanted to own, gets done.
• Big shared initiatives that are everyone’s priority and therefore advance more slowly than small ones that belong to a single determined person.
• A handoff between two teams where the work lives in the seam and neither side considers the seam theirs.
• After the failure, a genuinely baffled group, each member of which can honestly say they did nothing wrong — and each of whom is right.

Why It Causes Damage

The damage has a particular signature that makes it expensive. The things that fall through diffused responsibility are almost always the obvious things, the tasks so simple that everyone assumes they could not possibly be missed. That assumption is exactly why they are missed, and exactly why the miss does so much damage when it lands. Trust gets built on the floor of “well, the basics will obviously get done,” and it is the basics that diffusion eats first. A clever, difficult deliverable usually has someone who wanted to own it. The unglamorous certainty is what nobody claims.

It also fails silently right up until the deadline. A named owner who is in trouble tends to surface it — they raise their hand, because the problem is visibly theirs and they would rather flag it than wear it. A diffused responsibility has no one whose problem it visibly is, so there is no one positioned to raise the alarm. Everyone assumes progress is happening over where the others are, and the first hard evidence that it was not arrives at the moment the thing was due. Diffusion converts a problem that could have been caught early into one that is only discovered late, which is the most costly possible time to discover it.

And the instinctive fix makes it worse. When something falls through the gap, the natural response is to involve more people next time — more eyes, more sign-off, a wider circle of accountability. But adding people to an unowned task lowers each person’s stake further and widens the gap. The process gets heavier and the basics get less reliable at the same time, and the next failure gets blamed on individual carelessness when the real culprit was a structure that made carelessness the rational, blameless default.

How To Counter It

• For every task that matters, insist on a single named owner. “Who owns this?” must have exactly one answer, and that answer must be a person, never a team, a function, or a meeting. If the honest answer is “all of us,” the honest translation is “none of us.”
• Distinguish owning the outcome from doing the work. Several people can contribute; one person is accountable for it landing. The owner’s job is not to do everything — it is to make sure the thing happens, including by chasing the people who hold the pieces.
• Watch the seams between teams and handoffs especially hard. Work that crosses a boundary needs an owner who owns the crossing, not two sides who each own up to the edge of their own patch.
• Never let an action point exist without a name against it. A task with no owner is not a task; it is a hope. A task with three owners is a task with no owner wearing a disguise.
• Make the assumption explicit. Go round the group and ask each person what they are relying on someone else to do. The gaps surface immediately, because two people will name the same task and neither will think it is theirs.
• Resist the urge to fix a dropped ball by adding people. Far more often the fix is fewer people and clearer ownership, not a wider circle of shared accountability.

What Good Looks Like

Work where every consequential task has one owner who knows it is theirs and cannot quietly assume it away, and where that ownership is spoken out loud so there is no ambiguity to hide in. The owner may delegate, coordinate, and lean on a dozen contributors, but if it fails, everyone — including the owner — knows whose name was on it, and that clarity is not a punishment. It is a kindness, because it is what makes the thing actually get done.

Shared effort is real and valuable; it is shared responsibility that is the trap. The strongest teams pair wide collaboration with narrow ownership: many hands on the work, one name on the outcome. They treat “we’re all responsible for it” not as reassurance but as a warning sign — the precise sound a task makes just before it falls through the floor.

A Reflective Question

Think of something important that is currently “the team’s responsibility.” If it quietly failed to happen, and you gathered everyone afterwards, how many of them could honestly say it was their job to make sure it did — and if the answer is more than one, or fewer than one, what would it take to make the answer exactly one?