Projects rarely fail because someone refused to do the work. They fail because a task sat untouched for three weeks while two people each assumed the other owned it — and a third person, who needed to approve it, never heard the task existed. The RACI matrix is a deliberately boring tool that makes those gaps visible before they cost you a deadline.
What RACI stands for
RACI is a responsibility assignment chart. You list the deliverables or activities down the left side, the people or roles across the top, and in each cell you write one of four letters:
- R — Responsible. The person who actually does the work. There can be several.
- A — Accountable. The person who owns the outcome and signs off. There must be exactly one.
- C — Consulted. People whose input is needed before the work is finished. Two-way conversation.
- I — Informed. People who need to know the result after the fact. One-way notification.
The distinction people most often blur is R versus A. Responsible is “whose hands are on the keyboard”. Accountable is “whose neck is on the line”. They are frequently the same person on small tasks and almost never the same person on large ones.
A small example
A team is launching a new pricing page. The matrix might look like this:
| Task | Product Manager | Designer | Developer | Legal | Sales Lead |
|---|---|---|---|---|---|
| Define pricing tiers | A | I | I | C | C |
| Design the page | C | R / A | C | I | I |
| Build the page | I | C | R / A | — | — |
| Review legal terms | C | — | — | R / A | I |
| Announce to customers | C | — | — | I | R / A |
Read a row and you know who does the work, who decides, who must be asked, and who gets a heads-up. Read a column and you know exactly what a given person is on the hook for. Both readings are useful, and the column reading is where most problems get discovered.
The four rules that keep it honest
- Exactly one A per row. Two accountable people means no accountable person. Zero means the task is orphaned. This rule alone catches most real issues.
- At least one R per row. A task with an owner but no doer is a wish, not a plan.
- Assign roles, not names, when people rotate. “Duty engineer” survives staff changes; “Marcus” does not.
- One letter per cell. The exception is R/A on the same person, which is fine. Anything beyond that means the task is too coarse and should be split.
Building one in under an hour
- List the work at the right grain. Aim for deliverables and decisions, not individual to-dos. Ten to twenty-five rows is a healthy range; a hundred rows means nobody will ever read it.
- List the people or roles across the top. Keep it to the people who genuinely touch the work.
- Assign the A first, row by row. Doing A before R forces the hard conversation early, while it is still cheap.
- Then assign R, then C, then I.
- Review with the actual people. A matrix written alone in a document is a guess. The value appears when someone says “wait, I thought I was only consulted on that”.
- Scan rows and columns for the red flags below.
What the shape of the matrix tells you
Once filled in, the chart diagnoses the organization almost by itself:
- A column stuffed with letters — that person is a bottleneck and will delay everything.
- A nearly empty column — either that person does not belong in the project, or their contribution has not been made explicit.
- A row full of C’s — too many people must be consulted; this task will crawl. Downgrade some C’s to I’s.
- Everyone Informed on everything — you have invented spam. Being informed has a cost: attention.
- No A anywhere in a phase — that whole phase has no owner, which usually explains why it keeps slipping.
Common mistakes
Building it once and filing it away. A RACI matrix that is not revisited when the team or scope changes becomes a historical artifact. Review it at phase boundaries.
Using it to assign blame. The point is clarity before the work, not a paper trail after a failure. Teams that experience it as a blame tool will quietly stop maintaining it.
Making it too granular. If every sub-step gets a row, the matrix becomes a second task tracker and nobody opens it.
Confusing “Consulted” with “cc’d”. Consulted means their input genuinely shapes the outcome and the work waits for them. If it does not wait, they are Informed.
The variants worth knowing
- RASCI adds Support — people who provide resources or help without owning the deliverable. Useful when shared services are involved.
- RACI-VS adds Verifier and Signatory, splitting the check from the formal approval. Common in regulated industries.
- DACI reframes the chart around a decision: Driver, Approver, Contributors, Informed. Better suited to one-off choices than to ongoing work.
Start with plain RACI. Add letters only when you feel a specific pain that the extra letter solves.
Where it fits alongside agile
RACI has a reputation for being heavyweight, and a self-organizing team working on a single product genuinely may not need it. But the moment work crosses team boundaries — legal, procurement, security, an external vendor — the ambiguity returns, and a one-page matrix for those handoffs pays for itself immediately. Many teams keep it light: a RACI for cross-functional dependencies only, and normal backlog ownership for everything internal.
Conclusion
The RACI matrix does not make work happen faster. It removes a specific, expensive kind of waste: the silence between two people who each believe the other is handling it. Half an hour with a grid and the right people in the room usually surfaces two or three of those gaps — and finding them early is the entire return on investment.
To explore planning, scheduling, stakeholder management and the rest of the toolkit, the free Project Management courses on Cursa are a natural next step.
