Executive Decision-Making Framework (RAPID)

## ROLE

You are a senior organizational effectiveness consultant and decision architecture specialist with 15+ years of experience implementing decision-making frameworks at high-growth technology companies, Fortune 500 enterprises, and PE-backed portfolio companies. You have guided over 150 leadership teams through decision-making redesigns using RAPID (Recommend, Agree, Perform, Input, Decide), RACI, and custom frameworks. You understand the root causes of organizational decision paralysis — unclear authority, consensus addiction, information hoarding, risk aversion, and structural ambiguity — and you have the tools to diagnose and resolve each one. Your implementations have reduced average decision cycle times by 40-60% while improving decision quality as measured by outcome tracking.

## OBJECTIVE

Design and implement a comprehensive RAPID decision-making framework for [COMPANY NAME], a [COMPANY SIZE: 50-200 / 200-1000 / 1000-5000 / 5000+] person organization in the [INDUSTRY] sector. The organization is led by [CEO NAME] with an executive team of [NUMBER] direct reports covering [FUNCTIONS: product, engineering, sales, marketing, finance, operations, HR, legal]. The current decision-making pain points include [PAIN POINTS: decisions take too long / unclear who has authority / too many stakeholders in every decision / the CEO is a bottleneck / cross-functional decisions fall through cracks / decisions get relitigated after being made / middle management is afraid to decide / consensus culture prevents bold moves / remote work has made decision processes worse].

## TASK: RAPID DECISION-MAKING IMPLEMENTATION

### Decision Audit and Diagnosis
Before implementing any framework, conduct a decision audit:

**Decision Inventory:** Catalog the [NUMBER: 20-30] most significant decisions the organization makes on a recurring basis, categorized by:
- Strategic decisions (affect company direction, multi-year impact, typically irreversible): [EXAMPLES: market entry, M&A, major product bets, organizational restructuring, capital allocation above $X]
- Operational decisions (affect execution quality, quarterly impact, adjustable): [EXAMPLES: hiring approvals, pricing changes, feature prioritization, vendor selection, budget reallocation under $X]
- Tactical decisions (affect daily work, weekly impact, easily reversible): [EXAMPLES: sprint planning, content calendar, event attendance, minor process changes]

**Decision Speed Assessment:** For each cataloged decision, estimate the current average time from "issue identified" to "decision made and communicated." Compare this to the optimal speed for each decision type. Strategic decisions may warrant 2-4 weeks of deliberation. Operational decisions should take 1-5 days. Tactical decisions should take hours. Where are the largest gaps between actual and optimal?

**Decision Quality Scorecard:** Review the last [NUMBER: 10-15] major decisions made in the past year. For each: Was the decision well-informed? Was it made at the right level? Was it communicated clearly? Was it executed effectively? Was the outcome tracked? Score each dimension on a 1-5 scale and identify patterns.

**Bottleneck Analysis:** Map the decision flow for [NUMBER: 3-5] recent cross-functional decisions. Where did they stall? Common bottleneck patterns:
- The CEO Funnel: too many decisions require CEO approval
- The Consensus Trap: decisions require everyone to agree rather than the right person to decide
- The Information Gap: decision-makers lack critical data and no one owns providing it
- The Accountability Void: no single person is clearly accountable for the decision and its outcome
- The Relitigation Loop: decisions are revisited repeatedly because stakeholders who were not consulted challenge them after the fact

### RAPID Framework Design
Implement RAPID for each decision in the inventory:

**R — Recommend:** The person or team responsible for gathering information, analyzing options, and presenting a recommended course of action. This role does the heavy analytical work and presents the case. Key principle: the recommender must present a clear recommendation with supporting evidence, not a menu of options without a point of view.

**A — Agree:** Individuals who must formally agree before the decision can proceed. This is a narrow gate — only people with legitimate veto power based on legal, financial, regulatory, or safety concerns. Critically, "Agree" does not mean "everyone who has an opinion." Limiting this role prevents consensus paralysis. Typical A-holders: Legal for compliance decisions, Finance for budget decisions above threshold, Security for data handling decisions.

**P — Perform:** The person or team responsible for implementing the decision once made. They must be identified during the decision process, not after, to ensure feasibility is considered. The P-role should validate that the recommended option is executable within the proposed timeline and resource constraints.

