Diffusion of Responsibility
Diffusion of responsibility occurs when individuals in a group assume that others are responsible for taking action, leading to inaction or lack of accountability. This bias is common in organizational settings with unclear roles and responsibilities.
THE IDEA
The Role of Policy Owners and Accountabilities for Third‐Party Interactions
Paradoxically, even when some roles have a formal legal or regulatory responsibility, such as a head of health and safety, head of data privacy, head of compliance, etc., you can find unclear R2A2s: arrangements for who does what and with what authority. Here is what I have heard from policy owners on a number of occasions, ‘I am accountable for the policy development and communication, for delivering training, offering advice and reporting to the regulator. But that does not mean I can make sure the whole organisation is compliant with the policy. I rely on others to do what is needed and ask me for advice if they are unsure. In practice, I have no direct authority to instruct them what to do or to allocate resources in their direction; that is the job of operational management’.
Alongside this, I have also heard line managers say, ‘Everyone is accountable for compliance’, which may be true in broad terms, but can lead to a diffusion of responsibility, where managers and staff say, ‘It's surely [someone else's] job to do something! Why would it be down to me to act when others have equally been involved, and nothing terrible has happened?!’15
Other areas where R2A2 can be challenging include the following:
- When a steering group or committee is involved (After all, if a committee decides something, which individuals are accountable and responsible?).
- When a third‐party contractor or agent is involved.
- When – more broadly – different organisations need to work together on specific issues (e.g. border control, fire, police, ambulance, local government, intelligence services, etc.).
When roles and responsibilities are unclear in a critical area, ask who has the duty, authority, and resources to act.16 A general statement that everyone is responsible can leave the specific work unassigned.
When to use it
Project management: When multiple teams are involved, unclear ownership can lead to missed deadlines and tasks falling through the cracks.
Emergency response: In large-scale incidents, multiple agencies may assume others are taking action, causing delays in critical responses.
Corporate compliance: Employees may not follow policies because they believe the compliance department is solely responsible for enforcement.
Group decisions: In meetings, committee members may not speak up or take initiative because they assume others will handle controversial issues.
FROM THEORY TO EVERYDAY LIFE
In practice
Policy Owner's Dilemma
A policy owner develops guidance and training but cannot allocate operational resources. A gap arises if operational managers assume that the policy owner also carries out the work. Clarifying those separate responsibilities matters more than simply declaring that everyone is accountable.
Manager's Assumption
Line managers may say 'Everyone is accountable for compliance,' but this leads to staff thinking, 'It's surely someone else's job to do something,' resulting in diffusion of responsibility. Without clear individual accountability, no one takes action.
A MOMENT TO REFLECT
Put it to work.
In your organization, are roles and responsibilities clearly defined? Where might diffusion of responsibility occur?
Think of a recent situation where a task was left unfinished because everyone assumed someone else would do it. What could have been done differently?
How can you ensure that accountability is clearly assigned in group projects or cross-functional teams?
CONTINUE THE CONVERSATION
Source texts
- Beyond the Five Whys Root Cause Analysis and Systems Thinking (James C. Paterson)