Most teams do not have a decision-making problem. They have a decision-rights problem: everyone has an opinion, several people believe they can say no, and nobody is quite sure who is allowed to say yes. The RAPID decision-rights matrix, developed by Bain & Company, was built for exactly that confusion. It gives every person in a decision one clear role, so that disagreement can end in a choice rather than another meeting.

This guide explains the five roles, shows worked examples you can copy, and looks at the human behaviour that makes the framework fail even when it is drawn correctly.

What is the RAPID decision-rights matrix?

The RAPID decision-rights matrix is a tool for assigning roles in an important decision. RAPID stands for Recommend, Agree, Perform, Input and Decide. Instead of asking “who is involved?”, it asks a sharper question: what exactly is each person’s job in this decision, and how much power does that job carry?

The model was introduced by Bain’s Paul Rogers and Marcia Blenko in their January 2006 Harvard Business Review article, Who Has the D? How Clear Decision Roles Enhance Organizational Performance. RAPID is a registered trademark of Bain & Company. It is now widely used in consulting, product teams, non-profits and boardrooms.

In one line: one person recommends, a few people may block on specific grounds, others advise, one person decides, and named people execute.

The five RAPID roles explained

Two details matter more than the acronym suggests.

First, the letters are not the sequence. In practice the roles usually unfold as Recommend, Input, Agree, Decide and Perform. Nobody would remember “RIADP”, which is why the catchier order won.

Second, the Agree role is deliberately rare. In Bain’s guidance on RAPID, agree roles are assigned sparingly, the agreer works with the recommender early, and if the two cannot reconcile their views, the decider makes the final call. Anyone who exercises a veto must either offer an alternative or escalate the issue to the person with the D. A veto that simply says “no” and walks away is not a RAPID veto at all.

A worked RAPID example: launching a new pricing tier

Imagine a hypothetical Mumbai fintech deciding whether to launch a premium subscription tier.

Notice what is absent. The Sales Director, however senior, does not have an A. Sales has an essential voice, so it holds an I and a P. If sales leadership could block pricing, every price would quietly drift towards whatever is easiest to sell. Finance holds an A only because the brief requires the tier to protect margin. That is a specific condition, not a general seat at the top table.

A second example: a people decision

RAPID works just as well for decisions that are emotionally charged rather than commercial. Consider a hypothetical restructuring of two regional teams into one.

The quiet design choice here is that the two regional managers are both I and P. People who must carry out a decision commit to it far more readily when they have shaped it. Bain advises defining perform roles early and giving performers an input role, because they can flag implementation issues and are more likely to buy into the final decision.

RAPID vs RACI vs DACI

Readers comparing frameworks usually want to know which to use. The short answer is that they answer different questions.

RAPID’s distinctive contribution is that it makes veto power visible and narrow. RACI tells you who does the work. RAPID tells you who can stop it, and why.

Why decisions stall even after the matrix is drawn

Here is where I think most explanations of RAPID stop too early. The framework is simple. The behaviour around it is not.

In their Harvard Business Review article, Lindy Greer, Maxim Sytch and Jennifer Jordan examine four common mistakes that undermine decision rights. One of their observations deserves attention: when teams assign roles before goals are carefully defined, discussions about decision rights often degenerate into ego-driven turf wars. Their opening case describes twelve executives at a global technology company crowding around a table to make a heated final decision, when only the executives in the responsible role should have been in the room with the CEO.

Why does that happen? Because a decision role is never only a role. It is a statement about status. Being invited into the room where the decision is made feels like belonging. Being given an I can feel like being told your judgement matters less. David Rock’s SCARF model is a neuroscience-informed way of describing the social threats people react to: status, certainty, autonomy, relatedness and fairness. A RAPID chart can touch almost every one of them at once. Small wonder people push for an A they do not need.

This produces a pattern I want to name, because once you see it you will see it everywhere.

The shadow veto is the unofficial power to stop a decision, held by someone who was never given the A. It is rarely exercised openly. It looks like a late objection after the recommendation is finished, a meeting that keeps being rescheduled, a “let’s take this offline”, or a senior person who never says no but never says yes. Bain notes the same behaviour from the other side: some people in the A role wait for the decision instead of weighing in on the recommendation, then play what they wrongly believe is a veto card, undermining the decision maker and causing further delay.

