MOCHA: Splitting the Coaching Manager from the Owner

Summary

MOCHA assigns five roles: a Manager who coaches and unblocks, a single Owner who drives the work, Consulted advisors, Helpers who implement parts of it, and an Approver who signs off. Its signature move is splitting RACI’s Accountable into Manager and Owner, so the senior person supports rather than seizes the work. Created by The Management Center for mission-driven organizations, it carries an explicit equity purpose: making every contribution visible interrupts the pattern where credit and ownership drift along lines of race and gender. Choose it when developing owners matters as much as delivery, especially in non-profits and cross-functional teams of three or more people. For pure decisions, use DACI or RAPID instead.

The letters

MOCHA reworks the responsibility matrix around a clear separation between oversight and ownership.

The signature distinction is between Manager and Owner. In RACI these are effectively merged into Accountable. MOCHA insists they are different jobs: the Owner drives the work, and the Manager coaches the Owner and removes obstacles without seizing the wheel.

Origin and history

MOCHA was created by The Management Center, a United States non-profit that develops management practices for social-change, education-equity, and public-sector organizations. Unlike most of the family, it therefore has a clear organization of record and a well-maintained body of guidance, including role definitions, an FAQ resource, and a sample email for introducing the vocabulary to a team.

It was built explicitly as an improvement on RACI for mission-driven teams, and it carries a distinctive social purpose. The Management Center notes that in many organizations, who is seen as “in charge”, who becomes an invisible helper, and who actually drives the work often mirror race and gender disparities. MOCHA is designed, in part, to interrupt that pattern by making everyone’s contribution visible and giving each person real ownership over something. That equity dimension is not incidental; it is part of why the matrix exists and part of what distinguishes it from the more mechanical members of the family.

What problem it solves

MOCHA solves two problems at once. The first is the manager-owner confusion that RACI’s single Accountable role creates. When one person is both the coach and the driver, projects tend toward either micromanagement (the senior person does the work) or abdication (the senior person owns it in name but no one drives it). By separating Manager from Owner, MOCHA empowers the Owner to genuinely own the work while giving the Manager a clear, supportive job: coach, unblock, and hold to account, but do not take over.

The second problem is invisible work. By naming Helper and Consulted as distinct, credited roles, MOCHA makes visible the contributions that RACI tends to fold silently into someone else’s Responsible cell. Visible contribution is the basis of fair recognition, which is why the matrix doubles as an equity tool: work that is recorded is work that can be acknowledged.

When to choose it, and when not

Choose MOCHA when you want to separate coaching from ownership, when developing owners is a goal in itself, and when making contributions visible matters to you. It is a natural fit for non-profits and mission-driven organizations, for cross-functional delivery that spans handoffs and phases, and for teams with an active commitment to equity and inclusion. It is also well suited to development-minded management, because the Manager-as-coach role is explicitly about setting owners up to succeed rather than doing the work for them.

Do not use it for a two-person task where a quick conversation about who owns what is enough; The Management Center itself says MOCHA is a tool for projects with three or more people. And if the central question is a decision rather than the delivery of a project, a decision-rights framework such as DACI or RAPID will serve you better.

Common pitfalls

• More than one Owner. The cardinal error. Two owners diffuse the overall responsibility MOCHA exists to concentrate. Use a cascading MOCHA instead, where a Helper owns a discrete stream.
• Manager doing instead of coaching. If the Manager keeps grabbing the work, the Owner never truly owns it and the matrix’s development benefit is lost.
• Approver sprawl. A long list of approvers stalls the work. Ask who genuinely needs to sign off; often several should be Consulted instead.
• Enlisting people without consent. The Management Center is firm that Managers should not draft Owners, and Owners should not draft Helpers, without a conversation. Roles assigned without buy-in tend not to stick.
• Skipping the clarify-roles step. Assuming people know their role defeats the purpose; the value is in the explicit conversation.

Worked example

A non-profit launching a new scholarship program.

Reading the “Design the program” row: the Program Lead is the single Owner driving the design (O), the Program Director is the Manager who coaches and removes blockers but does not take over (M), Finance and the Alumni Volunteer are Consulted (C), and the Executive Director is the Approver (A). In the “Run outreach” row, the Alumni Volunteer is a Helper whose stream is large enough to warrant its own nested MOCHA, which is the cascading pattern The Management Center recommends for acknowledging helpers who really own a chunk of work.

Where it sits in the family

MOCHA is a task-centric matrix like RACI, but it is the member most consciously redesigned around people development and equity rather than pure role mechanics. Its Owner role plays the part of RACI’s Accountable, its Helper role resembles RASCI’s Support, and its Consulted and Approver roles map onto familiar territory. What has no clean equivalent elsewhere is the coaching-Manager role. If RACI is the neutral engineering tool of the family, MOCHA is its leadership-and-culture expression: the same grid, reorganized to develop owners and make contribution visible.

Sources

Web sources

• Assigning Responsibilities with MOCHA, The Management Center: https://www.managementcenter.org/resources/assigning-responsibilities/
• MOCHA Frequently Asked Questions, The Management Center: https://www.managementcenter.org/resources/frequently-asked-questions-about-mocha/
• What is MOCHA in project management, Tempo (created by The Management Center; separates management from ownership): https://www.tempo.io/blog/mocha-project-management
• How and why to use the MOCHA method, monday.com: https://monday.com/blog/project-management/what-is-the-mocha-project-management-method-how-to-use-it/

Academic sources

MOCHA has an organization of record but no peer-reviewed literature of its own. Its primary published source is a practitioner book, and its theoretical footing is the delegation literature.

• Green, J. and Hauser, S. (2012) Managing to Change the World: The Nonprofit Manager’s Guide to Getting Results. 2nd edn. San Francisco, CA: Jossey-Bass. The Management Center’s book, the closest thing to a founding text for MOCHA’s approach to delegation.
• Jensen, M.C. and Meckling, W.H. (1976) ‘Theory of the firm: managerial behavior, agency costs and ownership structure’, Journal of Financial Economics, 3(4), pp. 305-360. The principal-agent frame underlying the Manager-Owner split.