Project Smart ~ Exploring trends and developments in project management today

Calendar icon
Adobe PDF icon

How to Do RACI Charting and Analysis: A Practical Guide

~ By Royston Morgan

Project team in a huddle

RACI is an acronym that stands for responsible, accountable, consulted and informed.

A RACI chart is a matrix of all the activities or decision making authorities undertaken in an organisation set against all the people or roles. At each intersection of activity and role it is possible to assign somebody responsible, accountable, consulted or informed for that activity or decision.

When you hear these types of comments in an organisation a RACI Analysis may be overdue:

  • 'My boss always overrules my decisions whenever she wants'.
  • 'The approval process for even the simplest item takes so long today'.
  • 'It seems everyone is putting together a spreadsheet on the same data'.
  • 'Things are always slipping through the cracks'.
  • 'I have the responsibility, but not the authority to get the job done'.

Definitions of the RACI Categories

  • Responsible: person who performs an activity or does the work.
  • Accountable: person who is ultimately accountable and has Yes/No/Veto.
  • Consulted: person that needs to feedback and contribute to the activity.
  • Informed: person that needs to know of the decision or action.

A RACI analysis is useful for:

  • Workload Analysis: when used against individuals or departments overloads can be quickly identified.
  • Re-organisation: to ensure that key functions and processes are not overlooked.
  • Employee Turnover: newcomers can quickly identify their roles and responsibilities.
  • Work Assignment: allows duties to be redistributed effectively between groups and individuals.
  • Project Management: allows for flexibility in matrix management situations allowing for the right balance between line and project accountabilities.
  • Conflict Resolution: provides a forum for discussion and resolving inter-departmental conflict.
  • Documents the Status Quo: the output from RACI is a simple yet effective method of documenting the roles and responsibilities in an organisation.

How a RACI exercise is done:

  1. By identifying the functions and processes within the organisation or department and describing the key activities taking place. Avoid obvious or generic activities such as; attending meetings.
  2. By describing each activity or decision using a suitable action verb. Examples: Evaluate, Record, Monitor, Collect, Develop, Publish, Authorise, Schedule, Determine, Prepare, Approve, Inspect, Report, Decide, Write, Operate, Update, Conduct, Train, Review or Plan.
  3. When the action implies a judgment or decision (for example, evaluate, monitor, inspect, and review) create a phrase to indicate the primary outcome. Examples: Monitor service desk customer requests to identify training needs. Analyse call statistics to identify product problems.
  4. The activities or decisions to be made should be short and apposite and apply to a role or need, not to the specific person currently carrying out the task.
  5. Create a matrix with roles along the top and activities or tasks down the left side and in each of the table cells enter the appropriate RACI code.

When the analysis is done and the RACI matrix populated, any ambiguities need to be resolved. The matrix is reviewed and questions are asked of the data pattern to explore what it is telling us. The way to do this is to proceed along the vertical and then the horizontal axes in turn and for each column or row asking: If I find…then what does this mean?

Vertical Analysis

  • A lot of R's: Is it possible for the individual(s) to stay on top of so much? Can the activity be broken into smaller, more manageable chunks?
  • No empty spaces: Does the individual(s) need to be involved in so many activities? Are they a 'gatekeeper' or could management by exception principles be used? Can consulted be (R)educed to (I)nformed, or can things be left to the individual's discretion when something needs particular attention?
  • No R's or A's: Should this functional role be eliminated or have processes changed to an extent where resources could be reassigned?
  • Too many A's: Does a proper 'segregation of duties' exists? Should other groups be accountable for some of these activities to ensure checks and balances and accurate decision making throughout the process? Is this a 'bottleneck' in the process. Is everyone waiting for decisions or direction?
  • Qualifications: Does the level of the person fit the requirement of this role? Are too many senior personnel involved for routine decision making that could be deployed downwards?

Horizontal Analysis

  • No R's: Who is doing the job and getting things done? Are there too many roles waiting to be approved, be consulted or informed. Whose role is it to take the initiative?
  • Too many R's: Is this a sign of 'over the wall' activities?
  • No A's: Why not? There must be an 'A.' someone must be accountable for the thing happening - the buck stops with this person.
  • Too many A's: Is there confusion with too many fingers in the pie? It can also create confusion because every person with accountability feels they have final say on how the work should be done.
  • Too few A's and R's: The process may slow down while the activity is performed or the procedure may be outdated and can be streamlined if not needed.
  • Every box filled in: Do all the functional roles really need to be consulted? Are there justifiable benefits in consulting all the roles or is this just covering all the bases?
  • A lot of C's: Do all the roles need to be routinely informed or only in exceptional circumstances? Too many in the loop can slow the process down.
  • A lot of I's: If too many people are involved, usually too many C's and I's, it can dramatically slow things down.

