RACI

RACI is a responsibility matrix used to make execution, accountability, consultation and information flow explicit inside a process. It is useful when work falls between roles, approvals wait without an owner, or people keep saying “I thought you were handling it”. Used well, a RACI is not bureaucracy. It is a compact agreement about who does what and who ultimately answers for the result.

In brief

When something does not get done in a company, the most common explanation is rarely laziness. More often, everyone thought it belonged to someone else. The RACI matrix addresses this ambiguity by assigning four roles for each activity in a flow: Responsible, Accountable, Consulted and Informed.

The distinction looks simple, but it is powerful. The Responsible performs the work. The Accountable owns the outcome. The Consulted contributes before the decision or action. The Informed is notified after. A good RACI replaces repeated clarification emails with a visible operating agreement. A bad RACI becomes the bureaucracy critics complain about.

Operational definition

The four letters define four different relationships to the work.

Responsible means the role that executes the activity. There can be more than one responsible person when execution is shared, but the activity still needs to be described clearly enough that execution is observable.

Accountable means the role that answers for the outcome. For each activity there should be exactly one Accountable. This is the golden rule. Two Accountables usually mean none: when the result is missing, each can reasonably believe the other was carrying the final responsibility.

Consulted means a role whose input is needed before the decision or activity is completed. This is two-way communication. The role is not merely notified; it has information that can change the outcome.

Informed means a role that needs to know after the fact. This is one-way communication. Confusing Informed with Consulted is one of the fastest ways to slow an organisation: every unnecessary C adds a possible delay, a meeting, or a political veto.

A RACI should be built around a process, not around the organisation chart. The rows are activities inside a mapped flow. The columns are roles. A matrix built from abstract departmental responsibilities often ends up unused, because it does not answer the real question that appears in work: who owns this specific step now?

Why it matters for SMEs

In many SMEs the implicit Accountable for everything is the founder. At very small scale this works. As the company grows, it creates two opposite symptoms.

First, everything escalates to the founder. People wait for approval, even when the decision is small. Second, some things fall into the void. If the founder is implicitly accountable for everything, then nobody is explicitly accountable for many specific activities.

A RACI is a first practical instrument of structured delegation. It does not say “trust people and let them figure it out”. It says: for this activity, this role executes, this role answers, these roles must be consulted, and these roles only need to be informed.

For external readers, the same issue appears as key person risk. A company whose responsibilities are concentrated in the founder is harder to transfer, scale and integrate. A company with explicit responsibility boundaries can show that its operating model is not entirely embedded in one person.

Observable signals

The need for a RACI appears in recurring phrases.

“I thought you were doing it” indicates no clear Responsible.

“I did not know I could decide without you” indicates a contested or undeclared Accountable.

“Why was I not involved?” indicates that Consulted and Informed were never defined.

“I was waiting for approval” without anyone knowing who had to approve is a ghost approval: a costly form of pure waiting.

A quantitative signal is waiting time without corresponding work. If a mapped flow shows long pauses at specific steps, the cause may not be workload. It may be an undeclared authorisation owner.

Common mistakes

The first mistake is filling the RACI from the official version of the process. This produces a matrix for the nominal process: elegant, politically acceptable and often false. A useful RACI is built on the real flow.

The second mistake is the perforated matrix: two Accountables for the same activity, too many Consulted roles added for diplomacy, or rows where everyone is assigned something. A healthy RACI contains many empty cells. Empty space is information: it says this role is legitimately not involved in this activity.

The third mistake is treating the matrix as a document rather than an agreement. A RACI does not simply describe reality; it commits the organisation to a way of acting. If nobody uses it when something gets stuck, it dies within weeks.

The fourth mistake is the wrong level of detail. A RACI for macro-areas such as “sales is responsible for revenue” decides nothing. A RACI for every micro-task becomes unmanageable. The right granularity is the activity where a real misunderstanding can occur.

Operational example

A 35-person service company has a slow quotation flow. Median lead time is 11 days, with peaks at 20. Process mapping shows that actual work takes around six hours. The rest is waiting, concentrated in two points: technical validation and discount approval.

The RACI built on the real flow reveals why. For technical validation, two roles were considered possible Accountables: the technical manager and the deputy, “depending on who was there”. Each tended to wait for the other. For discount approval, the formal Accountable was the sales manager, but the founder intervened unpredictably, so the sales manager waited for both “just to be safe”.

The corrections were simple: one Accountable for technical validation, with written escalation criteria for complex cases; and an explicit discount threshold, where the sales manager could approve alone below 8%, while the founder was required above that threshold.

After eight weeks, median quotation lead time fell to five days. No new hire, no software. Only assumed responsibility replaced by declared responsibility.

Diagnostic questions

For the five or six critical activities in the main flows, could the company write the single Accountable for each one right now, without a long meeting?

Would the people involved write the same names?

How much waiting time in the flow is waiting for authorisations that nobody has formally established?

These questions connect RACI to time. Responsibility ambiguity is not only a climate problem. It is a lead time problem.

Practical implications

The correct sequence is: first map the real flow, then build the RACI on the activities that emerged, then actively use the matrix for a few operating cycles.

When something gets stuck, the first question should be “who was Accountable?” before “who is to blame?” The difference is structural. The first question tests the architecture of responsibility. The second processes people.

After several cycles, a good RACI becomes less visible because the organisation has internalised it. The success of a RACI is often measured by how rarely people need to open the document.

MARTRO reading

In MARTRO’s reading, RACI is not primarily a deliverable. It is a detector. The act of building the matrix together, on the real flow, exposes divergences that the organisation has accumulated over time.

Where the matrix is easy to fill, responsibility was already clear. Where discussion heats up, the delay or conflict was already pointing to a gap. This is why MARTRO treats RACI as diagnostic before prescriptive. It is also the natural bridge between process work and governance: when the ambiguity is no longer about who executes, but about who decides, the topic becomes decision rights.

When to go deeper

Go deeper when the same responsibility misunderstandings repeat or when authorisation waits dominate lead time. Natural next steps are decision rights, role gap and the practical guide on how to build a RACI without creating bureaucracy.

Frequently asked questions

Is RACI the same as the organisation chart? No. The organisation chart shows reporting lines. RACI shows who executes and who answers for specific activities inside a flow. In SMEs the two often diverge, and the RACI is usually closer to how the company really works.

How many RACI matrices are needed? Few. Only for flows where ambiguity produces measurable damage. Ten used and updated matrices are better than fifty archived ones.

Are there variants? Yes: RASCI, DACI and RAPID are common alternatives or complements. For most SMEs, the basic RACI covers the majority of operational ambiguity.

Why would an investor care about RACI? Because it documents whether responsibilities are transferable. It shows how much of the operating model depends on explicit roles and how much still depends on the founder.