RACI matrix after a meeting: roles and a worked example
Turn a discussion of duties into a RACI matrix: who does the work, owns the outcome, gives advice, and receives updates. With an example and review checklist.
Why “we’ll do it” leaves questions open
It is easy to agree that “marketing will prepare it and product will take a look.” Afterwards, marketing may be waiting for inputs while product thinks its role is advisory. A matrix clarifies how each team participates.
RACI assigns roles for a particular task. One person may prepare material in one row and accept the result in another. The letters do not provide authority, source access, or time. Check those before agreeing.
Put the agreements in a table
Start with deliverables
Break “work on the webinar” into an approved agenda, a finished presentation, and a working registration page. A broad row hides handoffs. One row per click makes the matrix hard to use.
Distinguish R and A
R does the work. A owns the result and approval in your model. Assign one A per row so the final decision has an owner. If there are several Rs, specify who integrates the result and how the work is divided.
Limit unnecessary involvement
Use C where advice prevents a poor decision. I receives updates about the result or change. Ask which issue needs a response before assigning C. Leave cells blank when involvement is unnecessary.
Agree using a concrete scenario
Walk the team through one row: who starts, asks for input, receives the output, and what happens if it is refused? If the matrix conflicts with existing authority, resolve the conflict before writing in an assignment.
Preparing a customer webinar
This fictional example uses names, conditions, and outcomes solely to explain the method.
I’ll assemble the content. The expert will check the technical examples, the lead will approve the agenda, and the account managers will get the finished version.
The remark covers preparation of the agenda. Publishing the page and setting up sound need their own rows.
Here the editor is R, the lead A, the expert C, and the account managers I. Another team may assign the roles differently.
| Deliverable | Editor | Lead | Expert | Account managers |
|---|---|---|---|---|
| Webinar agenda | R | A | C | I |
| Technical example | C | I | A/R | I |
| Customer announcement | R | A | C | I |
Template for agreeing on roles
Add the date and project boundaries before the table. Record disputed assignments and handoff conditions after it.
Project and phase: Deliverable | role 1 | role 2 | role 3 | role 4 _________ | R/A/C/I | R/A/C/I | R/A/C/I | R/A/C/I Who combines the work when there are several Rs: Acceptance criterion: When to consult C: How and when to inform I: Disputed authority: Who confirmed the assignments and when:
Check rows and columns
- Every deliverable has someone to do the work.
- Every row has someone accountable for the final decision.
- Where several people do the work, the tasks are divided.
- Consultation and notification are distinct.
A closer look
Can one person be both A and R?
Yes, if they both do the work and own the final outcome in the agreed model. This is common in small teams.
Does every cell need a letter?
No. A blank cell shows that the role need not participate in that task. Fill only the relevant cells.