From RACI to MOCHA: A Better Framework for Getting Strategic Work Done

Photo courtesy of Pexels/Kindel Media

You've just wrapped a strategic planning session. The energy in the room was high. Priorities are set, goals are clear, and everyone leaves feeling aligned.

Then six weeks pass—and nothing moves.

This is one of the most common frustrations we hear from association leaders: the plan was solid, but implementation stalled. And more often than not, the breakdown isn't about the strategy itself. It's about clarity—specifically, clarity around who is doing what.

The Case for Role Clarity After Strategic Planning

A strategic plan without clear role assignments is really just a wish list. When tasks and initiatives don't have named owners, what tends to happen is predictable: everyone assumes someone else is handling it, work gets duplicated in some areas and neglected in others, and decision-making stalls because no one is sure who has the authority to move things forward.

This is especially true in associations, where work often cuts across departments, involves volunteer leaders, and requires coordination among staff, boards, and committees. The more people involved, the greater the need for a shared understanding of who plays what role.

That's where responsibility assignment frameworks come in—and why we want to introduce you to one we think deserves more attention.

RACI: A Solid Starting Point

If you've spent any time in project management, you've probably encountered the RACI chart. RACI stands for Responsible, Accountable, Consulted, and Informed, and it's been a go-to tool for decades. The basic idea is straightforward: for each task or deliverable, you assign someone who does the work (Responsible), someone who owns the outcome (Accountable), people whose input is needed (Consulted), and people who need to be kept in the loop (Informed).

RACI has real strengths. It forces a conversation about who's involved and in what capacity. It surfaces potential bottlenecks. And it creates a visual map of responsibility that's easy to reference.

But as we've used it across dozens of strategic planning engagements, we've noticed some recurring pain points:

• The Responsible/Accountable distinction gets muddled. In theory, "Responsible" means you do the work, and "Accountable" means you own the outcome. In practice, people blur the two constantly—and in many associations, the same person ends up in both roles anyway, which defeats the purpose of distinguishing them.
• "Informed" is a passive role that doesn't drive action. Telling someone they'll be "kept informed" sounds inclusive, but it doesn't actually give them a meaningful role in the work. It can create a false sense of involvement—or worse, make people feel like they should have influence without actually giving them a way to exercise it.
• RACI doesn't account for management or coaching. Strategic initiatives rarely succeed on implementation alone. Someone needs to be checking in, asking hard questions, removing obstacles, and holding the work accountable over time. RACI doesn't have a dedicated role for the person doing that work.
• It can become a checkbox exercise. In complex organizations, RACI charts can grow unwieldy—long matrices with letters scattered across rows and columns that people fill out once and never revisit. The tool becomes documentation rather than a living guide for how work actually gets done.

Enter MOCHA

MOCHA is a responsibility assignment framework developed by The Management Center, a nonprofit that helps leaders working for social change build and run more effective organizations. It stands for Manager, Owner, Consulted, Helper, and Approver.

Here's how each role works:

• Manager — The person who holds the Owner accountable and keeps the work on track. They ask questions, review progress, share feedback, and step in when things drift. This person may or may not be the Owner's supervisor.
• Owner — The person with overall responsibility for driving the project forward. They coordinate the moving pieces, ensure the work gets done (directly or through Helpers), and involve the right people along the way. There should be one Owner—not two, not a committee.
• Consulted — The people whose input, perspective, or resources are needed to inform the work. They contribute to the thinking but don't own the outcome.
• Helper — The people who carry out portions of the work under the Owner's coordination. In some cases, a Helper may own a significant workstream with its own mini-MOCHA—what The Management Center calls a "cascading MOCHA." The Owner remains the overall integrator.
• Approver — The person or body who signs off on key decisions before they're final. In an association context, this might be the executive director, a board chair, or a committee with decision-making authority.

Why We Recommend MOCHA Over RACI

We've started using MOCHA with our clients—particularly in strategic planning contexts—for a few key reasons:

