RACI and Accountability Matrix: Keep the Gains Owned After the Project Team Leaves

The RACI and Accountability Matrix sits in the Sustain phase of RDMAICS. In the tool's own words, it lets you define RACI roles for ongoing sustainment activities to maintain clear accountability post-project. That is a narrow job, and a useful one.

RACI stands for Responsible, Accountable, Consulted and Informed. Responsible is the person who does the work. Accountable is the single person who answers for it. Consulted are the people whose input shapes it. Informed are the people who need to know the outcome.

Use the tool at the point of handover, not after it. The best time is while the project team still exists and can negotiate names into cells. Once the team has dispersed, you are no longer assigning accountability. You are asking for volunteers.

A second good moment is any review where the gains look soft. If a control chart has stopped being updated, the first question is not what happened to the process. It is who owned the chart.

The example used throughout this guide is the sample data built into the tool. It is fictional, and used only to show how the tool behaves.

The case is an accounts payable process that has just come out of an improvement project. Six sustainment activities have been identified. SPC monitoring, exception management, SOP maintenance, benefits tracking, an audit programme and training refresh.

Those six activities are the spine of the sustainment plan. Two of them watch the process itself. Two of them keep the documentation and the people current. Two of them check from the outside whether the gains are real.

Ten people or roles appear across the matrix. Some are operational, such as the AP Clerk and the AP team. Some are managerial, such as the AP Manager and the Process Owner. Some are governance, such as the Sponsor, the Black Belt and the Master Black Belt. Support functions appear too, in IT, HR and Finance.

The input is a single table. Each row is one sustainment activity. Each row then carries four role columns. The activity name and the Accountable column are marked as required. That is deliberate. An activity without a named accountable owner is not a sustainment activity. It is a hope.

In the worked case the rows read as follows. SPC monitoring has the AP Manager responsible, the Process Owner accountable, the Black Belt consulted and the Sponsor informed. Exception management has the AP Clerk responsible, the AP Manager accountable, IT consulted and Finance informed. SOP maintenance has the AP Manager responsible, the Process Owner accountable, HR consulted and the AP team informed.

Benefits tracking has Finance responsible, the Sponsor accountable, the Process Owner consulted and the MBB informed. The audit programme has the Black Belt responsible, the Sponsor accountable, the AP Manager consulted and the Process Owner informed. Training refresh has HR responsible, the Process Owner accountable, the AP Manager consulted and the AP team informed.

Notice the discipline in the naming. Every Accountable cell holds one role, not two. Where two names appear in a column, accountability splits, and split accountability behaves like no accountability at all.

The tool summarises the matrix into four figures. Six activities. Six of six with an accountable owner. Ten people or roles. Most often accountable, the Process Owner with three.

The tool then makes two plain observations. Every activity has an accountable owner. The AP Manager has a role in five of six activities.

Read those two statements together. The first is a pass. There are no orphan activities in this plan, which is the single most common failure in a handover document. The second is a caution. One role is involved in nearly everything, either as Responsible, Accountable or Consulted. That is a load question and a bus-factor question at the same time.

The Process Owner holding accountability for three of six activities is reasonable. SPC monitoring, SOP maintenance and training refresh are all process-health activities, and the process owner is the right place for them. The Sponsor holds benefits tracking and the audit programme, which sit above the process. The AP Manager holds exception management, which is day to day. That distribution makes structural sense.

The tool also offers an AI review that explains the result in context, which is useful when you are presenting the matrix to a steering group rather than to the project team.

A completed matrix is not a document. It is a set of decisions you can now make and defend.

Each of these decisions becomes harder to dodge once the names are written down. That is the point of the exercise.

A sustainment plan rarely collapses. It erodes. The signs are quiet and they are behavioural rather than numerical.

Watch for the Informed column going silent. In the worked case the Sponsor is informed on SPC monitoring and the MBB is informed on benefits tracking. If those reports stop arriving and nobody chases them, accountability has already thinned.

Watch for the Consulted column being skipped. SOP maintenance lists HR as consulted. If SOPs get updated without that consultation, the training refresh row quietly falls out of step with the documentation row.

Watch for role titles that no longer match real people. The matrix names roles, not individuals. That is good for durability and bad for detection, because a vacant role still looks filled on paper.

Finally, watch for the matrix itself going unreviewed. If the last edit date is older than the last reorganisation, the matrix is describing a structure that no longer exists.

The first mistake is treating the matrix as a completion task. Teams fill all twenty four cells in ten minutes, tick the deliverable and move on. The value is in the argument about who holds each cell, not in the cells being full.

The second mistake is putting a team in the Accountable column. The AP team appears twice in the worked case, both times as Informed. That is the correct use of a group name. Accountability needs one role.

The third mistake is confusing Responsible with Accountable. In SPC monitoring the AP Manager is responsible and the Process Owner is accountable. Those are different jobs. One updates the chart. The other answers for what the chart shows.

The fourth mistake is excluding the support functions. IT, HR and Finance each appear once or twice in the worked case. Leaving them out would make the matrix tidier and the plan weaker, because exception management, training refresh and benefits tracking all depend on them.

The fifth mistake is never revisiting it. A matrix built at handover is a snapshot. Put a date on it and a review interval next to the date.

Be honest about what the matrix does not do. It records an intention. It does not create accountability, and it cannot make anyone accept a role they were not consulted about. If the Process Owner was not in the room when three activities landed on them, the matrix is a plan written about someone rather than with them.

It also says nothing about whether the six activities are the right six. The tool counts activities. It does not judge coverage. You could build a clean matrix with every cell filled and still have no activity watching the one metric that matters most.

It carries no schedule, no effort estimate and no evidence. The AP Manager having a role in five of six activities is a count, not a workload. Whether that is twenty minutes a week or two days a week is outside the matrix entirely.

It does not measure performance. Six of six activities having an accountable owner tells you the plan is complete on paper. It tells you nothing about whether SPC monitoring happened last month or whether the benefit was realised.

Use it for what it is good at. It gives you a short, specific list of named commitments that you can read aloud in a review and check line by line. Pair it with the control plan and the benefits record, and the three together will tell you more than any one of them alone.