Every project has one. A neat grid, rows of deliverables down the side, names across the top, each cell filled with a carefully chosen letter. Responsible, Accountable, Consulted, Informed. It was built in week one, shared in the kick-off deck, saved in the project folder, and it has not been opened since.
I'm not saying this to be smug. I've created plenty of them. And I can count on no fingers the number of times someone on the team, mid-crisis, said "hang on, let me check the RACI".
Nobody reads the RACI. That's not really the problem, though. The problem is what we think the RACI did for us.
The unknown RACI
My favourite example. A company I worked at once produced a RACI at a team offsite. In person, properly facilitated, sticky notes and everything. A good day's work by the people in the room.
The catch: most of the names on it weren't in the room. They didn't know the RACI existed. Several of them were never told it existed. So there was a document assigning accountability to people who had no idea they were accountable, for decisions they didn't know were theirs to make.
Think about what that means in practice. When one of those decisions arrived, the person who was officially accountable didn't step up, because as far as they knew, it wasn't their decision. Everyone who'd been at the offsite assumed it was handled, because the grid said so. The grid was correct. It was also completely invisible to the one person it most needed to reach.
And to add insult to injury, in at least one case that person had since left the company. The RACI was still confidently assigning accountability to someone who no longer worked there. You can't get much less accountable than not being employed.
Accountability someone doesn't know about isn't accountability. It's an expensive surprise with a hefty delay on it.
What happens when the decision lands
That story is extreme, but the everyday version is universal. Six weeks into a project, the client asks to move the launch date. Or a developer finds the chosen payment provider can't do what the design assumes. Or two senior people give opposite feedback on the same page. Someone has to decide, now, and everyone's thinking the same thing: whose call is this?
At that moment, people don't open a spreadsheet. They look at each other. Then at whoever seems most senior, or speaks first, or is most annoyed. The decision gets made by whatever the room's social dynamics produce, which is sometimes the right person but often isn't.
Meanwhile the RACI sits there, correct and unconsulted, like a fire evacuation plan stuck on the back of a door nobody opens.
The four columns, honestly
Each letter rots in its own way.
- Responsible is usually fine, because it's obvious. The person doing the work knows they're doing the work. You didn't need a grid for this.
- Accountable is the only column that really matters, and the one most often broken. Count the As on each row of your last RACI. If a row has two, you haven't assigned accountability, you've assigned a future argument. And if the A belongs to someone who doesn't know they have it (see: the offsite), you've assigned nothing at all.
- Consulted is the column everyone secretly wants, and it's worth understanding why. Being consulted means your input is sought before a decision. In practice it can mean the right to give "helpful" feedback at the very last moment before launch, and certainly not a moment earlier. No ownership, no risk, and a guaranteed opportunity to be right in hindsight. It's the best seat in the house.
- Informed becomes a mailing list. Everyone in the I column gets the update, almost nobody reads it, and one day one of them discovers something in a meeting you "informed" them of three weeks ago, and it lands as though they'd never heard it. Technically you told them. Practically, you didn't.
When the RACI becomes a hit list
Which brings me to the second my second RACI example, and learned something I hadn't expected.
The resistance wasn't to the admin. It was to the letters. Getting it in place felt less like agreeing responsibilities and more like drawing up a hit list: who will be gone after when X goes wrong? I didn't cotton on immediately but soon realised that 90% of the room people saw it that way, and the expected behaviour followed. Nobody wanted to be an 'R' of anything. Everyone wanted to be a 'C'.
That's not people being lazy. It's people reading the culture correctly. If the organisation uses the grid to find someone to blame, then being named on it is a risk, and the rational move is to be named as little as possible, in the safest column available. The RACI doesn't create that culture. It just shows it to you, in writing, in a way that's hard to argue with.
Which is also why a lot of RACIs are really written for the leadership and the project manager. It feels like control. It's evidence for the post-mortem: it's in the kick-off deck, slide nine. But a document written to win a future argument does very little to prevent it, and if the team can smell that it's a blame register, they'll do exactly what that team did and keep their names out of it.
What to do instead
I'm not saying bin the RACI. The exercise is valuable. It's just valuable for different reasons than people think.
- Build it with the people on it. Obvious after the offsite story, and still routinely skipped. If someone's name goes in the A column, they should be in the conversation, or at the very least told directly, not left to find out from a slide or a document 'mentioned' notification.
- Treat the conversation as the deliverable. The useful moment is when two people discover they both think they own a decision, in a calm room rather than a tense one. The grid is just the minutes of that conversation.
- Test it with scenarios. Don't ask "is everyone happy with this?", because everyone will say yes. Ask "the client wants to cut the budget by 20%, who decides what goes?" People only discover they disagree when the question gets concrete.
- One A per row. Always. If you can't get to one, the disagreement is real and needs solving now, not parking in a cell with two letters in it.
- Give 'Consulted' a deadline. If your input is being sought, it's being sought by a date. Feedback that arrives after that date is noted, not actioned. This one change quietly kills the last-minute helpful comment, and everyone knows exactly why you're doing it.
- Make the 'R' safe. If people are avoiding the Responsible column, the problem isn't the grid, it's what happens to people when things go wrong. Say out loud, and then prove, that the RACI is for clarity, not for blame. You prove it the first time something goes wrong and you back the R instead of pointing at the cell.
- Put decision owners where people already look. Nobody opens the folder, but everyone opens the brief, the ticket and the channel. One line at the top, "Decision owner: Priya", beats a whole grid nobody visits.
The real job
A RACI was never meant to be a document. It's a set of agreements about who decides what, and agreements only exist in people's heads. Your job isn't to produce the grid. It's to make sure that when the hard question arrives, everyone already knows the answer, and that being the one who owns it doesn't feel like painting a target on your back.
Get that right and nobody will ever read your RACI.
That's fine.
They won't need to.