Join UsCEO MastermindAI Leadership MastermindExecutive AI ProgramFractional AI ExecutiveFractional Advisory1:1 Coaching5-Minute Leader
BooksPower Without PermissionAI Leadership Mastermind
PodcastMeet the Team
ResourcesBlogFree Courses5-Minute Leader AcademyFree AssessmentsResearch and DataTeaching PackagesTestimonialsCEO Coaching ReportGuest Post NetworkJoin UsAdd us on Google

Diffusion of Responsibility at Work: Why "We Will Handle It" Means Nobody Will

Diffusion of responsibility defined in 40 words, the 1968 Darley and Latané study, three workplace examples, and the handover rule that puts one name on it.

By Andreas Pettersson, Founder, Leaders ADAPT

"We will handle it" is the most expensive sentence in a company, because it is true of the group and false of every person in it. Diffusion of responsibility is the name for what happens next: the problem is known to everyone and owned by no one, and it sits.

This page gives the definition, the 1968 study, three versions of it I see in companies every month, and the one rule from the Delegation Protocol that ends it.

I run Leaders ADAPT and wrote the 5-Minute Leader. The rule is short. One A, or none.

Leaders ADAPT on diffusion of responsibility: Diffusion of responsibility is the tendency for each person in a group to feel less obliged to act because the responsibility is shared: the more people who could act, the less likely any one does. Darley and Latané showed it in 1968. At work it is "we will handle it" with no name attached, and the fix is one named owner with an outcome, a level and a date.

Diffusion of responsibility, defined

Diffusion of responsibility is a psychological effect in which a person is less likely to take action when other people are present, because the sense of responsibility is spread across the group rather than resting on any individual. The group knows. Nobody moves.

The original study, in three lines

In 1968 John Darley and Bibb Latané put people in separate booths for a discussion over an intercom, then had one participant, a recording, appear to have a seizure. People who believed they were the only listener went for help almost every time, and quickly. People who believed four others could hear it helped far less often and far more slowly. The study was the first clean demonstration of the bystander effect, and the explanation they gave was diffusion of responsibility.

Nobody in the five person condition decided to let someone suffer. They each assumed someone else had it.

Three ways it shows up at work

Where What it looks like The sentence that caused it
The shared inbox A complaint sits two days while five people watch the folder "The support team handles that inbox"
The known risk Everyone in the leadership meeting knows the contract expires in March, nobody owns renewing it "We need to sort that before March"
The fix that stalls A bug is raised in the channel, three engineers react with an emoji, nobody picks it up "Can someone take a look at this?"

Read the right hand column again. Every sentence assigns the work to a group, a department or a pronoun. Not one has a name in it.

Boomerang check: does your work stay delegated, or does it come back?

Three questions, scored to the protocol that fixes the leak. The 5-Minute Leader is the four protocols, Delegation, 1:1, Accountability and Rhythm, written down so a manager can run them in about five minutes a day, so tasks stop boomeranging back half done.

Get the 5-Minute Leader or see what is inside the 5-Minute Leader.

Why managers keep doing it

Assigning to a group feels fair and feels safe. Nobody is singled out, nobody can say they were overloaded, and the manager has technically delegated. The research says the opposite is true. The group assignment is the one most likely to produce nothing, and when nothing happens the manager cannot even say who to talk to.

There is a second reason, and it is the one I see most in founders. Naming one person means deciding. "You two sort it out" postpones the decision about who is capable, who has capacity and who you trust. The diffusion is the manager's, before it is the team's.

The five minute fix: one A, or none

The Delegation Protocol I teach has a rule for every piece of work that spans people. One accountable owner, or no assignment at all. Responsible people can be many. Accountable is one, and it is a name.

Applied to the three examples:

The inbox gets a named owner per shift, written on the rota. "Sam owns the inbox until 1pm, then Priya." Nothing sits because someone always knows it is theirs.

The contract gets a name and a date in the meeting, before the meeting ends. "Dana owns the renewal. Level two, bring me the two options by February 10." The authority level matters here. Without it Dana will wait to be told how far she can go, and the waiting looks like diffusion again.

