Role Clarity: Building a RACI Matrix That People Actually Use
Many RACI charts end up in a shared folder nobody opens. Here is how to build a smaller, sharper RACI matrix around real decisions, and keep it in daily use.

Somewhere on your shared drive there is probably a RACI chart, a grid showing who is Responsible, Accountable, Consulted and Informed for each task. It has sixty rows, nine columns and a colour code that made sense to the person who built it. Nobody has opened it since the workshop where it was created.
The idea behind a RACI matrix is sound. Every task or decision should have one person accountable for it, clear people doing the work, and clear lists of who to consult and who to inform. The trouble lies in how RACIs are usually built and what happens to them afterwards.
A quick reminder of the four letters
- Responsible: the person or people who do the work.
- Accountable: the single person who owns the outcome and makes the final call. One per row, always.
- Consulted: people whose input is needed before the work is done or the decision is made. This is two-way communication.
- Informed: people who need to know the result. This is one-way communication.
In practice, RACI exercises often make confusion worse, because they paper over disagreements instead of resolving them.
Why most RACI charts die quietly
Four patterns explain most of these failures.
They list activities, not decisions. Rows such as “manage inventory” or “handle customers” are too broad to assign. Everyone touches them, so everyone gets a letter, and the chart says nothing useful.
They avoid the hard rows. The rows that cause real friction, such as who can approve a discount above the standard limit or who decides when a late order ships partially, get skipped because they spark arguments in the workshop. Those are precisely the rows that matter.
They put more than one A on a row. Two accountable people means nobody is accountable. It usually happens when senior people do not want to give up control or offend each other.
They are never used again. The chart is not linked to anything people do daily: not to procedures, not to approval workflows, not to onboarding. It becomes a document about the organisation rather than a tool within it.
Building a RACI around real decisions
Consider a pharmaceutical distributor in Amman where customer returns cause constant friction. Sales promises credits, the warehouse refuses damaged goods, quality wants to inspect everything, and finance does not know when to issue the credit note. A focused RACI for this one process might look like this:
| Decision or task | Sales rep | Warehouse supervisor | Quality officer | Finance accountant | Sales manager |
|---|---|---|---|---|---|
| Accept a return request from a customer | R | I | I | I | A |
| Receive and log returned goods | I | A/R | I | ||
| Decide if goods are resaleable, to be destroyed or returned to supplier | C | A/R | I | I | |
| Issue the credit note | I | C | A/R | I | |
| Approve credit above the rep’s limit | R | C | A |
Five rows, five roles, one A per row. Everyone can read it in a minute, and it settles the arguments that were actually happening.
Notice what the chart forces into the open. Before, sales reps promised credits on the phone and finance learnt about them from an angry customer. Now the rep can only request, the sales manager accepts, and quality decides what happens to the goods before finance issues anything. The warehouse supervisor, who used to be blamed for refusing returns, has a clear job: receive, log and hand over. Nobody’s workload grew. The arguments simply had nowhere left to happen.
Steps to a RACI that works
- Pick one process with real friction. Do not try to map the whole organisation at once. Start where the arguments are.
- List decisions and handoffs, not general activities. Phrase each row with a verb and an object: approve the discount, release the order, confirm the delivery date.
- Use roles, not names. People change jobs. The role of warehouse supervisor stays. Add names in a separate list if helpful.
- Assign the A first. For each row, agree who owns the outcome before discussing anyone else. If the group cannot agree, escalate to the person who can decide, and do not leave the room with a blank.
- Keep C short. Every person consulted adds time. Ask whether their input changes the decision. If not, move them to I.
- Test with real cases. Take three recent examples, such as last week’s disputed return, and walk them through the chart. If the chart would not have prevented the confusion, a row is missing or wrong.
Keeping it alive after the workshop
A RACI becomes useful when it is built into the way work runs. Copy the relevant rows into the standard operating procedure for that process, so each step names its owner. Configure approval workflows in your systems to follow the same accountabilities, so the person marked A is the one who receives the approval request. Use the chart when onboarding someone into any role that appears in it.
In family businesses, a senior family member often holds an informal veto over many decisions. It helps to name that openly as the A on the rows where it truly applies, and to agree where it does not. A chart that shows where authority really sits is far more useful than one that pretends otherwise.
Then review it whenever the structure changes, and at least once a year. When a dispute comes up that the chart does not cover, add the row. Over time the RACI becomes an up-to-date record of how decisions are made, rather than a snapshot of one workshop.
Clear roles as part of a clear operation
Pick the process that caused the most arguments last month and build its RACI in a one-hour session with the people involved, using the six steps above. Then test it against the next three real cases before rolling the format out to other processes.
Role and ownership clarity is a core part of our Operations Transformation service. We help you settle the difficult rows, link them to procedures and systems, and keep accountability clear as the organisation grows.



