Responsibility Assignment Matrix (RAM)
A Responsibility Assignment Matrix maps who does the work, who owns the outcome, who has to be asked first, and who just needs to know, for every task, so authority and effort aren't scattered across a team pretending everyone is equally in charge.
Four boxes sit side by side, one per RACI letter, spelling out exactly what each role means before a single task gets filled in.
Reach for this when…
- A decision stalled because three people each thought someone else owned it.
- A project handover keeps breaking because responsibility was never actually assigned, just implied.
- You're bringing in a cross-functional team and roles overlap by default.
How to run it
- List every task or decision that needs an owner.
- For each one, name who is Responsible for doing it.
- Name exactly one person who is Accountable for it. Never two.
- Name who must be Consulted before it happens and who is Informed after.
- Review the matrix with the team before work starts, not after it stalls.
A worked example
Situation. Marco Ricci ran a mid-sized construction firm in Bologna, Italy, where a site handover had stalled twice because the structural engineer and the project manager each assumed the other had signed off on a safety variance.
Applied. He built a RAM for the handover naming exactly one Accountable person, the project manager, and moved the engineer to Consulted.
Result. The next handover on a similar project cleared in two days instead of three weeks, because there was exactly one name to chase.
The catch
The matrix only works if people actually behave differently once it's written, and plenty of teams file it away and carry on as before. Naming one Accountable person also concentrates real power, which some organisations resist for political reasons that have nothing to do with efficiency. It documents authority. It doesn't grant the skill to use it well.
Two Accountable names on one task is not a safety net. It's how the task ends up owned by nobody.