The bug gets assigned in the channel by the person who raised it or by the manager, in one line. "Alex, this is yours, level one, tell me when it is closed." The emoji reactions are the bystander effect in miniature, and the name is the cure.

Then the Delegation Board. One line per handover, owner, level, date. On Friday the manager looks at it and sees which items still have a name and which have quietly become "we" again. The how to delegate page has the handover in full, and the responsibility vs accountability page is the longer version of why those are different words.

The difference from social loafing, briefly

Diffusion of responsibility is about not starting. Social loafing is about trying less once you have. They come from the same source, being one of many, and they have the same fix, but they look different in a team. The person who never picks up the bug is diffusing. The person who picks it up with two others and does a third of the work badly is loafing. The social loafing page has that half.

The rule that puts a name on everything

Diffusion of responsibility ends the moment a task has one owner, and the Delegation Protocol in The 5-Minute Leader is how that happens in under three minutes. I wrote it after scaling a company to more than 150 people and finding that the problems everyone knew about were the ones nobody fixed. Four protocols, Delegation, 1:1, Accountability and Rhythm, each about five minutes a day, so the work has a name and the name has a date.

The Delegation Protocol holds the 3-Minute Delegation Conversation with its three authority levels, the 70% Test, the 25% Rule and the Delegation Board. Part 2 holds the One A or None rule and a one page RACI for work that genuinely spans a team.

There is a sentence in it that managers say when they want to be kind, and the protocol marks it as the moment responsibility starts to diffuse.

Get the 5-Minute Leader

Diffusion of responsibility FAQ

What is diffusion of responsibility?

Diffusion of responsibility is the tendency for each person in a group to feel less obliged to act, because the responsibility is shared across everyone present. The more people who could act, the less likely any one of them does. It explains why a problem known to a whole team can sit untouched for a week.

What is an example of diffusion of responsibility at work?

A customer complaint lands in a shared inbox that five people watch. Each sees it, each assumes a colleague will reply, and it sits for two days. Nobody decided to ignore it. The responsibility was spread across five people until it was nobody's. The fix is a named owner for the inbox, by hour or by day.

What is the difference between diffusion of responsibility and the bystander effect?

The bystander effect is the observed outcome: people are less likely to help when others are present. Diffusion of responsibility is one of the main explanations for it, the feeling that someone else is just as responsible, so you need not be. Darley and Latané demonstrated both in 1968 with people hearing a staged seizure.

How do you prevent diffusion of responsibility in a team?

Assign responsibility to one person by name, out loud, with the outcome, the authority level and a date it is checked. Never assign to "the team", "you two" or "whoever is free". For shared surfaces such as inboxes and on call, rotate a single named owner. People act when they know the job is theirs and nobody else's.

Is diffusion of responsibility the same as social loafing?

No, though they often appear together. Social loafing is reduced effort on a shared task you are already doing. Diffusion of responsibility is failing to start at all because you assume someone else will. One is pulling the rope less hard. The other is not picking it up. Both are cured by a visible, single owner.

Why does diffusion of responsibility happen?

Three things combine. Each person's share of the blame for inaction shrinks as the group grows. Each person reads the others' calm as a sign nothing is needed. And nobody wants to be the one who overreacts. Darley and Latané found that people who believed they were the only one to hear the emergency responded almost every time, and fast.

Find the "we" and replace it with a name

Open your last meeting notes and search for "we will", "the team will" and "someone should". Each one is diffusion of responsibility waiting to happen. Put a name, a level and a date on every one of them before the day ends, and watch how many move for the first time.

Which problem does everyone on your team know about that nobody owns?

Get the protocol that ends "we will handle it".

Leadership insights, straight to your inbox

Practical protocols from a former Canon CEO. No fluff, unsubscribe anytime.

Andreas Pettersson

Andreas Pettersson

Former Canon CEO. Founded and exited Arcules, an AI company backed by Canon and Milestone. Today he coaches CEOs and executives through Leaders ADAPT.

More Posts

Free Leadership Profile & Style Assessments