Responsibility assignment matrix
A responsibility assignment matrix (RAM), also known as RACI matrix (//) or linear responsibility chart (LRC), describes the participation by various roles in completing tasks or deliverables for a project or business process. RACI is an acronym derived from the four key responsibilities most typically used: responsible, accountable, consulted, and informed. It is used for clarifying and defining roles and responsibilities in cross-functional or departmental projects and processes. There are a number of alternatives to the RACI model.
Key responsibility roles in RACI model
There is a distinction between a role and individually identified people: a role is a descriptor of an associated set of tasks; may be performed by many people; and one person can perform many roles. For example, an organization may have ten people who can perform the role of project manager, although traditionally each project only has one project manager at any one time; and a person who is able to perform the role of project manager may also be able to perform the role of business analyst and tester.
- R = Responsible (also recommender)
- Those who do the work to complete the task. There is at least one role with a participation type of responsible, although others can be delegated to assist in the work required (see also RASCI below for separately identifying those who participate in a supporting role).
- A = Accountable (also approver or final approving authority)
- The one ultimately answerable for the correct and thorough completion of the deliverable or task, the one who ensures the prerequisites of the task are met and who delegates the work to those responsible. In other words, an accountable must sign off (approve) work that responsible provides. There must be only one accountable specified for each task or deliverable.
- C = Consulted (sometimes consultant or counsel)
- Those whose opinions are sought, typically subject-matter experts; and with whom there is two-way communication.
- I = Informed (also informee)
- Those who are kept up-to-date on progress, often only on completion of the task or deliverable; and with whom there is just one-way communication.
Very often the role that is accountable for a task or deliverable may also be responsible for completing it (indicated on the matrix by the task or deliverable having a role accountable for it, but no role responsible for its completion, i.e. it is implied). Outside of this exception, it is generally recommended that each role in the project or process for each task receive, at most, just one of the participation types. Where more than one participation type is shown, this generally implies that participation has not yet been fully resolved, which can impede the value of this technique in clarifying the participation of each role on each task.
Assigning people to facilities
The matrix is typically created with a vertical axis (left-hand column) of tasks (from a work breakdown structure) or deliverables (from a product breakdown structure), and a horizontal axis (top row) of roles (from an organizational chart).
|Code||Name||Project sponsor||Business analyst||Project manager||Technical architect||Applications development|
|Stage A||Manage sales|
|Stage B||Assess job|
|Stage C||Initiate project|
|- C04||Security governance (draft)||C||C||A||I||I|
|- C10||Functional requirements||A||R||I||C||I|
|- C11||Business acceptance criteria||A||R||I||C||I|
|Stage D||Design solution|
Another example from the maintenance and reliability community
|Tasks||Maintenance supervisors||Maintenance analyst||Maintenance planner||Maintenance technician||Maintenance support||Rel specialist||CMMS project engineer|
|Inputting failure data||A||C||I||R||C||C|
|Work order completion||R||C||C||C||A||I||I|
|Work order closeout||C||R||C||I||I||A|
|QA of failure data input||C||R||I||C||I||C||A|
|Analyze failure reports||C||C||I||C||A||R||I|
|Maintenance strategy adjustments||C||I||I||C||A||R||R|
|Implementing new strategies||R||I||R||C||A||I||I|
There are a number of alternatives to the RACI participation types:
- This is an early version of a responsibility assignment matrix, with the roles defined as:
- Review required
- Input required
- Sign-off required
- This is a version very useful to organizations where the output of activities under the accountability of a single person/function can be reviewed and vetoed by multiple stakeholders, due to the collaborative nature of the culture.
- The person/function carrying out the activity.
- The person/function ultimately answerable for the correct and thorough completion of the deliverable or task, and often the one who delegates the work to the performer.
- The person/function reviewing the result of the activity. They have a right of veto; their advice is binding.
- The person/function consulted to give advice based upon recognized expertise. The advice is non-binding.
- The person/function who must be informed of the result of the activity.
RASCI or RASIC
- This is an expanded version of the standard RACI, less frequently known as RASCI, breaking the responsible participation into:
- Those responsible for the task, who ensure that it is done as per the approver
- Resources allocated to responsible. Unlike consulted, who may provide input to the task, support helps complete the task.
- This is an alternative version of the standard RACI, foregoing the consulted participation and replacing it with:
- Resources which play a supporting role in implementation.
- This is an expanded version of the standard RACI, with an additional participation type:
- Quality review
- Those who check whether the product meets the quality requirements.
- This is an expanded version of the standard RACI, with two additional participation types:
- Those who approve the verify decision and authorize the product hand-off. It seems to make sense that the signatory should be the party being accountable for its success.
- This is an expanded version, of the standard RACI, also known as RACIO with one additional participation type.
- Out of the loop (or omitted)
- Designating individuals or groups who are specifically not part of the task. Specifying that a resource does not participate can be as beneficial to a task's completion as specifying those who do participate.
- Another version that has been used to centralize decision making, and clarify who can re-open discussions.
- A single driver of overall project like the person steering a car.
- One or more approvers who make most project decisions, and are responsible if it fails.
- Are the worker-bees who are responsible for deliverables; and with whom there is two-way communication.
- Those who are impacted by the project and are provided status and informed of decisions; and with whom there is one-way communication.
- Another tool used to clarify decision roles and thereby improve decision making, is RAPID, which was created by and is a registered trademark of Bain & Company.
- The recommend role typically involves 80 percent of the work in a decision. The recommender gathers relevant input and proposes a course of action—sometimes alternative courses, complete with pros and cons so that the decision maker's choices are as clear, simple and timely as possible.
- The agree role represents a formal approval of a recommendation. The 'A' and the 'R' should work together to come to a mutually satisfactory proposal to bring forward to the decider. But not all decisions will need an agree role, as this is typically reserved for those situations where some form of regulatory or compliance sign-off is required.
- The perform role defines who is accountable for executing or implementing the decision once it is made. Best-practice companies typically define P's and gather input from them early in the process.
- The input role provides relevant information and facts so that the recommender and decider can assess all the relevant facts to make the right decision. However, the 'I' role is strictly advisory. Recommenders should consider all input, but they don't have to reflect every point of view in the final recommendation.
- The decide role is for the single person who ultimately is accountable for making the final decision, committing the group to action and ensuring the decision gets implemented.
- Another tool used in organization design or roles analysis.
- Identify who is in charge of making sure the work is done.
- Identify who has final decision power on the work.
- Identify who actually does the work.
- Identify who is involved to provide support to the work.
- Identify who is informed that the work has been done (or will be started)
- A variant of RASCI developed by three Whitehall theorists (Kane, Jackson, Gilbert). This scheme is adapted for use in matrix management environments, and differs only from RASCI in having an additional role of Driver and a narrower definition of Support:
- An individual or party that assists those who are responsible for delivering a task by both producing supporting collateral and setting timescales for delivery in line with the overarching aim of the individual or party who is accountable for the overall accomplishment of the objective. The distinction between driver and support lies in that the former reinforces and clarifies the parameters of the task on behalf of those who are accountable, while the latter refers to those who help those who are responsible in reaching a given goal.
- A version developed at U Tokyo and MIT for model-based project management. The PDQA set of roles corresponds to demand for capabilities of teams. Roles include those for work on scope, handling of dependencies as coordination, and exception handling through error detection and decisions across a project organization. PDQA is used in agent-based modeling to simulate the supply of these capabilities by teams in projects.
- Provides skill-based effort within capacity to complete scope and also manages dependencies through coordination.
- Handles any decision, including scope acceptable and exception handling decisions leading to rework. (Does not generation nominal scope).
- Reviews scope as it progresses to detect poor quality and escalates to decision-maker as so. (Does not general nominal scope).
- Provides skill-based effort with the capacity to complete scope, in assistance to the primary. (Does not manage dependencies through coordination).
- A minimal set of decision-making categories used in organisation design or roles analysis.
- Decision maker
- Individuals who make the decision and is accountable for its impact on the business.
- Individuals accountable for providing guidance based on functional expertise and experience, highlighting issues and raising alternatives to support the Decision Maker.
- Impacted stakeholders are notified after the decision has been made and who will need to support the execution of the decision.
To be used when working on governance, risk, compliance (GRC) and outsourcing matters:
- Third parties contracted to execute activities in accordance with a service level agreement
- Key GRC roles, such as risk owner, policy owner - where accountability is devolved, but a role is needed to oversee whether accountabilities all fit together
There are also a number of variations to the meaning of RACI participation types:
RACI (alternative scheme)
- There is an alternative coding, less widely published but used by some practitioners and process mapping software, which modifies the application of the R and A codes of the original scheme. The overall methodology remains the same but this alternative avoids potential confusion of the terms accountable and responsible, which may be understood by management professionals but not always so clearly differentiated by others:
- Those responsible for the performance of the task. There should be exactly one person with this assignment for each task.
- Those who assist in the completion of the task
- Those whose opinions are sought; and with whom there is two-way communication.
- Those who are kept up-to-date on progress; and with whom there is one-way communication.
- This alternative is focused only on documenting who has the authority to make which decisions. This can work across all sized workgroups.
- Authorized to approve an answer to the decision.
- Responsible to recommend an answer to the decision.
- Those whose opinions are sought, and with whom there is two-way communication.
- Those who are informed after the decision is made, and with whom there is one-way communication.
- "188.8.131.52 Organization Charts and Position Descriptions". A Guide to the Project Management Body of Knowledge (PMBOK Guide) (5th ed.). Project Management Institute. 2013. p. 262. ISBN 978-1-935589-67-9.
- Jacka, Mike; Keller, Paulette (2009). Business Process Mapping: Improving Customer Satisfaction. John Wiley and Sons. p. 257. ISBN 978-0-470-44458-0.
- Cleland, David; Ireland, Lewis (2006). Project management: strategic design and implementation. McGraw-Hill Professional. p. 234. ISBN 0-07-147160-X.
- Blokdijk, Gerard (2008). The Service Level Agreement SLA Guide - SLA Book, Templates for Service Level Management and Service Level Agreement Forms. Fast and Easy Way to Write Your SLA. Lulu. p. 81. ISBN 978-1-921523-62-5.
- Brennan, Kevin (2009). A Guide to the Business Analysis Body of Knowledge (BABOK Guide). International Institute of Business Analysis. p. 29. ISBN 978-0-9811292-1-1.
- Smith Michael, Erwin James: Role & Responsibility Charting (RACI), Project Management Forum, 2005, p. 5[dead link]
- Margaria Tiziana: Leveraging Applications of Formal Methods, Verification, and Validation: 4th International Symposium on Leveraging Applications Proceedings], Part 1, Springer, 2010, p. 492
- A Guide to the Project Management Body of Knowledge. Project Management Institute. 2000. p. 111. ISBN 1-880410-22-2.
- Hightower, Rose (2008). Internal controls policies and procedures. John Wiley & Sons. p. 83. ISBN 978-0-470-28717-0.
- Baker, Dean (2009). Multi-Company Project Management: Maximizing Business Results Through Strategic Collaboration. J Ross. p. 58. ISBN 978-1-60427-035-8.
- Mikes, Joe; Denton, Tara (2011). Training Speeds Continuous Improvement. Life Cycle Engineering.
- Bolman, Lee (2008). Reframing organizations: artistry, choice, and leadership. John Wiley & Sons. p. 112. ISBN 978-0-7879-8799-2.
- Dickstein, Dennis (2008). No Excuses: A Business Process Approach to Managing Operational Risk. John Wiley & Sons. ISBN 978-0-470-48110-3.
- Kendrick, Tom (2006). Results without authority: controlling a project when the team doesn't report to you. AMACOM Books, division of the American Management Association. p. 106. ISBN 0-8144-7343-1.
- Moser, B. R.; Wood, R. T. (2015). "Design of Complex Programs as Sociotechnical Systems". Concurrent Engineering in the 21st Century. Springer: 197–220.