What Is A RACI Matrix?
What Is A RACI Matrix?
The RACI matrix is a responsiblity assignment chart that maps out every task,
milestone or key decision involved in completing a project and assigns which roles
are Responsible for each action item, which personnel are Accountable, and, where
appropriate, who needs to be Consulted or Informed. The acronym RACI stands for
the four roles that stakeholders might play in any project.
In almost 100 percent of these rescue efforts, I have found that there is no shared
understanding of participant roles and responsibilities, nor is there explicit
documentation to support it. Establishing such a consensus by employing the RACI
model almost always gets a stuck project moving again, and enables the key
stakeholders to readily deal with the other issues that require resolution.
The four roles that stakeholders might play in any project include the following:
1. Identify all the tasks involved in delivering the project and list them on the left-
hand side of the chart in completion order. For IT projects, this is most
effectively addressed by incorporating the PLC steps and deliverables. (This
is illustrated in the detailed example below, after the simplified version
immediately below.)
2. Identify all the project stakeholders and list them along the top of the chart.
3. Complete the cells of the model identifying who has responsibility,
accountability and who will be consulted and informed for each task.
4. Ensure every task has at least one stakeholder Responsible for it.
5. No tasks should have more than one stakeholder Accountable. Resolve any
conflicts where there is more than one for a particular task.
6. Share, discuss and agree the RACI model with your stakeholders at the start
of the project. This includes resolving any conflicts or ambiguities.
Resolving conflicts and ambiguities in a RACI matrix involves looking across each
row and up and down each column for the following:
Are there too many R's: Does one stakeholder have too much of the project
assigned to them?
No empty cells: Does the stakeholder need to be involved in so many of the
activities? Can Responsible be changed to Consulted, or Consulted changed
to Informed? I.e., are there too many "cooks in this kitchen" to keep things
moving? (And if so, what does that say about the culture within which this
project is being managed?)
Buy-in: Does each stakeholder totally agree with the role that they are
specified to play in this version of the model? When such agreement is
achieved, that should be included in the project's charter and documentation.
No R's: Who is doing the work in this step and getting things done? Whose role is it
to take the initiative?
Too many R's: Is this another sign of too many "cooks in this kitchen" to keep things
moving?
No A's: Who is Accountable? There must be one 'A' for every step of the PLC. One
stakeholder must be Accountable for the thing happening -- "the buck stops" with this
person.
More than one A: Is there confusion on decision rights? Stakeholders with
accountability have the final say on how the work should be done and how conflicts
are resolved. Multiple A's invite slow and contentious decision-making.
Every box filled in: Do all the stakeholders really need to be involved? Are there
justifiable benefits in involving all the stakeholders, or is this just covering all the
bases?
A lot of C's: Do all the stakeholders need to be routinely Consulted, or can they be
kept Informed and raise exceptional circumstances if they feel they need to
be Consulted? Too many C's in the loop really slows down the project.
Are all true stakeholders included in this model: Sometimes this is more of a
challenge to ensure, as it's an error of omission. This is often best addressed by a
steering committee or management team.