Clear responsibility and one accountable decision owner.
All notes

Project management

RACI matrix: assign roles for a product launch

How to build a RACI matrix that settles who does what, the rule of one accountable person per task, how to scan rows and columns for bottlenecks and gaps, when to use RASCI, DACI or RAPID instead, and how to run the workshop.

A new-product launch needs supplier approval, artwork and a release decision. Before assigning dates, the project lead needs to agree who will do each task and who can accept its result.

A RACI matrix assigns responsibility for tasks or decisions. It records who does the work, who owns the outcome, whose input is needed and who must be told. Building it requires those people to agree the assignments.

The four letters

The responsible person does the work; the accountable person answers for it. When the same person does both, write A/R. Count that assignment as both responsible and accountable when checking the row. An A on its own does not say who performs the work.

The rule that makes RACI work, and the one the PMBOK Guide stresses: one A per task. If two managers both expect to approve the same task, agree the final decision owner and any required consultation before recording the assignment.

The example: launching a new product

A consumer goods company is launching a new product variant. The project lead maps the main tasks against six roles:

Task Sponsor Project lead Marketing Supply chain Quality Finance
Approve the business case A C C C R
Define the product spec I A R C C
Plan materials and capacity A I R C C
Approve packaging artwork A R C R
Run the production trial A I R R
Release for sale A R I C C I

Read it by row

Each row is a task. Scan them for these patterns:

Pattern What it means What to do
No A or A/R Nobody owns the outcome Assign one accountable owner
More than one A or A/R Unclear decision rights Agree one accountable owner; review the other person's role
No R or A/R Nobody is assigned to do the work Assign the work
Lots of Cs Slow decisions, too many voices Keep C for people whose input changes the result; move the rest to I
Only I's apart from A and R Possibly fine, or a stakeholder is missing Check who'd be upset to be left out

Read it by column

Read each role's column to check the number and type of assignments:

Pattern What it means What to do
Many A's in one column Several decisions depend on one person Check approval deadlines and actual turnaround before reassigning work
Many R's in one column Overload; check capacity against the plan Rebalance, or accept the risk explicitly
No R, A or A/R at all The role may not need to be on the project Keep them informed, or take them off the core team
Only C's Useful expertise, or an unnecessary approval step Check that every C really changes decisions

The project lead has four A assignments. Check whether those approvals fall at the same time, whether decisions are waiting, and who else has the authority to approve them. Keep the assignments if the lead can meet the deadlines.

Variants, and when to use them

Model Letters Use it when
RACI Responsible, Accountable, Consulted, Informed The default for projects and processes
RASCI Adds Support: helps the R with the work Many people contribute to one deliverable
DACI Driver, Approver, Contributors, Informed Organising a single decision, popular in software product teams
RAPID Recommend, Agree, Perform, Input, Decide Big, contested decisions across functions

Bain & Company's RAPID separates the person who recommends from the person who decides. It also defines agreement rights for functions such as Legal or Quality. Use it when the team needs to settle the decision process as well as who performs the resulting work.

How to build it: a one-hour workshop

  1. Before the meeting, list 10 to 20 tasks or decisions at the level where confusion actually happens. Not "deliver the project", not "send an email".
  2. Invite one person per role, with enough authority to agree on behalf of their team.
  3. Fill in the A's first. It's where the disagreements are. Settle them one by one.
  4. Then the R's, then C and I. These go quickly once the A's are clear.
  5. Check rows and columns with the two tables above.
  6. Publish it where the work happens: in the project space, next to the plan. Not in an attachment.
  7. Revisit it at each phase gate, and whenever someone new joins or a task falls through the cracks.

Mistakes to avoid

  • Too granular. A 200-row matrix can be difficult to maintain. Start with tasks that cross team boundaries and keep the detailed assignments with the teams.
  • Names instead of roles, or roles instead of names. Use roles in the matrix, and keep a separate list of who holds each role right now.
  • Consulting everyone. Every C adds time. Consultation is a cost, spend it where it improves the result.
  • Treating it as done. The matrix describes a moment. Projects change phase, people move, and the matrix should follow.

Before using the launch plan, ask each responsible and accountable person to confirm their assignment. Resolve competing approval claims, then keep the named role holders and matrix beside the current schedule.

Roles are half of it; people adopting the change is the other halfKotter and ADKAR help make sure the change sticks once the roles are clear.

Sources

The launch and its roles are illustrative.

NextSafety stock and reorder point: formulas and example

Discuss an operations problem

I work with operations and transformation teams on operational excellence, digital transformation programs, supply chains and industrial AI. Send me the problem you’re working on and the result you need.

Abolfazl ShirkavandImage preview unavailable