RAPID: Making Veto Rights Explicit

Summary

RAPID assigns five roles to a decision: Recommend drives the proposal, Agree holds a bounded veto, Input informs without blocking, Decide is the single person who makes the call, and Perform executes it. Developed by Bain & Company and published by Rogers and Blenko in Harvard Business Review in 2006, it is the best-documented framework in this whole set, with a genuine evidence base linking clear decision roles to organizational performance. The letters are roles, not a sequence; reading them as a workflow is the classic beginner error. Use it for the ten to twenty high-stakes, recurring decisions in a large organization where authority is the bottleneck; use the lighter DACI for fast product-team calls, and a RACI-family matrix for tasks.

The letters

RAPID assigns roles to a specific decision, not to a task. The letters are roles, not a sequence, which is the single most common thing people get wrong about it.

Although the acronym spells R-A-P-I-D, the roles play out in a more logical order: Recommend gathers Input, secures the Agree parties’ consent, the single Decider decides, and then Perform executes. Reading RAPID as a workflow rather than as five parallel roles is the classic beginner error.

Origin and history

RAPID is one of the few matrices in this entire set with a firm, named provenance. It was developed by Bain & Company and set out in the Harvard Business Review article “Who Has the D? How Clear Decision Roles Enhance Organizational Performance” (January 2006), written by two Bain senior partners, Paul Rogers and Marcia W. Blenko. The framework was elaborated further in the book Decide & Deliver: Five Steps to Breakthrough Performance in Your Organization (Blenko, Mankins and Rogers, 2010). RAPID is a registered trademark of Bain & Company.

• Paul Rogers was a Bain partner based in London who led the firm’s global organization practice.
• Marcia W. Blenko was a Bain partner based in Boston who led the firm’s North American organization practice.

The framework emerged from Bain’s client work on a recurring pain point: decisions getting stuck at predictable bottlenecks (global versus local, center versus business unit, function versus function, inside versus outside partners) because it was unclear who actually had the authority to decide. Bain’s specific contribution was to make veto rights explicit through the Agree role, to separate those veto rights from mere advisory input, and to insist on a single decider. The approach has since been adopted at scale by organizations including LinkedIn, whose then-chief executive Jeff Weiner described using it, and Coinbase.

What problem it solves

RAPID exists because responsibility matrices handle decisions poorly. A RACI chart tells you who builds a thing, but not who is allowed to say yes to building it. In large organizations the expensive failure is not unclear tasks but unclear authority: decisions stall, get relitigated, or are quietly vetoed by people whose role in the call was never defined. Bain’s research found that a large share of meetings end without the intended decision being made, and that executives are widely dissatisfied with their organizations’ decision effectiveness.

RAPID’s answer is to name, for a given decision, exactly who recommends, whose consent is genuinely required, who merely informs, and, above all, who decides. The discipline of a single D and a deliberately limited set of A’s is what breaks the gridlock. It converts a fuzzy cloud of stakeholders into a clear decision process with one accountable decider and an explicit, bounded set of veto-holders.

When to choose it, and when not

Choose RAPID for high-stakes, recurring decisions in large and complex organizations, especially where cross-functional bottlenecks are the problem: major capital investments, pricing strategy, portfolio choices, organizational structure, and the handful of decisions that most affect performance. Bain suggests applying it to the top ten to twenty decisions rather than to everything. It is at its best where the friction is authority and where the cost of a stalled or relitigated decision is large.

Do not use it for tasks; that is what the RACI family is for. Do not apply it to every small decision, where its overhead outweighs the benefit. And for a small product team that simply needs a clear owner and a fast call, the lighter DACI is usually a better fit than RAPID’s heavier machinery.

Common pitfalls

• Reading the letters as a sequence. RAPID is a set of roles, not a five-step process. Treating P (Perform) as coming before D (Decide) because it appears earlier in the acronym causes real confusion.
• Too many Agrees. Every A is a veto. Grant the Agree role sparingly, or you rebuild the gridlock you were trying to remove.
• Confusing Input with Agree. Input informs; Agree can block. Blurring them either gives advisors a veto they should not have or strips genuine veto-holders of their power.
• More than one Decider. The single D is the heart of the framework. Two deciders is no decider.
• Applying it everywhere. RAPID is for the decisions that matter most. Spread it across trivial calls and it becomes bureaucracy.

Worked example

A decision on whether to enter a new market segment, in a large firm.

The value is in the boundaries. Sales, Finance, and Operations inform the recommendation but cannot block it. Legal and Compliance genuinely can block, and that veto is stated openly rather than exercised by ambush. Exactly one person decides. Everyone knows their role before the decision is live, which is what stops the call from stalling or being reopened after the fact.

Where it sits in the family

RAPID is the heavyweight of the decision-rights family, built for scale and for high-stakes recurring decisions. Its lighter counterpart is DACI, which strips the framework down to a Driver and a single Approver for faster, product-team decisions. The two share the core insight that the person who drives a decision (Recommend, or Driver) is not the person who makes it (Decide, or Approver). Choose RAPID when the organization is large, the decision matters, and the bottleneck is authority spread across functions; choose DACI when you want the same clarity with less ceremony.

Sources

Web sources

• Who Has the D?, Bain & Company (RAPID is a registered trademark of Bain): https://www.bain.com/insights/who-has-the-d/
• RAPID: Bain’s tool to clarify decision accountability, Bain & Company: https://www.bain.com/insights/rapid-tool-to-clarify-decision-accountability/
• Who has the D?, Semantic Scholar (article record, Rogers and Blenko): https://www.semanticscholar.org/paper/Who-has-the-D-How-clear-decision-roles-enhance-Rogers-Blenko/ecc795c32e3e9b94cca0f241c0905ffa7c6396b9

Academic sources

• Rogers, P. and Blenko, M.W. (2006) ‘Who has the D? How clear decision roles enhance organizational performance’, Harvard Business Review, 84(1), pp. 52-61. The founding article, including the four bottlenecks and the role definitions. Reprint R0601D.
• Blenko, M.W., Mankins, M.C. and Rogers, P. (2010) ‘The decision-driven organization’, Harvard Business Review, 88(6), pp. 54-62. Extends the argument from single decisions to organization design.
• Blenko, M.W., Mankins, M.C. and Rogers, P. (2010) Decide & Deliver: Five Steps to Breakthrough Performance in Your Organization. Boston, MA: Harvard Business Press. The book-length treatment, with Bain’s supporting research on decision effectiveness.
• Jensen, M.C. and Meckling, W.H. (1992) ‘Specific and general knowledge, and organizational structure’, in Werin, L. and Wijkander, H. (eds.) Contract Economics. Oxford: Blackwell, pp. 251-274. The decision-rights theory RAPID operationalizes.