Skip to main content

Why Use a RACI Matrix?

Not too long ago, I was involved in a post implementation meeting for a change that was not very successful. During the meeting there was a very heated discussion, some of the comments I heard were: 
  • ‘I thought you were going to do that’
  • ‘That is not my responsibility”
  • ‘Why wasn’t I informed that this was occurring’
  • 'I have the responsibility, but not the authority to get the job done'
  • ‘I knew how to fix the issue, but no one ever asked me’  
It occurred to me that having a RACI chart would address these comments. The RACI model is a straight forward tool used for identifying activities and relating them to roles and responsibilities, thus avoiding confusion over who does what and how people are involved. The acronym RACI stands for: 
  • Responsible: This role is responsible for the correct execution of process and activities. This person or persons do the work to achieve the task.
  • Accountable: This role has ownership of the quality and the end result of the process. This must be one person and is often the project executive or project sponsor. 
  • Consulted: This role has involvement through input of knowledge and information. They provide information for the project and with whom there is two-way communication. This is usually several people, often subject matter experts.
  • Informed: This role receives information about process execution and quality. These are the people who are kept informed about progress and with whom there is one-way communication. They are usually affected by the outcome of the tasks so need to be kept up-to-date. 
Putting together an authority matrix can be a time-consuming, but worthwhile, task. This chart will clarify to all involved which activities they are expected to fulfill, as well as identify any gaps in service delivery and responsibilities. Without clearly defined roles and responsibilities it is easy for projects to run into trouble. When people know exactly what is expected of them, it is easier for them to complete their work on time, within budget and to the right level of quality. A RACI matrix is used to discuss, agree and communicate roles and responsibilities.

Comments

The said…
Agree that using the RACI language on a project is invaluable, even if you don't want to take the time at the beginning to straighten out everyone's role by constructing a full matrix.

What do you think the barriers are to using RACI? I am finding that many companies "know" it but are not using it fully ...

Cassie Solomon, RACI-Training
Vladimir said…
As a greatest barrier I see making this too complex and too big when communicating to people.
This is why I rather use words 'who does what' instead of RACI matrix.
I admire ITSM professor writes concise and easy to understand articles about quite complex things.
S.Covey has a lot of things about importance of 'who does what' in his book 'Predictable Results in Unpredictable Times'.
Thanks for your comments, and the book recommendation. I've not read it, so I've added to my list.

Popular posts from this blog

What is the difference between Process Owner, Process Manager and Process Practitioner?

I was recently asked to clarify the roles of the Process Owner, Process Manager and Process Practitioner and wanted to share this with you.

Roles and Responsibilities:
Process Owner – this individual is “Accountable” for the process. They are the goto person and represent this process across the entire organization. They will ensure that the process is clearly defined, designed and documented. They will ensure that the process has a set of Policies for governance.Example: The process owner for Incident management will ensure that all of the activities to Identify, Record, Categorize, Investigate, … all the way to closing the incident are defined and documented with clearly defined roles, responsibilities, handoffs, and deliverables. An example of a policy in could be… “All Incidents must be logged”. Policies are rules that govern the process. Process Owner ensures that all Process activities, (what to do), Procedures (details on how to perform the activity) and the policies (r…

How Does ITIL Help in the Management of the SDLC?

I was recently asked how ITIL helps in the management of the SDLC (Software Development Lifecycle).  Simply put... SDLC is a Lifecycle approach to produce the software or the "product".  ITIL is a Lifecycle approach that focuses on the "service".
I’ll start by reviewing both SDLC and ITIL Lifecycles and then summarize:
SDLC  -  The intent of an SDLC process is to help produce a product that is cost-efficient, effective and of high quality. Once an application is created, the SDLC maps the proper deployment of the software into the live environment. The SDLC methodology usually contains the following stages: Analysis (requirements and design), construction, testing, release and maintenance.  The focus here is on the Software.  Most organizations will use an Agile or Waterfall approach to implement the software through the Software Development Lifecycle.
ITIL  -  is a best practice for IT service management (ITSM) that focuses on aligning IT services with the needs …

Incidents when a Defect is Involved

Question: We currently track defects in a separate system than our ticket management system. With that said, my question is does anyone have suggestions and/or best practices on how to handle incidents when a defect is involved? Should the incident be closed since the defect is being worked on in another defect tracking system if it is noted in the incident ticket? I am considering creating an incident statuses of 'closed-unresolved' so the incident can still be reported on in our ticket management system but know it is being worked on/tracked in the defect system. With defects, it is possible that we may never work on them because they are very low priority and the impact is low to the user. However, in some cases a defect is being worked on. Should we create a problem ticket instead?
Thanks, René W.

Answer: RenĂ©. In ITIL, the activity you are describing is handled by the Problem Management process. ITIL does not use the term “defect” but it does use the term “known error” to…