Skip to content

RACI, RASIC, or RAPID – throw out the complexity

RACI is arguably the most popular tool for responsibility planning. RAPID puts a decision-making spin on this framework. But do you need either? This article contests the usefulness of these models, and explains how to remove the complexity and introduce a more effective approach that centres around approval and delivery.

Published by Rupert Morrison

Organizational design responsibility matrix

[This article was updated on July 17, 2019]

As organizations grow, understanding what work needs to be done and how to divide that work among the workforce becomes more and more complex. By linking the organizational system to time allocation and accountability, you can begin to see which roles are connected to which activities to understand where the gaps are.

Assigning activities to roles is usually done using an ‘accountability matrix’. Although RACI is the most popular matrix for this task, I would argue that it doesn’t provide enough clarity around roles and responsibility. Far from simplifying the process, RACI makes it more complex than it needs to be.

RACI framework doesn’t give enough clarity on roles and responsibilities

The first time I came across RACI was during an organisational design project for an automotive company in South Africa in the 1990s. As part of the prep, I reviewed our methodology and discovered the accountability framework we would use to determine who’s Accountable (A) for an activity (or decision), who needs to be Consulted (C) or Informed (I), and who is ultimately Responsible (R) for that activity.

But as I contemplated its usefulness, a series of questions came to mind:

  1. What is the difference between being Accountable and Responsible?
  2. How important is it to define who needs to be Consulted and Informed?
  3. What about the people who need to be involved in actually doing the work?
  4. And what about those who have a veto on a decision, or think they should have?
  5. The point of the ‘A’ and the ‘R’ is that there should only be one person involved, a single point of accountability. But what happens if there are two (or more) decisions makers, i.e. two people that have a veto?

What didn’t occur to me until much later, having used the framework numerous times since, is once you’ve set it up, how do you sustain it? How do you communicate it? How do you make it live? Too often, we define things like RACI as a one-off and people make a big fuss over whether they’re consulted before a decision is made or informed after it’s been made.

Throw out the complexity – make it RAD

We take a different view of RACI and advise clients to simplify the framework by doing the following:

  1. Remove the ambiguity between ‘R’ and ‘A’ – just have the ‘R’ and define it as Responsible and Accountable
  2. Simplify the ’I’ and the ’C’ by leaving it to the person responsible to decide who needs to be Informed and Consulted

So, this leaves you with just the ’R’ but we can add more useful elements back in. We can now:

  1. Define who needs to Approve a decision – ‘A’ helps to clarify governance
  2. Consider who else is needed to Deliver the work or make a decision

This gives us the ‘RAD’ framework – a simple way of assigning responsibility for activities, identify who needs to approve the work, and who else needs to be involved to make it happen. No unnecessary meetings, complications, or confusion over accountability.

OrgVue enables you to define the link between roles, processes, and activities through a grid that feels similar to a spreadsheet. But once defined, you can clearly can see who is responsible for what within your organization through org chart visualizations. In my view, it’s more important to define what’s in the box rather than where the box sits in the org chart.

Organizational design responsibility matrix

Of course, there are frameworks other than RACI for prescribing accountability in an organization. One of the best is RAPID, developed by Bain Consulting.

In Bain’s words: “High-quality decision-making and strong performance go hand in hand. Yet, in many companies, even clear, well framed decisions can be derailed by uncertainty over roles and responsibilities. To address this common problem, Bain created RAPID®, a loose acronym for Input, Recommend, Agree, Decide. and Perform. RAPID® assigns owners to the five key roles in any decision.”

It’s important to say there‘s no right or wrong framework, but you should avoid complexity. Whichever you choose, OrgVue can help you configure the links between people and work to accommodate your preferred framework.

Getting your accountability matrix right and keeping it simple will pay dividends. By combining this with information on the time people spend on individual activities, you can define the cost of each activity and process. And once you can do this, you’re in a position to identify improvements that would make a significant difference to the productivity (and profitability) of your organization.

Read more on organizational design

In our article What is organizational design?, you’ll learn what happens when org design goes wrong and how to put theory into practice successfully.