Quick reference
Memory aid
R does it, A owns it, C advises, I hears about it. One A per task, always.
TL;DR
For every task, assign: R (does it), A (owns it — exactly one), C (advises before), I (told after). Minimize C's to prevent bottlenecks. Review and update regularly.
What Is RACI Matrix?
RACI is a simple chart that answers 'Who does what?' for every task. For each task, you assign four types of involvement: R (does the work), A (owns the outcome), C (gives input before), I (told after).
A RACI matrix is a grid with tasks/decisions on rows and people/roles on columns. Each cell contains R, A, C, or I. Rules: every task needs exactly one A (the buck stops here), at least one R (someone does the work), and C and I as needed. The matrix eliminates confusion about roles, prevents tasks from falling through cracks, and reduces unnecessary involvement that slows decisions.
RACI Matrix Example
A matrix with tasks as rows and roles as columns. Each cell contains R, A, C, or I.
| Task | PM | Dev Lead | Designer | QA |
|---|---|---|---|---|
| Define requirements | R/A | C | C | I |
| Create designs | I | C | R/A | I |
| Build feature | I | R/A | C | I |
| Test & sign off | A | I | I | R |
Origin & context
The RACI chart grew out of responsibility assignment matrices, also called linear responsibility charts, long used in project management and systems engineering. No single originator is credited. It became widely adopted as organizations grew more complex and cross-functional.
Core Components
Responsible (R)
The person who does the work. Multiple people can be R for a task.
Example
The developer writing the code for a feature.
Accountable (A)
The one person who owns the outcome and has final decision authority. Only one A per task.
Example
The product manager who approves the feature as complete and meeting requirements.
Consulted (C)
People whose input is sought before the work is done — two-way communication.
Example
The security team consulted on data handling requirements before development starts.
Informed (I)
People who are kept updated on progress or outcomes — one-way communication.
Example
The VP of Engineering informed when the feature ships.
When to Use RACI Matrix
Project role clarity
Problem it solves: Eliminates confusion about who does what, especially in cross-functional projects.
Real-world application
A product launch team creates a RACI covering 30 tasks across marketing, engineering, sales, and legal, eliminating the 'I thought you were doing that' moments.
Organizational restructuring
Problem it solves: Clarifies how roles and responsibilities change in a new organizational structure.
Real-world application
After a merger, a RACI matrix can be created for all key processes to clarify which organization now owns what — reducing duplicate work and gaps.
Every row should have exactly ONE 'A'. If a task has zero A's, nobody owns it. If it has two A's, nobody owns it either.
How to Apply RACI Matrix: Step by Step
Before you start
- →A list of tasks, decisions, or deliverables
- →A list of roles or people involved
- →Stakeholder agreement to participate in RACI creation
List Tasks and Roles
Create the rows (tasks) and columns (roles/people).
Tips
- ✓Be specific about tasks — 'Marketing' is too vague; 'Create launch press release' is actionable
Common mistakes
- ✗Tasks too broad or too granular
Assign RACI
For each cell, assign R, A, C, I, or leave blank.
Tips
- ✓Start with A — who owns each outcome?
Common mistakes
- ✗Assigning multiple A's to avoid conflict — this always backfires
Validate
Check the matrix: exactly one A per row, at least one R, minimal C's.
Tips
- ✓Review with all listed people to get buy-in
Common mistakes
- ✗Creating the RACI without input from the people listed
Communicate and Use
Share the RACI and reference it when role confusion arises.
Tips
- ✓Post it visibly and update as roles change
Common mistakes
- ✗Creating the RACI and filing it away — it's a living tool
Value & Outcomes
Primary benefit
Eliminates role confusion by making responsibilities explicit and unambiguous.
Additional benefits
- ✓Reduces unnecessary consultation that slows decisions
- ✓Prevents tasks from falling through cracks
What you'll learn
- →How to clarify roles and responsibilities in any project or process
- →How to streamline decision-making by reducing over-consultation
Typical outcomes
Best Practices
📋 Preparation
- •List all key tasks and decisions
- •Identify all relevant roles
🚀 Execution
- •Enforce one A per task
- •Minimize C assignments to prevent bottlenecks
🔄 Follow-Up
- •Review and update the RACI as the project evolves
- •Use it to resolve role disputes
💎 Pro Tips
- •If someone is C on everything, they are a bottleneck. Challenge whether they truly need to be consulted or just informed.
Too many C's on a task means decision paralysis. If everyone must be consulted, nothing moves. Be ruthless about who truly needs to be consulted vs. informed.
Limitations & Pitfalls
Static — doesn't capture how roles change over time
Mitigation: Review and update the RACI at phase transitions
Doesn't capture the quality or depth of involvement
Mitigation: Supplement with process documentation for complex tasks
Where this comes fromMultiple origins in project management practice introduced this.
More Management Frameworks
Other frameworks in the Stratrix library.
Wardley Mapping
A strategic mapping technique that visualizes the components needed to serve a user need, arranged by their position in the value chain (visibility) and their stage of evolution (genesis to commodity), revealing strategic options and moves.
Project & Product ManagementLean Startup
An entrepreneurial methodology that uses a Build-Measure-Learn feedback loop, minimum viable products (MVPs), and validated learning to rapidly test business hypotheses and reduce the risk of building products nobody wants.
Project & Product ManagementStage-Gate Process
A product development framework that divides the innovation process into stages separated by gates (decision points), where management reviews progress and decides to go, kill, hold, or recycle the project.
Project & Product ManagementKanban
A visual workflow management method that uses boards, cards, and work-in-progress limits to optimize the flow of work through a system, enabling teams to deliver continuously without the structure of fixed-length sprints.
Project & Product ManagementJobs-to-be-Done
A product innovation framework that focuses on the underlying 'job' customers are trying to accomplish rather than the product itself, revealing unmet needs and disruptive innovation opportunities.
Project & Product ManagementDesign Thinking
A human-centered innovation methodology with five phases — Empathize, Define, Ideate, Prototype, and Test — that uses deep user understanding and rapid experimentation to solve complex problems creatively.
More from Stratrix
Test a decision, free
Set a live decision against the companies that made it before you.
AcquisitionsThe Distance TestDivestituresThe Divestiture TestDiversificationThe Diversification TestMake or buyThe Make-or-Buy TestAll Access
Every Casebook, three Strategy Packs a seat each year and the Analyst, for teams that face these decisions all year.
$1,999 a year · $499 a seatWhat is included →New analyses, by email
The defining moves in business, checked against the record, as they publish.
See RACI Matrix in the wild.
Follow RACI Matrix across the companies and lenses where it actually shaped the strategy — the decision, the rationale, and how it played out.