RACI Matrix Explained: The 4 Letters and the One-A Rule (Full Example)
"Who's doing what on this release?" A RACI matrix answers that with four letters. In this video I build a full RACI matrix for a made-up online shop that is launching free returns: what responsible, accountable, consulted and informed really mean, the one-A rule, how to read a matrix by its rows and columns, a 6-step method to build one, the finished matrix, and the 5 mistakes to avoid.
Step by step
A RACI matrix is not an org chart
- A RACI matrix is not an org chart. It doesn't show who reports to whom. It shows who does what on each task. Tasks go down the side, roles go across the top, and each box gets R, A, C or I. The BABOK Guide calls it a responsibility matrix.
Explain like I'm 5: the restaurant kitchen
- Think of a restaurant kitchen. The cook makes the dish (Responsible). The head chef decides if it goes out and answers for it (Accountable). The guest is asked about allergies (Consulted, two-way). The waiter is told when it's ready (Informed, one-way).
The four letters (BABOK)
- The BABOK Guide defines the letters: Responsible: the people doing the work (can be several). Accountable: the one person who answers for it and decides. Consulted: people asked for input before, often experts, two-way. Informed: people told the outcome, one-way.
What you need before you start
- Before you start, get 3 things: a list of tasks small enough for one person to own, a list of roles (finance, warehouse) rather than only names, and a time box, such as one 30-minute meeting. Your stakeholder list is a good starting point.
The problem: nobody knew
- The example is an online shop launching free returns. Last time, a free shipping banner went live with the wrong order value, finance never saw it, and nobody knew who had signed it off. The RACI matrix answers who does what this time.
R: responsible
- R means Responsible: the people who do the work. A task can have more than one R. Every task needs at least one R, or nobody does it. If one person has an R on every row, they become the bottleneck.
A: accountable and the one-A rule
- A means Accountable: the one person who answers for the result and makes the final call. Give each task only one A. With two, each waits for the other. Here, finance is accountable for the refund rule.
C and I: consulted and informed
- C means Consulted: ask them before the work is done, and listen. The warehouse is consulted on the returns rules. I means Informed: tell them once it's decided. Customer service is informed. Every C costs time, so don't make everyone a C.
Read it by rows and columns
- Read the matrix 2 ways. Across each row, look for exactly one A and at least one R. Down each column, look for people with too many R's (overloaded) or too many A's (slowing decisions), and ask why any empty column is there.
Build it in 6 steps
- Build it in 6 steps: list the tasks, list the roles, give every task its A, add the R's, add the C's and I's sparingly, then check it and agree it with the people in it. Starting with the A keeps the matrix from filling up with C's.
Steps 1-2: tasks and roles
- Step 1: the 6 tasks are write the returns requirements, set the refund rule, build the returns page, accept the returns page, handle returned parcels and train the service agents. Step 2: the roles are sales manager, business analyst, developer, finance, customer service and warehouse.
Step 3: the A first
- Step 3: for each row, ask who answers for it if it goes wrong. Requirements, build page and accept page: the sales manager. Refund rule: finance. Returned parcels: the warehouse. Training: customer service. If two people want the A, split the task in two.
Step 4: add the R's
- Step 4: add the R's. The business analyst writes the requirements, runs the acceptance test and runs the training. Finance sets the refund rule, so it has both A and R. That's allowed. The developer builds the page and the warehouse handles parcels.
Step 5: C's and I's, be stingy
- Step 5: for the requirements, consult finance, customer service and the warehouse, and inform the developer. For the refund rule, consult the sales manager and business analyst, and inform the developer and customer service. If you won't wait for someone's answer, make them an I.
Step 6: check it and agree it
- Step 6: check that every row has one A and at least one R, then agree it in a short meeting, not by email. Here the warehouse asks for a say in the refund rule, so it becomes a C on that row.
Worked example: the finished matrix
- Requirements: business analyst R, sales manager A, finance, customer service and warehouse C, developer I. Refund rule: finance R and A. Build page: developer R. Accept page: business analyst R. Both: sales manager A. Parcels: warehouse R and A. Training: business analyst R, customer service A.
Replay last time's mistake
- Test it against last time's mistake. Finance is the only A on the refund rule, so nothing goes live until finance signs off. The warehouse is consulted before customers hear about it, and customer service is informed before day 1.
Where the matrix lives
- Keep the matrix where everyone can see it: a table in Excel or Google Sheets, or a Confluence page next to the requirements. Some teams also put the A on each Jira ticket as the owner. Keep one per release and update it when people or tasks change.
5 common mistakes
- 5 common mistakes: 2 A's on one task, the boss holding every A, consulting everyone, rows too big to own ("do the project"), and making the matrix once and never updating it.
Recap
- Recap: R does the work, A answers for it (only one per task), C is asked before (two-way), I is told after (one-way). Build it in order: tasks, roles, the A, the R's, the C's and I's, then check and agree it.
Common mistakes
- Two A's on one task. Shared accountability means each person waits for the other to decide. If 2 people both want the A, split the task into 2 smaller tasks, each with its own A.
- Making everyone a C. Every C is a review or an email you must wait for. Ask whether you will really wait for their answer; if not, make them an I.
- Giving the boss every A. Then every decision queues behind one busy person. Give the A to the person closest to the work who can answer for it, such as finance for the refund rule.
- Never updating the matrix. People change jobs and tasks change, so an old matrix sends questions to the wrong person. Link it from the plan and review it when people or tasks change.
When a business analyst uses this
Before a release, a business analyst runs a 30-minute workshop to fill in a RACI matrix for each deliverable, such as requirements, refund rules and acceptance testing. It shows who signs off each piece, so sign-off isn't chased later with "I thought you did".
Questions people ask
What does RACI stand for?
Responsible, Accountable, Consulted and Informed. Responsible people do the work, the one Accountable person answers for it, Consulted people are asked before, and Informed people are told after.
Why use a RACI matrix?
It makes clear who does each task and who makes the final call. That stops work from falling through the gaps and stops decisions from stalling because nobody knows who signs off.
How does a RACI matrix work?
Tasks go down the side, roles go across the top, and each box gets R, A, C or I. Each row should have exactly one A and at least one R.
