Why Your RACI Matrix Isn’t Working

If you've ever sat in a project kick-off and watched someone wheel out a RACI matrix, you'll know what usually happens next. An hour is spent debating whether the Finance Director is Responsible or Accountable. Someone insists the board should be Consulted on everything. By the time the meeting ends, the grid has thirty names in it, half the boxes are unclear, and no one feels any clearer about who actually makes decisions.

RACI matrices are everywhere. They're also, in many organisations, almost entirely useless.

That's not because the underlying idea is wrong. It's because most teams implement them badly, and then wonder why accountability doesn't improve.

 

What RACI is actually for

RACI stands for Responsible, Accountable, Consulted and Informed. The original intent is simple and sound: for any given task or decision, you should know who does the work, who owns the outcome, who needs input before a decision is made, and who needs to be told once it's done.

Done well, a RACI model removes ambiguity. It stops decisions getting made by whoever shouts loudest. It prevents the same person being dragged into every meeting because nobody has been clear about who actually needs to be there. In complex organisations - especially charities with multiple reporting lines, or SMEs that are growing faster than their processes - that kind of clarity is genuinely valuable.

The problem isn't the framework. The problem is how it tends to be used in practice.

 

Where it goes wrong

Too many people marked Accountable

Accountability is singular by design. There should be exactly one person accountable for any given task or decision;  the person who, if it goes wrong, is the one who has to answer for it. The moment you put two names in the Accountable column, you have shared accountability, which is functionally the same as no accountability at all.

We see this constantly in charity digital projects. Two trustees, a CEO and a Head of Communications are all marked as Accountable for the new website. When decisions need to be made, everyone defers to everyone else. When something goes wrong, no one owns it.

Consulted as a dumping ground

In organisations where people feel excluded from decisions or where leaders are nervous about being seen to exclude anyone, the Consulted column becomes a way of managing politics rather than managing a project. If fifteen people are consulted on every decision, you don't have a RACI matrix; you have a very slow committee.

Genuine consultation means: this person's input will materially affect the outcome. If their view won't change anything, they shouldn't be in the Consulted column.

Created once, never used again

A RACI that lives in a slide deck from the project kick-off meeting is not a working tool. It's a historical document. If your team isn't referring to it when disputes arise - if it's not the thing you open when someone asks "hang on, who decides this?" - then it's decorative, not functional.

Confused with a skills matrix or an org chart

A RACI matrix is about decision-making and accountability, not about who has which skills or who reports to whom. We've seen organisations try to use RACI matrices to document capabilities, workload distribution and team structure simultaneously. The result is a document that tries to do too much and ends up doing none of it well.

 

The questions to ask before you build one

Before you create a RACI matrix for your next project or workstream, it's worth asking a few things honestly.

Do we actually have a decision-making problem?

If your team already knows who decides what, and decisions get made at the right level, a RACI matrix may add process overhead without adding value. Use it where there's genuine ambiguity like new projects, new teams, new governance structures.

Are we willing to enforce it?

A RACI only works if people actually defer to it. That means the person marked Accountable genuinely has the authority to make the call and isn't going to be overruled every time the situation gets difficult. If your organisational culture means decisions always drift upward regardless, sorting out that culture is a prerequisite, not something the RACI will fix.

Is the scope narrow enough?

The more useful a RACI tends to be, the more specific the scope. A RACI for "website content" is probably too broad. A RACI for "who approves new page additions, who writes copy, who signs off before publishing, and who gets told when something goes live" is specific enough to be actionable.

 

What good looks like

A genuinely useful RACI matrix is short, specific and alive. Short means it covers a bounded set of tasks and decisions, not an entire organisation's operations. Specific means the entries are precise enough that someone could pick it up cold and know exactly what to do. Alive means someone is responsible for keeping it updated, and it's the thing the team actually uses when questions arise.

In digital projects particularly, we'd suggest three practical rules:

One Accountable per row, always.
If you're tempted to put two people, that's a signal you have a governance gap that needs addressing, not a reason to double up in the matrix.

Limit Consulted to people whose input genuinely changes the output.
If removing them from that column wouldn't affect the quality of the decision, remove them.

Review it at each project milestone.
Accountability should shift as a project moves through phases. Who owns the decision to build isn't necessarily the same person who owns the decision to launch, or the decision to change something after it's live.

 

The bigger point

RACI matrices are a tool for clarity. They work when clarity is the goal. They fail when they're used as a proxy for good governance, when they're created to be seen to have a process rather than to actually support one, or when they're completed in a meeting and never opened again.

If your team is avoiding difficult conversations about who's really in charge of what, a RACI won't solve that. It might make it look solved, briefly. But the conversations will keep surfacing.

The organisations we work with that handle digital projects well aren't the ones with the most sophisticated frameworks. They're the ones where accountability is real, decisions get made at the right level, and people feel genuinely empowered to own their part of the work.

A RACI matrix, done well, can help create that environment. That's the point of it. Don't let it become the opposite.

---

Tim Cawood is the founder of Cawood.io. He has led digital governance and transformation projects across charities, professional membership bodies and commercial organisations. If you're navigating a complex digital project and want to think through your governance model, get in touch.