RACI Matrix

RACI Matrix/Chart is the type of responsibility assignment matrix for effective work organization, communicating the responsibilities.
Read more

RACI Matrix/Chart is the type of responsibility assignment matrix for effective work organization. Defines and communicates the roles and responsibilities of various entities, especially when the roles and responsibilities are unclear or when additional clarity is needed. It is usually depicted as a simple chart, where you assign people or groups to specific tasks.


Who is responsible? Direct responsibility for the work, usually, they develop and complete the deliverables themselves.


Who oversees the work? Delegate and review the work, they keep the deadlines and are accountable for the work.


Who provides additional info or support? Provide input or feedback on work, their opinions need to be taken into account.


Who to keep up to date? Updated about the progress of work, they mostly do not interact directly with the work, but the outcomes are important to them.

How to

  1. Create a list of all items that are important enough to be included, but keep in mind to use the right granularity for the context of your RACI matrix
  2. Create a list of all people involved in the work as a whole
  3. Create a table with one list as a first column and the second one as a first row
  4. Capture relations between items and people (replace with entities) by entering the letters R, A, C, I to reflect the interaction hierarchy/ structure
  5. If there are entities with no connection to tasks remove them

RACI Matrix/Chart

Similar posters

CEDAR Feedback
CEDAR Feedback CEDAR is a structured feedback model providing coaching opportunities via repeated revisiting and readjusting of the feedback and the goals.
STATIK Kanban The Systems Thinking Approach To Introducing Kanban (STATIK) is a repeatable way to start with Kanban resulting in continuous improvement.
Data Model Canvas
Data Model Canvas The Data Product Canvas is a framework for developing data products based organized into 10 blocks within 3 domain areas.
Kanban Practices
Kanban Practices Visualize Visualizing your work provides transparency, identifying the bottlenecks. Create cards for the items you work on. Think of the workflow – statuses that work items go through to make implicit policies explicit, which enable learning how the work works. Limit Work In Process Stop starting, start finishing. Limit the number of items being worked...
Theory Of Constraints
Theory Of Constraints The Theory of constraints says the throughput of any system is limited by at least one constraint slowing it down.
Classes of Service (CoS)
Classes of Service (CoS) Classes of service (CoS) provide a transparent way of categorizing the incoming work items and ensuring they are properly prioritized and governed to lead to meeting customer expectations. They enable managing risk, priorities, and cost of delay. Expedite High-priority items that should be worked on as soon as possible. Expedite class work items have critical...
Seven wastes of software development
Seven wastes of software development Similar to what TPS identified as seven categories of waste in manufacturing, also software development has its own wastes.
Core Kanban Practices
Core Kanban Practices One of the few rules or practices which are the foundation of Kanban are its 3 core practices: Visualize, Limit WIP, and Manage flow.
The prime directive of agile software development
The prime directive of agile software development Acronymat poster: The prime directive of agile software development - Never be blocked, the system must work all the time.
AIDAOR The AIDAOR is a hierarchical model, where a persona moves through a series of cognitive steps before and after making a purchase decision.