You build a RACI matrix for a cross-functional project by separating two things people usually blur: accountability for a decision and responsibility for a deliverable. Every row gets exactly one A. Every deliverable gets at least one R. Consulted is reserved for the people whose own work actually changes depending on the outcome — everyone else is Informed. Seniority and reporting lines do not enter into it. A RACI matrix records who decides and who does, and nothing else.
Key takeaways
- A row with five A's is not a matrix; it is a decision nobody owns, and it will stall exactly when the deadline arrives.
- Accountability follows the decision, responsibility follows the deliverable. On a flat team these are rarely the same person, and that is fine.
- Consulted is the most abused letter in the whole framework. If someone's work does not change based on the decision, they are Informed, not Consulted.
- A matrix that stays in a tool nobody opens solves nothing. Export it as a PDF with a few lines of SOP behind the highest-stakes row so the team can move without escalating.
The first draft: five people, five A's, no owner
Picture a product launch. Five people sit in the kickoff, all at the same seniority: engineering, marketing, sales, support, finance. Nobody reports to anybody else in the room. The project lead is a coordinator, not a boss.
The team does the right thing and builds a RACI matrix. The first draft comes back looking tidy. Engineering is A on build tasks. Marketing is A on the campaign. Sales is A on pipeline. Support is A on the handover docs. Finance is A on the pricing model. Every department head has claimed accountability for their own turf, which is reasonable and even correct.
Then look at the two rows that decide whether the launch happens on time.
The launch-date decision has five A's. Marketing, engineering, sales, support and finance each marked themselves Accountable, because each of them can individually block the date and each of them wanted that on record.
The go-live checklist has no R at all. Everybody assumed somebody else was assembling it.
That draft has a perfect disaster hiding inside it. It looks complete. It has letters in every cell. And it has guaranteed that the launch date becomes a negotiation between five equals with no tiebreaker, and the checklist gets done by whoever panics first, probably the night before.
Why a flat team breaks a RACI matrix on the first draft
When no one has authority over anyone else, everyone claims accountability for their own department and no one claims it for the shared decision. That is not ego — it is a rational response to being measured on your own function's results. The matrix just makes the pattern visible.
This is where a rule check earns its keep. Flags like "multiple A's in this row" and "no R assigned" are not nitpicks. They are the two failure modes that cost flat teams the most time: decisions that require a consensus that will never form, and deliverables that require a volunteer who never appears.
What to do with each flag
| Situation | What to do | Why |
|---|---|---|
| More than one A on a row | Name one. If two people genuinely share it, the row is too big — split it. | A decision with five owners is a decision with none. |
| No R on a row | Assign the person who will actually do or coordinate the work | Unassigned work gets done by whoever panics first, usually late. |
| Someone marked C on nearly everything | Ask: does your work change because of this decision? If not, mark I. | Every unnecessary C is a meeting, and every meeting is a delay. |
| A department head is A on their own deliverable | Keep it. Consider marking them AR if they also do the work. | Accountability and responsibility can sit with one person, as long as it is labelled. |
| The launch date has five A's | Move A to the project lead. Keep only the people whose work depends on the date as C. | Decisions need one name attached, or they need a VP who is not in the room. |
The corrected matrix
The fix is not to make the project lead the boss of the launch. It is to make them the owner of exactly one decision.
- Launch date decision — A: project lead. C: marketing, because campaign timing depends on the date, and support, because staffing depends on it. I: engineering and finance.
- Go-live checklist — R: engineering lead, coordinating the assembly. A: project lead. C: support, for the handover. I: sales and finance.
- Each department's own deliverables — A: that department head. R: the person doing the work. C: whoever downstream depends on that deliverable. I: everyone else.
Read the difference. The project lead is A on one row, not five. Each department head is still A on their own deliverables, so nobody lost authority over their function. And C has been cut down to the two people whose work genuinely shifts if the date moves — not the five who wanted a seat at the table.
That last cut is the one people resist. It feels rude to downgrade a colleague from C to I. It is not rude. It is the difference between a decision that lands in a day and one that takes two weeks of calendar Tetris.
Put the SOP behind the row that keeps getting escalated
A matrix tells you who decides. It does not tell you what deciding involves. That gap is where escalations live.
Behind the launch-date row, write a few lines: what has to be true before the date is confirmed, who signs off, what happens if a department is not ready, and how the date moves if it has to. Three to five sentences is usually enough.
Now the next time someone asks "can we push the date?", the answer is in a document instead of in a vice president's inbox. The team can act without escalating to someone who is not in the room — which is the entire point of doing this work in the first place.
You can draft the whole thing in the free RACI matrix generator at tools.exiuss.com/raci-matrix: list your roles and tasks, click a box to cycle through blank, R, A, AR, C and I, and let it flag the rows that break the rules. Write the SOP behind each task while you are there, then export the finished matrix as a PDF, CSV or text file and put it where your team already works.
Quick checklist
- List your decisions and deliverables as rows before you assign a single letter.
- Check every row: exactly one A. Split any row that seems to need two.
- Check every row: at least one R, and a named person behind it.
- Interrogate every C — if their work does not change because of the decision, mark I.
- Write three to five lines of SOP behind your highest-stakes decision row.
- Export as PDF and share it before the next kickoff, not after the next escalation.