RACI Matrix: A Practical Guide
/RACI (pronounced ray-c) MATRIX - Includes Free Template
The RACI matrix is an extremely useful stakeholder analysis tool. Here's an overview:
Knowledge Area: Business Analysis Planning & Monitoring
Applicable Task: Conduct Stakeholder Analysis
Useful When: Identifying stakeholders involved in a process. Helps the BA predict the level of involvement of each stakeholder by answering questions such as: Who handles what? Who knows about what? Who makes which decisions?
Also Known As: Responsibility Assignment Matrix, Linear Responsibility Chart
Definition:
R- “Responsible” for executing the task
A- “Accountable” for the outcome of the task, whether positive or negative; represents the sole decision-making authority
C- “Consulted” throughout the duration of the work; may provide advice as a subject matter expert
I - “Informed” of the outcome/progress of the work
I’ll use a simple process to bring it to life: Building a customer ordering system. See RACI matrix below.
RACI Matrix with roles on the vertical axis and tasks on the horizontal axis
PRACTICAL APPLICATION
- Identify the tasks involved in the process
- Identify the roles involved in the process
- Fill in the RACI template by matching each role to R,A,C or I, corresponding to the appropriate task.
Once the RACI matrix is done, it’s time to analyze and look for areas that MAY breed issues:
Review the matrix vertically (Roles)
- To many Rs under a role could mean that a person is overworked - consider splitting the tasks or getting additional resources.
- A role with too many As may become a bottle-neck in the future; consider delegation
Review the matrix horizontally (Tasks)
- A task with no R means no one is responsible for it. Ask yourself: Is this task necessary? If yes, consider assigning it to someone. If the task is unnecessary, consider eliminating it.
- A task with no A means no one is accountable. Every task must have one and ONLY one accountable person.
- Having too many Cs linked to a task can cause confusion and slow down the progress of the work; this is similar to having too many Is. Consider if informing and consulting so many people is necessary.
Do you have any additional ideas on how to analyze RACI matrices? Share by leaving a comment.
User story maps are an interesting and collaborative way of eliciting user requirements. One of the reasons why I find it so powerful is because it provides a unique approach for aligning discussions relating to the user, their goals, the process that supports the accomplishment of their predefined goals; and the requirements that need to be addressed to solve business problems.