• It separates management from ownership. This is the most significant difference. RACI doesn't have a role for the person who coaches the work forward — checking in, asking hard questions, and course-correcting when things drift. That responsibility either falls to whoever is "Accountable" or doesn't live anywhere at all. MOCHA explicitly names a Manager whose job is to do exactly that. In our experience, this single distinction dramatically improves follow-through. Strategic priorities are more likely to advance when someone is actively shepherding the work, not just waiting for a status update.
• It replaces "Informed" with "Helper." Instead of a passive category of people who receive updates, MOCHA gives contributors a defined, active role. Helpers know what they're responsible for and who they report to within the context of the project. This is more honest about how work actually happens in teams—and it reduces the hidden labor that often goes unacknowledged in collaborative environments.
• It emphasizes singular ownership. MOCHA insists on one Owner per project or initiative. This sounds simple, but it's transformative. When two people "co-own" something, what often happens is that neither fully owns it. One Owner, supported by a Manager and Helpers, creates a clear line of accountability.
• It's built for collaborative environments. The Management Center designed MOCHA specifically for mission-driven organizations where collaboration is valued and stakeholder input matters. Associations fit this description perfectly. MOCHA doesn't discourage collaboration—it structures it so that broad involvement doesn't come at the cost of clear accountability.
• It brings hidden labor into the open. In associations, informal roles have a way of calcifying. The same staff member ends up coordinating logistics for every initiative. The same volunteer gets pulled into projects without being formally asked—or formally recognized. Over time, these patterns tend to follow predictable lines of positional power, tenure, and identity. MOCHA doesn't solve those dynamics on its own, but it forces a more honest conversation about who is actually doing what. When every contributor has a named role—not just the Owner and Approver, but the Helpers and Consulteds too—workload distribution becomes visible, credit becomes easier to give, and assumptions about who "naturally" takes on certain work are harder to leave unexamined.
• It scales with complexity. For larger initiatives, MOCHA supports a cascading structure: the overall project has one Owner, but individual workstreams can have their own sub-MOCHAs, with Helpers "owning" discrete pieces of the work. This makes it adaptable for everything from a single event to a multi-year strategic plan.

What Happens When You Don't Use a Framework Like This

We've seen it enough times to name the pattern. Without clear role assignments, strategic plans tend to experience:

• Diffusion of responsibility — When everyone is responsible, no one is. Tasks fall through the cracks because each person assumes someone else is handling them.
• Decision gridlock — Without a named Approver, decisions get stuck in endless loops of input-gathering and consensus-seeking. Good ideas die in committee.
• Burnout among the willing — The most proactive staff members absorb more than their share of the work because no one else has been explicitly assigned. Over time, this leads to resentment and exhaustion.
• Eroded trust — When people can't count on the plan being implemented, they stop investing in the planning process. Future strategic conversations feel hollow because the last plan never went anywhere.
• Invisible labor — Contributions go unrecognized because they were never formally assigned. People do essential work that no one tracks, acknowledges, or accounts for in workload planning.

These aren't hypothetical risks. They're the lived experience of many associations we work with—and they're almost always preventable with upfront clarity about roles.

Putting MOCHA Into Practice

If you're wrapping up a strategic planning process (or revisiting a plan that's stalled), here's how to put MOCHA to work:

• Start with your highest-priority initiatives. You don't need to MOCHA everything at once. Identify the three to five strategic priorities that matter most and assign roles for each.
• Have the conversation out loud. Don't just fill in a chart and circulate it. Talk through who's playing each role and why. Make sure the Owner understands what ownership means, the Manager knows they're expected to actively coach (not just oversee from a distance), and Helpers are clear on what they're being asked to do.
• Revisit regularly. MOCHA isn't a one-time exercise. Check in on role assignments at quarterly reviews or whenever a project transitions from one phase to the next. Roles may need to shift as the work evolves.
• Name the Approver early. One of the fastest ways to stall a project is to leave the approval path ambiguous. Decide upfront who has sign-off authority, and make sure the Owner knows how and when to engage them.
• Don't forget about communication. If you're coming from RACI, you'll notice there's no "Informed" role in MOCHA. That's by design — but it doesn't mean communication stops mattering. Instead of assigning a passive category of people who receive updates, MOCHA treats communication as a task the Owner is responsible for managing. Who needs to know what, and when? In an association context, that might mean the Owner builds member-facing updates into the project plan and assigns a Helper to draft them. The communication still happens — it just lives inside the work rather than as a label on a chart.

The Bottom Line

Strategic planning is only as valuable as the implementation that follows. And implementation depends on people knowing—really knowing—who is driving the work, who is supporting it, who needs to be consulted, who is helping implement, and who makes the final call.

RACI got us partway there. MOCHA takes us further.

If your organization is ready to move from planning to doing, we'd love to help you build the clarity and accountability structures that make it possible. Reach out to Event Garde to learn how we support associations through strategic planning and focused implementation.