RACI matrix for a team of two or three
Published 22 September 2026
A RACI matrix is a grid of tasks against people, with every cell marked R, A, C or I. It was designed for projects that have a sponsor, a project office and a room full of interested parties. Most infrastructure work has one engineer, one colleague and a manager who wants a weekly update, and at that size the whole exercise collapses to two questions.
The two questions that survive
- Who signs off? That is the A, and there must be exactly one. It is the rule most often broken and the one that costs most.
- Who needs telling, and when? That is the I, and it is where small teams actually fail. The surprise is the damage, not the work.
If a matrix answers those two clearly, it has earned its hour even if half the grid is blank. If it does not, no amount of filling in the other cells will rescue it.
The failure mode when a four-role method meets a two-person team is predictable: a document where the same name is R, A and C on every single row. That is not a plan. It is an hour spent writing down that you are doing the work, which you already knew.
What the four letters mean
RACI, which expands to responsible accountable consulted informed, assigns one or more of those four letters to each person for each task. Done properly:
- Responsible: does the work. More than one person can be R on a task, and often is.
- Accountable: answers for whether it was done, and done correctly. Exactly one person, per task.
- Consulted: asked before the work, and it is a two-way conversation. Their answer can change what you do.
- Informed: told after, or at an agreed point, and it is one-way. They are not being asked to approve anything.
One person being both R and A on a row is completely normal, particularly on small work: you are doing it and you are answerable for it. That is not the problem. Two people being A is.
One A per row. Not two, not zero. Two accountable people means nobody is: each can reasonably assume the other has it, and at 2 a.m. in a change window that assumption is made by both at once. Zero accountable people means the task has an owner for the work and nobody who answers for the outcome, which is how a job gets done exactly as specified and still leaves everyone unhappy.
If you cannot name a single A for a row, the row is usually two tasks badly joined. Split it until each half has an obvious owner.
Consulted and informed are not degrees of the same thing
This is the distinction that gets muddled most, and it is the source of almost every "why wasn't I asked about this" conversation after the fact.
Consulted is before and two-way. You are telling someone what you intend to do while there is still time for them to change it, and you are obliged to listen. Marking someone C is a commitment to delay until they answer.
Informed is after and one-way. You are telling someone what happened, or what is about to happen at a point where their opinion is no longer part of the decision. No reply is required.
Both mistakes cost something. Recording someone as I when they expected to be C is the one that ends up in a post-incident review. Recording everyone as C when they only needed telling is quieter but not free: it means nothing moves until six people have replied to an email, which is how a two-week job becomes a two-month one.
When a RACI matrix is overhead
Often. It is worth saying plainly, because most writing on this subject assumes the answer is always yes.
For a two-person job that nobody outside the two will notice: reclaiming a VLAN, replacing a failed PSU, tidying a firewall object group: a RACI matrix is pure overhead. You will spend longer building the grid than doing the work, and the grid will say one thing: this person is doing it.
The honest test:
Are you about to change something that someone outside the room will notice?
If no, skip it and get on with it. If yes, the people who will notice are exactly the list you are about to write down, and that list is most of the value.
Note what the test is not: it is not "is this difficult" or "is this a big project". A one-line change to a DNS record can fail it badly, and a fortnight of structured cabling in an empty room can pass it.
Where it does earn its place
In infrastructure work there is a fairly short list of situations where a matrix repays the effort, and they have one thing in common: the boundary of your own authority is somewhere in the middle of the job.
- Cross-team change windows. The moment a second team has to be awake, someone has to be accountable for the window itself as distinct from the work inside it.
- Anything touching a system another team owns. You are R. You are almost certainly not A. Writing that down before the work is much easier than establishing it afterwards.
- Vendor-involved work. A vendor engineer is R on their part and never A for your outcome, and the matrix is the cleanest way to say so without it being a conversation about trust.
- Out-of-hours approval chains. The A must be a person who is contactable during the window, or the A must be delegated in writing to someone who is. An accountable person who is asleep is a decision that does not get made.
- Work with a back-out decision. Someone has to be able to call it. If that is not agreed in advance, it gets decided by whoever is most tired.
A worked example: replacing a firewall pair
Take a real shape of job. The perimeter firewall pair at a branch site is end of support and is being replaced out of hours. There is a site-to-site VPN to a payments provider that has to be rebuilt on the new hardware, one internal application that everybody notices when it stops, and a service desk that will take the calls if it goes wrong.
The team is two network engineers, an IT manager, the application owner and the service desk lead: five people, which is already enough for a matrix to be worth twenty minutes.
| Task | You | Second engineer | IT manager | App owner | Service desk |
|---|---|---|---|---|---|
| Rule base built and reviewed on the new pair | R, A | R | I | C | — |
| Change window agreed and published | R | I | A | C | I |
| VPN rebuild booked with the payments provider | R, A | I | I | C | — |
| Swap and recabling in the rack | R, A | R | — | — | — |
| Back-out decision during the window | R | C | A | C | I |
| Post-change service verification | R | R | I | A | I |
| Service desk told it is done and what to watch for | R, A | — | I | I | I |
Seven rows, three distinct accountable people, and most of the grid is you. That is what an honest small-team matrix looks like: it is not balanced, and it is not supposed to be.
The rows that justify the document are the three where the A moves away from you. The window belongs to the manager, because agreeing that a service will be down at 11 p.m. on a Thursday is not a network engineer's decision to make alone. The back-out call belongs to the manager too, and that is the row that needs a second sentence attached, because a manager who is unreachable at 1 a.m. has not delegated anything by going to bed. Either they are on the call, or the matrix says in writing that the A passes to you after a stated time. The backout plan is where that gets written down.
Verification belongs to the application owner. You can confirm the firewall is passing traffic and that the tunnel to the payments provider is up: a check that the service answers on its port from outside is the honest version of that test, but only the application owner can say the thing works properly. Making them A is also the only way that check reliably happens before everyone goes home.
The last row looks trivial and is not. A service desk that does not know a change happened will spend the following morning troubleshooting a symptom you already know the cause of.
Reading a matrix back before you rely on it
Four things to look for, all of which are visible in about ten seconds:
- A row with two As. Fix it now, because it will be found at the worst possible moment.
- A row with no A. Usually a task nobody wanted to own, which is a useful thing to have surfaced.
- A person who is C on everything. Either they are genuinely a bottleneck (worth knowing) or you have marked them C when you meant I, and you have quietly committed to waiting for them seven times.
- A column that is entirely I. That is fine, and it is often the most useful column on the page. It is the list of people who will otherwise be surprised.
And one test for the whole document: if every row reads R, A, C in the same column, you did not need a matrix. Delete it without guilt.
The informed column is the one that goes wrong
Small teams rarely fail because the work was unassigned. Two engineers know perfectly well who is doing what. They fail because a change landed on somebody who had not been told it was coming, and the cost of that is entirely out of proportion to the effort of a sentence sent in advance.
The reason it does not get sent is dull and practical: telling four different people means writing the same update four times, in four places, and nobody does that consistently for very long. So the I column decays into whoever you happened to be in a channel with that day.
RASCI, RACI-VS and the rest
There are variants. RASCI adds S for supportive, splitting the people who help from the person responsible. RACI-VS adds V for verifier and S for signatory, separating the person who checks the work from the person who formally accepts it. Others exist, and a few are genuinely useful in regulated environments where verification and sign-off must be different people by policy.
For a small team, be sceptical. If a plain RACI matrix is not working, the cause is nearly always that the A is ambiguous or the I list is incomplete, and adding a fifth letter fixes neither. The grid is called a RACI matrix or a RACI chart interchangeably, incidentally: there is no difference between the terms, and RACI is one form of what the project management literature calls a responsibility assignment matrix.
The short version
Name one person accountable per task. Write down who has to be asked before, and who only has to be told after. Skip the exercise entirely when nothing outside the room will notice. For a firewall migration with a colleague and a manager that is ten minutes of work, and it is the entire benefit: the rest of the method is scaffolding for an organisation you do not have.
Sources
- Responsibility assignment matrix: the broader category RACI belongs to, and a list of the lettered variants