RACI Matrix
RACI prevents the most common cause of project failure: nobody is sure who owns what. The framework forces explicit role assignment for each task, and it works only if every task has exactly one Accountable.
Origin
RACI emerged from the project management discipline in the 1950s-60s, formalized in IBM's project management handbooks and later adopted by management consultancies. The acronym is not attributable to a single inventor; the structure has been refined into many variants (RASCI, RACIO, DACI) that adjust the role labels for specific contexts.
The four roles
- Responsible (R) — does the work. Multiple people can be Responsible for one task; they're the ones doing it.
- Accountable (A) — owns the outcome and is the final approver. Exactly one person per task; if you have two Accountables, you have none.
- Consulted (C) — provides input before the work is done. Two-way communication. Often subject-matter experts whose perspective shapes the output.
- Informed (I) — kept up to date on progress and outcome. One-way communication. They don't shape the work; they need to know it's happening.
When RACI is the right tool
RACI is the right tool for: cross-functional projects where ownership has been ambiguous; recurring processes where role drift has crept in; new initiatives where decision rights need to be agreed up front; and audits or compliance work where role clarity is required. It's a poor fit for: small teams of fewer than 8 people (the overhead exceeds the value); creative work where the structure inhibits collaboration; or fast-moving operational decisions where the matrix becomes obsolete faster than it can be updated.
How to build a RACI
- List tasks vertically. Be specific — "design the form" rather than "design." Granular enough that one person can plausibly own each.
- List roles horizontally. Use roles, not names — RACIs by name go stale every time someone changes jobs.
- Assign A first. Each task needs one Accountable. If you can't decide between two people, the matrix has surfaced a real problem; resolve it before continuing.
- Assign R. Often the Accountable is also Responsible (denoted A,R). Sometimes the Accountable delegates the work to one or more Responsibles.
- Assign C and I sparingly. Every consultation costs time; every "informed" notification adds noise. Add only where genuinely needed.
- Validate with the people on the matrix. A RACI built in private will be ignored. Walk through it with the team; expect changes.
- Revisit when reality changes. RACIs go stale. Review at major project milestones or when team composition changes.
Worked example: a SaaS company launching pricing changes
A 200-person SaaS company is changing its pricing model — moving from per-seat to usage-based for the SMB tier. The change touches product, marketing, sales, finance, customer success, and legal. The RACI:
| Task | CFO | Head of Product | Head of Marketing | Head of Sales | Legal |
|---|---|---|---|---|---|
| Pricing model design | A,R | R | C | R | I |
| Customer impact analysis | R | R | I | A,R | I |
| Product changes (metering) | I | A,R | I | I | — |
| Customer communication | C | C | A,R | R | C |
| Legal review (contracts) | I | I | I | I | A,R |
| Sales team training | I | C | I | A,R | — |
The matrix surfaces immediate decisions: the CFO is Accountable for pricing model design (not the Head of Product, despite their build role) — a deliberate choice to anchor the decision in financial modeling. Sales is Accountable for customer impact analysis because they own the customer conversations; this prevents marketing from owning a number it can't influence.
How RACI goes wrong
- Too many Accountables. The most common failure. "Everyone is Accountable" means no one is. Force the choice.
- Too many Cs and Is. The matrix becomes performative; people add themselves to every row out of FOMO. Discipline is essential.
- Tasks too vague. "Marketing" is not a task; "Write the launch announcement" is. If the task can be broken into two with different owners, break it.
- Built and forgotten. A RACI is a living document. Without revisits, it freezes assumptions about a world that has moved on.
- Used as a substitute for relationships. RACI clarifies who owns what; it doesn't replace the trust and communication that make collaboration work.
Critique
RACI is procedurally rigid in a way that doesn't always match how knowledge work happens — informal channels often produce better outcomes than the matrix predicts, and over-formalization slows decisions. Variants like DACI (Driver, Approver, Contributor, Informed) better fit cross-functional decisions. The choice of variant matters less than the discipline of explicit role assignment, which is what makes RACI useful at all.