Ben Webb on Project Accountability: The One Word Missing From Most Project Plans
I’ve seen beautifully documented projects collapse in slow motion, not because the strategy was flawed, the budget unrealistic, or the schedule aggressive — but because accountability was diluted to the point where it effectively disappeared. Everyone was “involved”. Everyone was “consulted”. Everyone was “across it”. No one was accountable.
And when things went wrong — as they always do — the project had nowhere to go.
Responsibility is comfortable. Accountability is not.
Most project environments are very good at assigning responsibility. Roles are defined. Org charts are polished. Position descriptions are clear. On paper, it all looks robust.
Accountability is different.
Responsibility says this is part of your job.
Accountability says this outcome is on you.
Responsibility is safe. Accountability is exposed.
In complex projects, responsibility is often spread deliberately. Tasks are distributed, inputs are shared, and collaboration is encouraged. None of that is wrong. The problem arises when accountability is treated the same way — as something that can be shared, rotated, or parked with a group.
It can’t.
The moment accountability is assigned to “the team”, “the committee”, or “the process”, it stops existing in any meaningful way. Decisions slow down. Risks linger unresolved. Issues drift from meeting to meeting, collecting commentary but never resolution.
Everyone remains busy. Nothing actually moves.
Why RACI doesn’t fix weak leadership
When projects start to wobble, the instinctive response is often to reach for structure. More governance. Clearer RACI matrices. Additional reporting layers. Another steering group.
RACI has its place. Used well, it can clarify who does what. Used poorly — which is most of the time — it becomes a shield.
I’ve reviewed more RACI matrices than I care to remember, and a pattern shows up consistently:
-
Lots of “R”
-
Plenty of “C”
-
The occasional “I”
-
And an “A” that sits with a role title rather than a person
That’s not accountability. That’s administrative comfort.
RACI does not create leadership. It documents intent. If the person marked as “Accountable” does not feel genuine ownership of the outcome — including the consequences of failure — the matrix is meaningless.
Weak leadership hides behind process. Strong leadership uses process as a support, not a substitute.
Ambiguity is not accidental — it’s often protective
One of the uncomfortable truths about project environments is that ambiguity is sometimes maintained deliberately. When accountability is unclear, underperformance becomes harder to isolate. Decisions can be deferred. Failures can be reframed as collective issues rather than individual ones.
I’ve seen this play out repeatedly in large programs, particularly where politics, reputation, or public scrutiny are involved. Ambiguity becomes a form of insurance. If no one is clearly accountable, no one can be clearly blamed.
The cost of this protection is paid by the project.
Ambiguity slows decisions. It weakens risk management. It encourages escalation instead of ownership. Over time, it erodes trust — not just within the project team, but between delivery teams and executives, clients, and stakeholders.
Projects don’t need more protection from accountability. They need more courage around it.
Accountability shows up when things go wrong — not when they’re easy
Every project looks accountable when things are going well. Milestones are met. Reports are positive. Meetings are upbeat. Ownership appears clear because nothing is being tested.
Accountability is revealed under pressure.
When a contractor fails.
When a budget assumption collapses.
When a political decision changes the rules mid-stream.
When the schedule no longer makes sense but no one wants to say it out loud.
In those moments, the difference between responsibility and accountability becomes stark. Responsible teams ask what should we do? Accountable leaders say this is what we’re doing — and here’s why.
Real accountability shortens decision cycles. It accepts imperfection. It trades false consensus for clarity. And it always involves someone being willing to put their name against an outcome.
What real accountability looks like on complex projects
On the projects that succeed — especially the hard ones — accountability is visible and unambiguous.
You can hear it in meetings.
You can see it in decision logs.
You can feel it in how risks are managed.
Real accountability looks like:
-
Decisions being made even when information is incomplete
-
Clear ownership of risks, not just registers full of them
-
Leaders stepping forward when outcomes aren’t achieved, not stepping sideways
-
Escalation being used sparingly, not as a default
-
Teams knowing exactly who has the final call — and respecting it
Importantly, accountability does not mean authoritarianism. It doesn’t mean shutting down input or ignoring expertise. It means someone synthesises that input and then owns the outcome.
That distinction matters.
The uncomfortable trade-off: accountability reduces comfort but increases delivery
Many organisations say they want accountability. Fewer actually design for it.
True accountability makes environments less comfortable in the short term. It exposes gaps. It creates moments of tension. It forces decisions that some stakeholders would prefer to avoid.
But it dramatically improves delivery.
Projects with real accountability move faster. They resolve issues earlier. They are more resilient when conditions change. And they build trust — because people know where ownership sits.
In my experience, the most effective project leaders don’t talk about accountability much. They demonstrate it. Repeatedly. Quietly. Publicly when necessary.
Why this matters more now than ever
Modern projects are more complex, more visible, and more interdependent than ever before. They operate across blurred organisational boundaries, political cycles, and constant scrutiny.
In that environment, accountability is not optional. It is the stabilising force.
Without it, frameworks become theatre, governance becomes noise, and progress becomes an illusion.
With it, even imperfect plans can succeed.
Comments