# RACI

A responsibility-assignment matrix that marks who is Responsible, Accountable, Consulted, and Informed for defined work.

- Type: framework
- Domain: Leadership & teams
- Level: Foundational
- Last reviewed: 2026-09-21
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/raci/>)

## What it means

RACI maps activities or deliverables against four participation roles. Responsible people perform the work; one Accountable owner answers for the result; Consulted people provide input; and Informed people receive updates. The matrix clarifies collaboration around execution, especially when work crosses organizational boundaries.

## Why it matters

Product initiatives can fail between functions even when each function performs well. RACI exposes missing owners, duplicated effort, and consultation overload before execution begins. It also gives teams a shared starting point for negotiating responsibilities instead of relying on titles or assumptions.

## When to use it

Use RACI for multi-team launches, operational processes, migrations, compliance work, or recurring deliverables where handoffs are unclear. A short matrix is usually more useful than mapping every backlog item.

## How it works

1. List the meaningful activities, deliverables, or process stages that need clear ownership.
2. Name roles or teams across the columns rather than individual names when continuity matters.
3. Assign at least one Responsible party and exactly one Accountable owner to each row.
4. Add Consulted and Informed roles only where their involvement has a practical purpose.
5. Review the matrix together, resolve overloaded roles, and update it when the operating model changes.

## A practical example

For a payments migration, engineering is Responsible for implementation, the platform lead is Accountable for technical readiness, security and support are Consulted, and regional product teams are Informed. Customer communication is a separate row with different ownership rather than being buried in the technical task.

## Where it breaks

RACI describes responsibility, not sequencing, capacity, competence, or decision quality. Labels can create false certainty when the work remains vague. Large matrices become difficult to maintain, and strict interpretation may discourage collaboration beyond assigned boxes.

## Common mistakes

- Giving a row several Accountable owners.
- Mapping trivial tasks until the matrix becomes unreadable.
- Using Consulted as a veto right.
- Publishing the matrix without discussing it with the named groups.

## Visualization

[View the visualization on the website](<https://wiki.soroush.uk/topic/raci/#visualization-raci>)

## Sources

1. [RACI Chart: What It Is and How to Use It](<https://www.atlassian.com/work-management/project-management/raci-chart>) — Atlassian · Framework guide
2. [Responsible, Accountable, Consulted, and Informed Matrix](<https://www.csuci.edu/office-departments/oe/documents/self-serve-raci.pdf>) — California State University Channel Islands · University practice guide

## Related topics

- [DACI](<https://wiki.soroush.uk/topic/daci/>)
- [Decision Rights](<https://wiki.soroush.uk/topic/decision-rights/>)
- [Product Operations](<https://wiki.soroush.uk/topic/product-operations/>)
