RACI

Overview

RACI is a Responsibility Assignment Matrix — a structured way to map people to tasks so that ownership is unambiguous. It has been embedded in project management and organizational design practice since the 1980s, appearing across PMI methodology, consulting engagements, and management training. No single inventor is reliably identified; the Responsibility Assignment Matrix concept appears in systems engineering literature from the 1950s–60s, and the RACI acronym became the standard form as organizational complexity grew in the decades that followed.

The four roles:

• Responsible (R): the person (or people) who do the actual work. Multiple R's are allowed — they share the execution.
• Accountable (A): the person ultimately answerable for the outcome — the one who approves or signs off. There must be exactly one A per task. This is the most important rule in the entire framework.
• Consulted (C): people whose input is sought before the work is done or the decision is made. Two-way communication — their views can influence the output.
• Informed (I): people who are kept in the loop after decisions are made. One-way communication — they need to know, but they don't have a say.

The critical distinction is between R and A. In practice, these are frequently confused or collapsed. Having two Accountable people for a task means neither is — accountability requires singularity. The Responsible can be a team; the Accountable must be one person who, when things go wrong, is the one who answers for it.

When to Use It

Whenever multiple people are involved in a decision or body of work and there is any ambiguity about who owns what. RACI is most valuable at the start of a project or initiative — before the confusion sets in — not as a post-hoc explanation of why things went wrong. Also useful for diagnosing organizational dysfunction: when a client's teams are duplicating effort, missing handoffs, or making conflicting decisions, a RACI analysis of those workflows almost always reveals the structural cause.

How It Works

1. List the tasks or decisions — on the rows of the matrix. Be specific enough to be useful: "approve the marketing budget" is a task; "marketing" is not.
2. List the stakeholders — on the columns. Include everyone who touches the work, not just the obvious owners.
3. Assign roles — for each task/stakeholder intersection, assign R, A, C, I, or leave blank (no involvement).
4. Validate the matrix with these checks:
   • Is there exactly one A per row? If multiple, consolidate.
   • Is there at least one R per row? If zero, who actually does this?
   • Does any column have too many R's? One person doing everything usually means someone else is underemployed or the roles aren't real.
   • Are there so many C's and I's that communication overhead is the real burden?
5. Discuss the gaps and conflicts — the matrix is a conversation starter, not a final decree. The most valuable output is often the disagreement it surfaces: "I thought you owned that."

Common Pitfalls

• Multiple Accountables — the most common failure; two A's means no A; force the conversation about who really owns it
• Confusing R and A — the manager who does the work is R; the executive who must answer for it is A; confusing them creates both micromanagement and unaccountability
• Too many Consulted and Informed — including everyone on the matrix adds noise; a C means you'll actually seek their input, not just notify them; an I means they need to know for their own work, not just because it seems polite
• RACI as bureaucracy — a 50-row RACI chart that no one maintains or uses defeats the purpose; start small, focus on the tasks where ownership is genuinely unclear
• Building it without the team — a RACI created by one person in a spreadsheet and then distributed lacks the buy-in that makes it work; build it in conversation

Recommended Books

• Flawless Consulting — Peter Block
• The Five Dysfunctions of a Team — Patrick Lencioni
• The McKinsey Engagement — Paul Friga