RAPID Decision Framework
RAPID is a decision-rights framework developed by Bain & Company in the early 2000s. The acronym defines five roles: Recommend (the person who proposes the decision), Agree (those whose formal sign-off is required, typically legal/compliance), Perform (those who execute the decision once made), Input (those whose perspective should be sought but who don't have veto power), and Decide (the SINGLE person who makes the final call). The model's central insight: most failed decisions aren't failures of analysis — they're failures of clarity about who gets to decide. When 4 people think they have the D, you get conflict; when 0 people think they have it, you get drift. RAPID forces explicit, written assignment of roles BEFORE the decision is made, which is when politics is cheapest.
The Trap
RAPID is often more about politics than process — and pretending otherwise is the framework's biggest trap. In practice, RAPID assignments are heavily contested precisely because everyone wants the D (decision rights) and nobody wants to be just an I (input). Senior leaders often refuse to formalize RAPID because doing so makes their power explicit, which can be politically inconvenient. The other major trap: RAPID-by-committee. Some orgs assign the D to a 'committee' — which is the exact opposite of what RAPID requires. The whole point is one person gets the D. Committees can recommend or input; they cannot decide. Finally, RAPID gets weaponized: senior leaders give the D to a junior person to offload responsibility for a decision that goes wrong, then take credit when it goes right. Real RAPID requires owning your D.
What to Do
For every significant decision, write the RAPID grid before the discussion starts. Step 1: Define the decision in one sentence — be specific (e.g., 'Choose enterprise vs self-serve as primary GTM motion for FY26'). Step 2: Assign exactly ONE person to D — no committees. Step 3: List the As (formal sign-offs needed — usually 1-2 people, often legal/finance/compliance). Step 4: List the Rs (one to three recommenders — too many cooks dilute). Step 5: List the Ps (executors). Step 6: List the Is (input providers — these people will be CONSULTED but won't decide). Step 7: Share the grid with all parties before debate begins. The 30-minute conversation about who has which letter saves weeks of post-decision politicking.
Formula
In Practice
Bain's published case study on a Fortune 100 retailer applied RAPID to their pricing decisions, which had previously involved 12+ stakeholders per SKU and took 6+ weeks per pricing change. After implementing RAPID — with the Category Manager as D, Pricing Analytics as R, Legal as A, Store Ops as P, and Marketing/Finance/Merch as I — average pricing decision time dropped from 6 weeks to 3 days. The deeper effect: managers stopped looping in 'optional' stakeholders just to spread political cover. The framework didn't change WHO was smart; it changed who could veto, which dramatically accelerated decision velocity.
Pro Tips
- 01
The 'one D' rule is non-negotiable. The moment you assign D to a committee or two co-leaders, you've built consensus dependency back in. If the work genuinely needs two decision-makers (rare), restructure the decision into two sub-decisions, each with its own D.
- 02
RAPID grids should be PUBLISHED in the decision memo, not just discussed verbally. Written grids force the political conversation upfront and create accountability. 'Who had the D on this' should be findable in the doc 6 months later.
- 03
Distinguish A (Agree, formal veto) from I (Input, no veto). The most common RAPID gaming move is for senior people to demand A status when they should only have I. Push back: 'Do you actually need to formally sign off, or do you want to be consulted?' Most agree to I when forced to choose. As proliferate when nobody asks the question.
Myth vs Reality
Myth
“RAPID is a process improvement that everyone will embrace”
Reality
RAPID makes power explicit, which is politically threatening to people whose influence depends on ambiguity. Implementations frequently stall because senior leaders block the framework — they prefer the option to inject themselves into any decision rather than commit to a defined role. Successful rollouts require executive air cover and willingness to overrule political resistance.
Myth
“RAPID slows decisions because of all the upfront role-assignment work”
Reality
The opposite. The 30-minute role-assignment conversation upfront eliminates weeks of post-decision conflict and re-litigation. Bain's research shows orgs that adopt RAPID see 30-60% faster decision cycles for significant decisions. The 'slowness' of RAPID is concentrated upfront where it can be managed; without RAPID, the slowness is distributed across the entire decision lifecycle invisibly.
Try it
Run the numbers.
Pressure-test the concept against your own knowledge — answer the challenge or try the live scenario.
Knowledge Check
Your company is choosing a new HRIS system. The CHRO wants the D. The CFO insists she also needs the D because of cost. The CEO suggests a 'joint decision.' What's the RAPID-correct answer?
Industry benchmarks
Is your number good?
Calibrate against real-world tiers. Use these ranges as targets — not absolutes.
Decision Cycle Time (Significant Decisions)
Decisions involving 5+ stakeholders.RAPID-Implemented Org
5-10 days
Average Mid-Market
15-25 days
Bureaucratic
30+ days
Source: https://www.bain.com/insights/decide-and-deliver-five-steps-to-breakthrough-performance-in-your-organization/
Real-world cases
Companies that lived this.
Verified narratives with the numbers that prove (or break) the concept.
Bain & Company (Origin)
2006-Present
Bain & Company developed RAPID in the mid-2000s and published the foundational research in their book 'Decide & Deliver' (2010), based on a 760-company study. Their data showed that organizations in the top quartile of decision effectiveness outperformed bottom quartile peers by 2x on financial returns. Bain's published case studies span Fortune 100 retail (pricing decisions cut from 6 weeks to 3 days), pharma (drug development go/no-go decisions clarified, accelerating pipeline by 30%), and tech (M&A decisions standardized, with 50% reduction in time-to-close). RAPID has since been adopted by an estimated 30%+ of Fortune 500 companies as the default decision-rights framework.
Companies in Foundational Study
760
TSR Multiplier (Top vs Bottom Decision Effectiveness)
2x
Fortune 500 Adoption
~30%+
Year Codified
2006-2010
RAPID is one of the most empirically validated decision frameworks in business. The 2x TSR data is rigorous. Skepticism about RAPID is usually political (people don't want explicit role definition) rather than analytical.
Procter & Gamble (Lafley era)
2000-2009
When A.G. Lafley took over P&G in 2000, decision velocity was a major problem — major brand decisions (e.g., Tide repositioning) routinely took 12+ months and 50+ stakeholders. Lafley implemented RAPID-style decision rights across the brand portfolio. Key shift: brand managers (not committees) got the D for brand-level decisions, with category leaders as A and corporate marketing as I. Time-to-decision for major brand changes dropped from 12 months to 3-4 months. P&G's 9-year revenue growth under Lafley (2000-2009): $40B → $79B, with decision velocity cited as a major operational lever in his memoir 'The Game-Changer.'
Brand Decision Cycle (Pre)
12+ months
Brand Decision Cycle (Post)
3-4 months
Revenue Growth (Lafley tenure)
$40B → $79B
Stakeholders per Decision (Pre → Post)
50+ → 8-10
Even in a 200,000-person CPG giant, RAPID-style clarity dramatically accelerates decision-making. Scale doesn't excuse slowness — it requires explicit decision-rights frameworks.
Hypothetical: 'RAPID Theater' Implementation
2022
Hypothetical: A 400-person enterprise SaaS company hired a consulting firm to implement RAPID. Six weeks of workshops produced 50+ documented RAPID grids for major decision categories. Glossy decks were presented to the board. But the CEO refused to actually delegate Ds — he kept inserting himself into every brand, product, and pricing decision despite the published grids saying 'D = Brand Manager.' Within 6 months, the RAPID grids were a fiction nobody referenced. Decision velocity actually got WORSE because employees felt cynical about leadership. Two senior executives quit citing 'culture of false empowerment.' RAPID became another example of process theater.
RAPID Grids Documented
50+
Grids Actually Followed
~5
Decision Velocity Change
Slightly worse
Senior Exec Attrition
2 in 12 months
RAPID without CEO commitment is worse than no RAPID. The framework explicitly limits CEO discretion, which most CEOs find harder to accept than they admit. Diagnose your CEO's willingness to NOT have the D before investing in implementation.
Decision scenario
The Pricing War
You're CRO at a $40M ARR SaaS company. Your competitor just dropped pricing 30%. Your VP of Marketing wants to match immediately. Your VP of Finance wants to hold pricing to protect gross margin. Your CEO is texting you for a recommendation. The decision needs to be made within a week.
Competitor Action
30% price cut announced
Decision Window
1 week
Stakeholders Asserting D
VP Marketing, VP Finance, CEO, CRO
RAPID Grid Status
Not defined
Decision 1
You can let the conflict play out (slow), escalate to the CEO (creates bottleneck), or apply RAPID to clarify roles immediately.
Convene a 'pricing committee' with VP Marketing, VP Finance, you, and CEO — let the group decide togetherReveal
Within 24 hours, publish a RAPID grid: D = CRO (you — pricing strategy is your accountability). R = VP Pricing + VP Marketing. A = CFO (margin floor sign-off only). I = CEO + VP Sales + Customer Success. Make a clear recommendation within 4 days, get sign-offs in day 5, communicate decision in day 6.✓ OptimalReveal
Related concepts
Keep connecting.
The concepts that orbit this one — each one sharpens the others.
Beyond the concept
Turn RAPID Decision Framework into a live operating decision.
Use this concept as the framing layer, then move into a diagnostic if it maps directly to a current bottleneck.
Typical response time: 24h · No retainer required
Turn RAPID Decision Framework into a live operating decision.
Use RAPID Decision Framework as the framing layer, then move into diagnostics or advisory if this maps directly to a current business bottleneck.