Who Owns This: RACI Lite How-to
RACI lite succeeds when it creates one Accountable human for the outcome, not a prettier shared inbox. This play bans dual-A as a default exit. If two leaders insist on co-owning, the facilitator forces a split of the outcome into two named results, or escalates the conflict instead of papering it with a matrix.
This is a fast ownership-clarity play for managers, cross-functional leads, and directors. It is not a project-management certification, and it does not claim RACI is universally required or that RACI beats RASCI or DACI. Do not invent productivity stats from “implementing RACI.” Do not use the session to assign blame for past failures.
Play card
| Field | Detail |
|---|---|
| Time box | 30-45 minutes |
| Players | Workstream lead/facilitator + one representative per function (keep the room small) |
| Goal | One-page RACI lite + decision-rights notes + revisit date |
| Done looks like | Exactly one Accountable per outcome; Consulted lists trimmed; rollout plan for people not in the room |
Hubs: How Departments Work Together, Leadership Team Meeting Design, Sales to CS handoff, delegation without dumping, New Manager, Director / VP.
When to use
- Ambiguous ownership: “we all kind of own this.”
- Recurring drops on a multi-team deliverable.
- Handoffs, launches, or LT agenda items that stall on who decides.
- New cross-functional workstream before kickoff.
When not to use
- Performance issue with one person (manage performance; do not matrix it).
- Pure strategy disagreement (decide strategy first).
- HR or employee-relations matters (use HR paths, not RACI).
- Enterprise operating-model redesign that needs formal governance forums.
Prep
- Named outcome in one sentence (not a vague theme).
- List of decisions and tasks (aim for 5-12 rows, not 80).
- Known pain points: drops, dual approvals, surprise stakeholders.
- Invite list: functions that touch the work; leave spectators out.
Plain-language definitions
| Letter | Meaning |
|---|---|
| R – Responsible | Does the work. Can be more than one person if tasks split cleanly. |
| A – Accountable | One human who owns the outcome and the decision. Exactly one per row/outcome. |
| C – Consulted | Gives input before the decision; two-way. Keep short. |
| I – Informed | Told after; one-way. Not a meeting seat by default. |
Timed steps
| Clock | Move |
|---|---|
| 0-5 min | Open: one Accountable rule; no blame archaeology. |
| 5-15 min | List outcomes/tasks; reject boiling-the-ocean row sprawl. |
| 15-30 min | Fill A first, then R, then trim C, then I. |
| 30-40 min | Decision-rights notes for contested rows; ban dual-A. |
| 40-45 min | Revisit date + rollout message for people not present. |
Facilitator scripts
Force single A: “Who is the one human that leadership will call if this fails? That person is A. If you both raise hands, we split the outcome into two named results or escalate.”
Dual-A pushback: “Co-own is how this stayed stuck. Either split the outcome or we take the conflict to [LT owner / sponsor], not into a matrix with two A’s.”
Over-Consulted: “If everyone is C, nobody is fast. Who must be consulted because a miss creates real risk? Everyone else becomes I.”
RACI as blame map: “We are designing forward. Past drops inform risks; they are not today’s agenda.”
Output template
RACI LITE - [Workstream] - [Date]
Outcome (1 sentence):
Facilitator:
Revisit date:
| Decision / task | R | A | C | I |
| - | - | - | - | - |
| | | | | |
Decision-rights notes (exceptions, escalation path):
Rollout: who was not in the room and how/when they hear this:
Hypothetical example (sample)
Workstream (sample): “Launch Partner Portal phase 1 by Nov 15.”
| Decision / task | R | A | C | I |
|---|---|---|---|---|
| Scope freeze | Product lead | VP Product | Sales, CS | Eng all-hands |
| Integration build | Eng lead | Eng director | Product, Security | CS |
| Customer comms | CS lead | CS director | Product, Sales | Support |
| Go / no-go | PMO | VP Product | Eng, CS, Sales | LT |
(All roles fictional and for teaching.)
Rollout without surprising people
Send the one-pager within 24 hours. Name what changed for each function. Invite corrections on factual misses (wrong system owner), not re-litigation of the single-A rule. Put the matrix where the work lives (project brief, LT pre-read), not in an orphaned slide.
Signals the play worked
Fewer dropped balls on named tasks; faster decisions because A is known; cleaner escalations (people know who decides). These are qualitative process signals. Do not invent company-wide productivity percentages.
Pairing with other plays
- LT agendas that stall: Leadership Team Meeting Design.
- Revenue transfer ownership: Sales to CS handoff.
- Individual managers learning to hand off work: delegation without dumping and Delegation play.
Watch-outs
- Everyone Consulted.
- Dual Accountable as a peace treaty.
- Living spreadsheet nobody opens.
- Using RACI to blame individuals in the room.
- Claiming one matrix style is best for every company.
- Replacing formal operating models in complex enterprises with a one-page lite sheet alone.
Next links
Cross-functional hub: How Departments Work Together. Stage hubs: New Manager, Director / VP. Keep ownership language consistent across LT, handoffs, and project kickoffs.