RACI Matrix: How to Build One That People Actually Use
A step-by-step approach to responsibility assignment, the four mistakes that make matrices decorative, and how to keep yours current after week one.
What the four letters mean
Responsible is the person or people who do the work. Accountable owns the outcome and holds final approval. Consulted provides input before the decision is made. Informed hears the result afterwards and needs no say in it.
The rule that carries most of the value: exactly one Accountable per activity. If two names sit in that column, in practice nobody owns it, and the activity will stall the first time the two disagree.
Responsible can be shared across several people. Accountable cannot. Keeping that distinction crisp is most of what separates a working matrix from a wall decoration.
Building one in an hour
List the decisions and deliverables down the left, not the tasks. Task-level matrices grow to two hundred rows and are abandoned within a fortnight; decision-level matrices stay at fifteen to twenty-five rows and remain readable.
Put the roles across the top rather than individual names where you can. Roles survive staff turnover; names require a rewrite every time someone moves team.
Fill it in live with the people it names in the room. A matrix drafted alone and circulated for comment collects silence, and silence is not agreement — it is deferral.
The four mistakes to avoid
Too many Consulted entries turns every routine decision into a committee, and delivery slows to the speed of the least available person. Be deliberate: consultation is a cost, not a courtesy.
No Accountable leaves decisions orphaned until they escalate as issues. Building the matrix once and never revisiting it makes it a historical artefact. Filling it in without the named people guarantees at least a third of it is wrong.
Add a review of the matrix to your phase-gate or quarterly checkpoint. Five minutes of maintenance prevents the slow slide into irrelevance.
Keeping the matrix useful after week one
A responsibility matrix decays quietly. People change roles, new workstreams appear, and within a quarter a third of the entries are wrong. Attach the review to something that already happens — a phase gate, a quarterly planning session — rather than relying on someone remembering.
Store it where the work happens, not in a slide buried in a shared drive. A matrix linked from the project home page gets consulted; one attached to a kick-off email does not.
Use it during conflict rather than after it. When two people believe they own the same approval, opening the matrix in the meeting resolves the question in seconds and, if the matrix is wrong, produces an immediate correction.
Frequently Asked Questions
- What is the difference between RACI and RASCI?
- RASCI adds Support: people who actively help the Responsible party complete the work without owning the outcome. It is useful where shared services do part of the delivery.
- How detailed should a RACI be?
- Aim for fifteen to twenty-five rows covering decisions and major deliverables. Beyond that, maintenance cost overtakes clarity benefit.
Published by AgilePro.info under our Editorial Policy. Guidance is based on established delivery practice and is general information, not professional advice for a specific project.