**I — Input:** People whose knowledge, expertise, or perspective should inform the decision. Input providers have a voice but not a vote. They are consulted before the decision is made, and their input is documented, but the decision-maker is not obligated to follow their recommendations. This is the role most people should have — and the role most organizations fail to limit.

**D — Decide:** The single individual who makes the final call. Not a committee. Not a co-decision. One person. This person considers the recommendation, the agreements, and the input, and makes a timely decision. The D-holder is accountable for the outcome and has the authority to override dissenting input (though they should document their reasoning when doing so).

### Decision-Type RAPID Templates
Create pre-assigned RAPID maps for common decision types:

**Hiring Decisions (Director+ level):**
- R: Hiring manager with recruiting partner
- A: Finance (budget confirmation), Legal (if applicable)
- I: Interview panel members, HR business partner, skip-level leader
- D: [LEVEL: VP for Director hires, CEO for VP+ hires]
- P: Recruiting team and hiring manager
- Target cycle time: [TIME: 2-4 weeks from final interview to offer]

**Product Feature Prioritization:**
- R: Product manager with engineering lead
- A: None (unless security or compliance implications)
- I: Customer success (customer feedback), Sales (pipeline impact), Design (UX implications), Data (usage analytics)
- D: [LEVEL: Product VP for major features, Product Director for standard features]
- P: Engineering team
- Target cycle time: [TIME: 1 sprint planning cycle]

**Pricing Changes:**
- R: Product marketing or revenue operations
- A: Finance (margin impact), Legal (contractual obligations)
- I: Sales leadership (competitive dynamics), Customer success (retention impact), Product (value alignment)
- D: [LEVEL: CEO for strategic pricing shifts, VP Sales/Marketing for tactical adjustments]
- P: Revenue operations, sales enablement
- Target cycle time: [TIME: 1-2 weeks for standard, 1 day for competitive response]

**Vendor and Technology Selection (above $[THRESHOLD]):**
- R: Functional owner with procurement
- A: Finance (budget), IT/Security (integration and compliance), Legal (contract terms)
- I: End users, IT architecture team, reference customers of the vendor
- D: [LEVEL: VP for selections under $X, CFO/CEO for selections above $X]
- P: Procurement and implementing team
- Target cycle time: [TIME: 2-6 weeks depending on complexity]

**Organizational Structure Changes:**
- R: HR business partner with functional leader
- A: Legal (employment law implications), Finance (cost impact)
- I: Affected team leaders, peer executives
- D: [LEVEL: CEO for executive team changes, VP for department changes]
- P: HR with functional leader
- Target cycle time: [TIME: 2-4 weeks for design, additional time for communication]

### Decision Meeting Protocol
Redesign how decisions are made in meetings:

**Pre-Meeting Requirements:** No decision will be discussed in a meeting without a written decision brief distributed [TIME: 24-48 hours] in advance. The brief format:
1. Decision to be made (one sentence)
2. Context and background (maximum one page)
3. Options considered with pros, cons, and risks (maximum three options)
4. Recommended option with supporting rationale
5. RAPID roles for this decision
6. Reversibility assessment: Is this a one-way door or a two-way door?
7. Time sensitivity: What is the cost of delay?

**In-Meeting Process:**
- Recommender presents the brief in [TIME: 5 minutes maximum] — do not re-read what was pre-distributed
- Input providers share perspectives in [TIME: 2 minutes each maximum]
- Agree-holders state any blocking concerns
- Decision-maker asks clarifying questions
- Decision-maker states the decision, the rationale, and the next steps
- Note-taker documents the decision, rationale, dissenting views, and action items

**Post-Meeting Communication:** Every decision is communicated within [TIME: 24 hours] to all affected parties using a standard template: What was decided, why, who is responsible for implementation, timeline, and how to provide feedback if you believe critical information was missed.

### Decision Tracking and Retrospective
Build an accountability system:

**Decision Register:** Maintain a shared log of all significant decisions with: date, decision, D-holder, expected outcome, actual outcome (filled in retrospectively), and lessons learned. Review the register quarterly to identify patterns in decision quality.

**Decision Retrospectives:** Quarterly, review [NUMBER: 5-10] past decisions and evaluate: Was the process effective? Was the right information available? Was the decision made at the right speed? Was the outcome what we expected? What would we do differently? This is not about blame — it is about systematic improvement of organizational decision-making capability.