RACI Matrix

Purpose

The RACI Matrix eliminates ambiguity about who does what. For every key task or decision, the team assigns exactly one Accountable person (the final decision-maker), one or more Responsible people (who do the work), Consulted stakeholders (whose input is sought), and Informed parties (who are kept in the loop). The result is a clear contract that prevents duplication, gaps, and finger-pointing.

At a glance

How to run

1. List tasks/decisions (5 min): Down the left column, list the key tasks, deliverables, or decisions.
2. List roles/people (3 min): Across the top row, list the roles or individuals involved.
3. Assign RACI (20 min): Go cell by cell. For each task, assign R, A, C, or I to each role. Enforce: exactly one A per row.
4. Review patterns (5 min): Look for overloaded individuals (too many Rs or As), empty rows (nobody assigned), and missing Cs (stakeholders who should have input).
5. Confirm (2 min): All parties agree to the matrix. Document and share.

Materials needed

• Spreadsheet, whiteboard grid, or printed template
• Task/decision list (prepared in advance)
• Role/person list

Pitfalls & common mistakes

• Multiple As in one row: Only one person can be accountable per task. If there are two, nobody is.
• Confusing R and A: R does the work; A owns the outcome and has final say.
• Too granular: Keep tasks at a meaningful level. Every sub-task does not need a RACI.
• Never updating: The RACI should evolve as the project evolves.

Inclusion & accessibility

• Use a digital shared document so remote participants can contribute.
• Walk through the matrix together rather than filling it in silently — silent completion leads to misaligned expectations.
• Use colour coding for quick visual scanning.

Variations

• RASCI: Adds Supportive (S) for people who assist R but are not the lead.
• DACI: Decision-maker, Approver, Contributor, Informed — popular at Atlassian.
• RAPID: Recommend, Agree, Perform, Input, Decide — Bain & Company's version.

When NOT to use this

• For very small teams (2–3 people) where roles are obvious.
• When the project is highly fluid and roles change daily — the overhead of maintaining the matrix is not worth it.
• When a simpler tool (e.g., task board with assignees) suffices.

Source & further reading

• Project Management Institute (PMI)
• MindTools: RACI Matrix
• Atlassian: DACI Decision-Making Framework