When a task falls through the cracks, the cause is rarely laziness. It is usually unclear ownership: two people assumed the other had it, and nobody decided. A RACI matrix fixes this by naming, for every task, who does the work, who owns the outcome, who must be consulted, and who just needs to know. This guide shows how to build one that people actually use, not a spreadsheet that dies after the kickoff meeting.

What RACI actually means

RACI stands for four roles you assign per task or decision:

• Responsible – the person doing the work. There can be several.
• Accountable – the single person who owns the result and signs off. Exactly one.
• Consulted – people whose input you need before acting. Two-way conversation.
• Informed – people told after the fact. One-way notice.

The whole model rests on one rule: one Accountable per row. The moment two names share accountability, ownership evaporates and you are back to “I thought you had it.”

Why teams stay confused without it

Confusion is structural, not personal. As a team grows, the number of possible handoffs grows faster than headcount. Roles overlap. A designer, a product manager, and an engineer all touch the same feature, and each reasonably assumes a different person makes the final call. RACI does not add process for its own sake; it makes an implicit assumption explicit before it becomes a missed deadline.

How to build one in under an hour

1. List the real tasks, not the phases

Rows should be verbs someone can be held to: “approve the budget,” “write the test plan,” “publish the release notes.” Avoid vague rows like “planning.” You cannot be accountable for a noun.

2. List the people or roles as columns

Use roles (Product Lead, QA) rather than names when people change often. Use names when the team is small and stable.

3. Fill in one letter per cell

Go row by row. Assign exactly one A. Add R where work happens. Be stingy with C and I – every extra Consulted slows the task down.

4. Check the two failure patterns

• A row with no A: nobody owns it. Assign one.
• A row with two A’s: split the task until each half has a single owner.

A real scenario

A five-person team kept shipping releases with broken links in the announcement email. In the post-incident chat, the writer said marketing owned the email; marketing said the writer owned copy; the PM said QA should have caught it. Three people, three assumptions, zero owners. They built a two-row RACI: “draft email” (writer R, PM A) and “verify links before send” (QA R, PM A). The PM was Accountable for both, so there was one throat to clear. The broken-link problem stopped the next release – not because anyone worked harder, but because the ambiguity was gone.

Additional reading is available at 789WIN.COM.

Common mistakes and how to fix them

• Too many Consulted. If eight people must weigh in, nothing ships. Fix: demote most C’s to I. Ask “does this person’s input change the decision, or do they just want to watch?”
• Accountable and Responsible collapsed into one busy person. That person becomes a bottleneck. Fix: it is fine for one person to be both A and R on a small task, but on large ones, separate them so the owner can delegate.
• Building it once and filing it away. A RACI is only useful when contested. Fix: pull it up the moment someone asks “whose job is this?” If it does not answer the question, edit it on the spot.
• Confusing Accountable with seniority. The most senior person does not have to be A on everything. Fix: assign A to whoever is closest to the outcome and can actually decide.

Action checklist

• List 5 to 15 concrete tasks as verb phrases.
• List the people or roles involved.
• Assign exactly one A per row.
• Mark R wherever hands-on work happens.
• Keep C and I to the minimum that is genuinely needed.
• Scan for rows with zero or two A’s and fix them.
• Store it where the team already works, not in a buried folder.
• Revisit it whenever ownership is questioned.

Conclusion and next step

A RACI matrix does not manage work; it removes the ambiguity that makes work stall. Your next step is small: pick the one recurring task your team keeps dropping, write a single row for it, and assign one Accountable name today. That single row often prevents the next “I thought you had it.”

FAQ

How is RACI different from a job description?

A job description says what your role covers in general. RACI says who owns a specific task on a specific project. The same person can be Accountable on one task and merely Informed on the next.

Can one person be both Responsible and Accountable?

Yes, especially on small tasks. The rule is one Accountable per row, not one letter per person. On larger work, separating the two lets the owner delegate the doing.

What if nobody wants to be Accountable?

That reluctance is the signal. Usually the task is unclear or under-resourced. Clarify the deliverable and the authority that comes with it, then the ownership question becomes answerable.

Is RACI overkill for a small team?

For everyday work, yes. Use it only where handoffs repeatedly fail. A three-row matrix for one messy process beats a fifty-row document nobody reads.

References

• Project Management Institute (PMI), A Guide to the Project Management Body of Knowledge (PMBOK Guide) – covers responsibility assignment matrices including RACI.