Change Management Issues

Developing RACI charts surfaces many organisational issues because it reconciles the three elements of roles and responsibilities:

  • Role Conception: what people think their jobs are.
  • Role Expectation: what others in the organisation think another person's job function is and how it should be carried out.
  • Role Behaviour: what people actually do in carrying out their job.

RACI is a useful tool which can become overused and be a catch all for all types of problems, so be sensible about the level of granularity for the definition of tasks/activities. Take it to a deep enough level that it is meaningful and at a level of that is sensible. Who is responsible for making the coffee is not required. It is also important to stay focused on the original reason for undertaking the RACI exercise and ensure that this goal is achieved. Rather than creating a perfect RACI covering the organisation in exquisite detail be realistic and understand that 80% of the reality of a situation will be more than the organisation ever knew before the exercise was started.


This article is part of a series from a book on popular consulting techniques.


Advertisement


Comments (2)

Topic: How to Do RACI Charting and Analysis: A Practical Guide
5/5 (2)
Gravatar
Full StarFull StarFull StarFull StarFull Star
19th February 2016 4:36am
Martin Kioko (Nairobi) says...
I would like to understand the RACI principle in conflict management, who should be punished or rewarded for an act or omission. I am in an organization where RACI is applied, and I received a show cause letter when I had even escalated an issue to the next level.
Gravatar
Full StarFull StarFull StarFull StarFull Star
31st December 2016 7:45pm
Gustavo Gomez (Moses Lake) says...
I see the RACI chart as a "team requirement conversational tool" that is presented and discussed with all the stakeholders prior to starting a project. What I see missing is "signing-off" by the stakeholders. Missing deadlines or any failure by a team member should be captured, analyzed, and dealt with during the early stages of the development process. Therefore, the RACI chart should be considered a "living document" meaning that changes in tasks or responsibilities are conceivable and, if any of these should occur, it should be handled properly and quickly to help avoid missing deadlines.

Just my thoughts.

Gus

Add a comment



(never displayed)



 
2000
What is the next number: 2, 3, 4, ..?
Notify me of new comments via email.
Remember my form inputs on this computer.

Extreme Project Management

The running back dives for the first down with the defender on his back

Three war room strategies to try when you need to bring life back to a dead project, or save an engagement that is on the brink of disaster.

Demand a Strong Project Plan

Gantt chart

What to look for to advance your consulting projects from contract to execution.

How to Become a Project Manager

Senior lecturer in front of his class

If you're new to project management don't be bamboozled by all the jargon. This article sets out the skills needed to become a competent project manager.

Project Cost Management

Pile of British one pound coins

How do we know what a project will cost? We really don't until the project is complete because we can't accurately predict the future. What we can do is create an estimate.

PROJECT SMART is the project management resource that helps managers at all levels improve their performance. We provide an important knowledge base for those involved in managing projects of all kinds. With weekly exclusive updates, we keep you in touch with the latest project management thinking.

WE ARE CONNECTED ~ Follow us on social media to get regular updates and opinion on what's happening in the world of project management.


Latest Comments

Ashwini Pendharkar commented on…
10 Golden Rules of Project Risk Management
- Tue 20 June 1:32pm

Tery commented on…
A Brief History of SMART Goals
- Mon 19 June 10:10pm

Tammy Marin commented on…
Better Coaching Using the GROW Model
- Thu 15 June 10:37pm

Latest tweets

General Project Management • Please Advise: Does PRINCE2 Practitioner Exam Scenerio Changes… https://t.co/OK90gkJzMN #projectsmart #pmot about 11 days ago

RT @rkelly976: “I cannot give you the formula for success, but I can give you the formula for failure, which is: Try to please everybody.”… about 14 days ago

General Project Management • Re: Do I need project management software? https://t.co/u4Tu1fnzuY #projectsmart #pmot about 14 days ago