The shadow veto survives because it is cheap. Blocking costs nothing; deciding exposes you. Psychologists have long described diffusion of responsibility, the tendency for individual accountability to thin out when many people share a situation. A decision with five possible blockers and no clear D is diffusion of responsibility with a calendar invite.

A moment of reflection

If you lead a team, sit with these for a minute:

• Which recurring decision in your organisation keeps returning to the table, and who quietly benefits from it never being final?
• Where do you hold a shadow veto yourself, slowing things down without ever saying no?
• If you were forced to write one name next to the D, would the rest of the room accept it, or only tolerate it?

How to build a RAPID matrix that actually works

1. Define the decision before the roles. Write the decision as a single question with a deadline, plus the criteria a good answer must meet. Roles assigned before this become a negotiation about status.
2. Name the D first. Choose the person closest to where the decision will be lived who still sees the full trade-offs. If the decide role must be held by a group, agree up front how it will reach a final decision when there is no agreement, such as a majority vote or the chair’s casting say.
3. Appoint one R and give them real authority to run the process. Bain describes recommenders as the quarterbacks of the decision process. A weak R produces a decision nobody can make.
4. Ration the A. For every proposed A, ask whether this person protects a specific legal, regulatory, financial or technical condition. If not, they are an I. One company Bain describes reassigned decision rights so that its regulatory team held an A only on the text of a brochure, to keep it compliant with federal regulations. Compliance protected what needed protecting without holding the whole project hostage.
5. Invite performers early as inputs. The people who execute will spot implementation problems before anyone else.
6. Make the matrix public and time-bound. Share it with everyone involved, record the decision and the rationale, and review the roles when the strategy, structure or team changes.
7. Watch for the shadow veto. When someone objects late, ask one calm question: “Which role do you hold on this decision?” It is surprisingly clarifying.

Does clear decision-making really affect performance?

Bain’s own research suggests it does. In a survey of almost 800 companies, Bain reported a 95% correlation between companies that excel at making and executing key decisions and those with top-tier financial results, measured by revenue growth, return on capital or total shareholder return. That is consultancy research rather than peer-reviewed science, and correlation is not causation. Still, it matches what many leaders sense: organisations rarely fail for lack of intelligence. They fail for lack of decisions.

The idea has travelled far beyond consulting. Uber’s chief executive Dara Khosrowshahi told company leaders in a memo to say openly who “has the D” in meetings, a phrase he likely borrowed from the 2006 article.

Where RAPID fits in a leader’s toolkit

RAPID does not tell you what to decide. For that, you still need strategic tools such as the BCG Matrix for portfolio choices or the OODA loop for fast-moving situations. What RAPID governs is who decides, and that is a deeply human question shaped by status, shame and power.

It also exposes the leader who holds the D. When you are the final decider, the information reaching you is often softened on the way up, a pattern I have called the altitude filter. A good matrix can tell you who should speak to you. It cannot make them honest. That part is leadership. It is the kind of work I explore with senior leaders in executive coaching, where the question is rarely “which framework?” and usually “why do I avoid the D?”

The real test of a RAPID matrix

A RAPID chart on a slide proves nothing. The real test arrives the first time someone with no A tries to stop a decision. Then the person holding the D has to say, kindly and clearly, “Thank you, I have heard you, and I am deciding.” Frameworks give us permission to be clear. Courage is what turns that permission into a decision.

If a recurring decision in your organisation keeps stalling and you would like to think it through with someone outside the room, you can book a free 15-minute consultation.

Dr Krishna Athal Life & Executive Coach | Corporate Trainer | Leadership Consultant

Dr Krishna Athal is a Life & Executive Coach, Corporate Trainer and Leadership Consultant working across India, Mauritius and Singapore. His work integrates psychology, neuroscience, emotional intelligence and human behaviour.

See Full Bio

Life & Executive Coaching Life Coaching Executive Coaching