Apply Raci Matrix

---
name: apply-raci-matrix
description: Use when a project or recurring process has unclear ownership — tasks stall waiting on an unnamed decision-maker, or too many people weigh in on a decision that only needed one owner — assign each task exactly one Responsible doer and one Accountable owner, and explicitly limit who is Consulted (two-way input before the decision) versus merely Informed (one-way notification after it).
source: 'RACI responsibility assignment matrix, documented in Project Management Institute, "A Guide to the Project Management Body of Knowledge (PMBOK Guide)"; widely attributed origin in 1950s–60s matrix-management and organizational-design practice'
tags: [project-management, accountability, raci, organizational-design, roles-and-responsibilities]
related: [design-organizational-structure, apply-extreme-ownership, design-team-meeting-structure]
---

# Apply RACI Matrix

Assign each task or decision exactly one Responsible doer and one Accountable owner, and explicitly limit who is Consulted (two-way input sought before the decision) versus merely Informed (notified after it) — because unclear ownership, not lack of effort, is what causes tasks to stall and decisions to be second-guessed by people who were never meant to have a vote.

## Why This Is Best Practice

**Why best:** Most task and decision breakdowns in organizations are not caused by anyone failing to do their job — they're caused by nobody being clearly assigned the job of deciding or doing in the first place, or by too many people being given an implicit veto through vague "everyone should weigh in" norms. RACI's specific contribution is forcing exactly one name into the Accountable role per task — not zero, not several — because shared or absent accountability is what produces stalled decisions and diffused responsibility, and forcing exactly one Responsible doer per task prevents the common failure where a task assigned to "the team" gets done by no one in particular.

**PMBOK Guide and matrix-management practice:** The RACI matrix — Responsible, Accountable, Consulted, Informed — is documented as standard project-management practice in the Project Management Institute's PMBOK Guide, one of the most widely adopted project-management standards globally. Its four roles are specifically and narrowly defined: Responsible is the person who does the work; Accountable is the single person ultimately answerable for the task being done (and who must approve it); Consulted are people whose input is sought two-way before the decision is finalized; Informed are people who are notified one-way after the decision or task is complete, with no expectation of input. The matrix's discipline comes specifically from restricting Accountable to exactly one name per row — multiple "accountable" parties reintroduce the diffused-ownership problem the tool exists to solve.

**Adopted by:** RACI matrices are standard practice in project management across industries, documented in PMI's PMBOK Guide and taught broadly in project-management certification curricula (PMP and related credentials); widely used in matrix-managed organizations where cross-functional projects otherwise suffer from unclear ownership across departments.
**Impact:** The specific, measurable value of RACI is structural: it converts an implicit, often contested assumption about who owns a decision into an explicit, single-named assignment, and it explicitly caps the Consulted and Informed roles to prevent decision paralysis from too many people expecting a vote — a discipline credited across project-management practice with reducing the specific failure modes of stalled tasks (no one clearly Responsible) and re-litigated decisions (no one clearly, singularly Accountable).

## Steps

1. **List every significant task or decision in the project or process, one row per item.** Vague, bundled tasks ("marketing") should be broken down to a level where a single Responsible person and a single Accountable owner can be meaningfully named.

2. **Assign exactly one Accountable owner per row.** This person is ultimately answerable for the task being completed correctly and must have the authority to approve or reject the work — never assign more than one Accountable owner to the same task, since that reintroduces the diffused-ownership problem RACI exists to solve.

3. **Assign one or more Responsible doers per row — the people who actually perform the work.** The Accountable owner can also be the Responsible doer for smaller tasks, but for larger or cross-functional tasks these are often different people.

4. **Name specifically who is Consulted — whose input is genuinely sought, two-way, before the task or decision is finalized.** Keep this list deliberately short; every name added here adds a genuine two-way conversation the Accountable owner must have before proceeding, not just a courtesy mention.

5. **Name specifically who is Informed — who is notified, one-way, after the decision or task is complete, with no expectation of their input changing anything.** Being Informed does not entitle someone to revisit or re-litigate the decision; conflating Informed with Consulted is a common failure that reintroduces the delay RACI is meant to prevent.

6. **Publish the completed matrix and refer back to it explicitly when ownership becomes ambiguous mid-project.** The matrix's value comes from being consulted as the actual reference when a dispute or ambiguity arises, not just from having been created once at kickoff.

## Rules

- Never assign more than one Accountable owner to a single task or decision — shared accountability functions as no accountability.
- Every task must have at least one Responsible doer explicitly named; a task with no named Responsible party will stall regardless of how important it is.
- Keep the Consulted list short and genuine — everyone on it should receive an actual two-way conversation before the decision, not a courtesy notification.
- Treat the Informed role as strictly one-way and after the fact; being Informed does not grant standing to revisit a decision already made.

## Examples

**Cross-functional product launch:** A product launch spans engineering, marketing, and legal. Using RACI, the launch date decision has one Accountable owner (the product lead), with engineering and marketing leads Responsible for their respective workstreams, legal Consulted specifically on compliance risk before the date is locked, and the broader company Informed once the date is finalized — preventing the common failure where marketing, legal, and engineering each assume veto power over the date.

**Recurring approval bottleneck:** A recurring process (expense approvals, for instance) has been informally handled by "whoever's available," causing inconsistent delays. Assigning one specific Accountable approver per expense category, with clear escalation if that approver is unavailable, resolves the stalling that arose from no one being clearly, singularly responsible for the decision.

**Preventing decision re-litigation:** A team lead makes a technical architecture decision after consulting two senior engineers (Consulted) and notifies the rest of the team afterward (Informed). When a team member who was only Informed pushes to revisit the decision after the fact, the team lead points to the RACI assignment to clarify that input was already explicitly sought from the Consulted parties before the decision was finalized.

## Common Mistakes

- **Assigning multiple people as Accountable for the same task**, believing this provides more coverage — it instead reintroduces diffused ownership and the exact ambiguity RACI is meant to eliminate.
- **Conflating Consulted and Informed**, treating everyone who should eventually hear about a decision as though their input must be sought before it's made — this produces decision paralysis and defeats the purpose of limiting genuine two-way consultation to a short list.
- **Leaving a task with no named Responsible party**, assuming "the team" will handle it — tasks without a specifically named doer reliably stall.
- **Creating the matrix once at project kickoff and never referring back to it** when ownership disputes arise mid-project, losing the tool's actual practical value as a reference point.

## When NOT to Use

- For very small teams or simple tasks where ownership is already genuinely unambiguous — the overhead of formalizing a RACI matrix isn't justified when everyone already knows who owns what.
- For decisions requiring genuine group consensus rather than single-owner accountability (for instance, certain governance votes) — RACI's single-Accountable-owner structure is specifically for task and decision ownership, not for decisions designed to be made collectively.
- As a substitute for actually resolving an underlying authority conflict — if two people or departments have a genuine, unresolved dispute about who should hold the Accountable role, RACI documents the assignment but doesn't itself resolve the organizational conflict behind the disagreement.