PM Through ConsensusA Project Management Course
Subsection 4.1

Roles with MOCHA, DARCI, or RACI

~7 min

Reading

MOCHA, DARCI, RACI: three role-assignment tools. Pick one and use it. Roles named at the start prevent half the conflicts later.

In project management, roles are clearly defined at the beginning of a project. The three most common tools are MOCHA (Manager, Owner, Consulted, Helper, Approver), DARCI (Decision-maker, Accountable, Responsible, Consulted, Informed), and RACI (Responsible, Accountable, Consulted, Informed). They overlap heavily; the differences are mostly vocabulary.

The Management Center popularized MOCHA in nonprofit settings. The big move in MOCHA is naming a single Owner — one person whose responsibility it is to ensure the work happens. Not two co-owners. Not "the team". One human, by name. The Helper(s) do the work. The Owner does not necessarily do the work; the Owner makes sure the work happens.

A real MOCHA for a community event might look like: Manager (ED), Owner (the event lead), Consulted (program director, comms director), Helper (three volunteers by name), Approver (board chair, if the budget requires it). Put it at the top of the project scope. Update it as people's availability changes.

Whatever framework you pick, the rule is the same: every task has exactly one Accountable person. If two people are accountable, neither is. If nobody is, the task does not happen. The framework is just a way to make this discipline visible.

MOCHA · DARCI · RACI · pick one, name humans in each role TASK MOCHA Manager · Owner · Consulted · Helper · Approver DARCI Driver · Approver · Responsible · Consulted · Informed RACI Responsible · Accountable · Consulted · Informed Survey design Module 7 prep O: Naomi M: Rosa · A: ED R: Naomi D: Rosa · A: ED R: Naomi A: Rosa Member outreach calls + texts O: Field team M: Marco · H: volunteers R: Field team D: Marco R: Field team A: Marco Data analysis after the close O: Sam C: data fellow R: Sam C: data fellow R: Sam A: Rosa Final report to leadership O: Rosa A: ED · C: board chair R: Rosa A: ED R: Rosa A: ED All three frameworks force the same discipline: one Owner per task, no anonymous "we", no ambiguous "the team will handle it".
MOCHA on one real project: Spring multilingual phone bank Goal: 4,000 member conversations in English, Spanish, Vietnamese over six weeks The project six weeks · three languages · one report M · Manager Rosa Campaigns Director sets the goal, unblocks the owner, does not decide for them Prevents: "who do I escalate to when stuck?" O · Owner Marco Lead Organizer one human · by name owns the plan, the calendar, the number Prevents: "the team will handle it" C · Consulted Linh · Sofia Language leads (VN, ES) asked before the script goes live; not voting on it, but heard on it Prevents: "nobody asked the people doing the calls" H · Helper Volunteer pod ~24 callers · 3 shift leads named in shift calendar, not in a "volunteers" group chat Prevents: unnamed labor, missed credit at the close A · Approver Janelle Executive Director one final yes on the script and the close-out report Prevents: a surprise board veto three days before launch Every name above is a real human who can be paged on Friday afternoon. That is the only test that matters.

Learner action

For your project, build a MOCHA, DARCI, or RACI table. Name every role with a real human's name (not a team or title alone). Share it with that named human and confirm they accept the role.

Action: Complete the learner action above, then slide to continue.