RAPID Framework for Organizational Decisions Without Deadlock

Apply the RAPID Framework to unblock a critical decision in my organization.\\\\\\\\n\\\\\\\\n**The Decision at Hand:**\\\\\\\\n- Description: [DESCRIBE THE DECISION]\\\\\\\\n- Why it's stalled: [EXPLAIN — e.g., many stakeholders, no owner, conflicting opinions, fear of making the wrong call]\\\\\\\\n- How long it's been pending: [TIME PERIOD]\\\\\\\\n- Impact of NOT deciding: [DESCRIBE THE COST OF INACTION]\\\\\\\\n- People involved: [LIST WITH TITLE AND STAKE IN THE DECISION]\\\\\\\\n\\\\\\\\n**Apply RAPID:**\\\\\\\\n\\\\\\\\n1) **R — Recommend (Who recommends?):**\\\\\\\\n- Who should research and bring a structured recommendation?\\\\\\\\n- Recommendation format: options analysis, pros/cons, recommendation with justification\\\\\\\\n- Deadline to deliver the recommendation: [SUGGEST]\\\\\\\\n\\\\\\\\n2) **A — Agree (Who must agree?):**\\\\\\\\n- Who has veto power? (keep it to a minimum — 1 to 2 people)\\\\\\\\n- Clear approval criteria: what would convince this person?\\\\\\\\n- Process if there's a veto: how do you resolve the impasse?\\\\\\\\n\\\\\\\\n3) **P — Perform (Who executes?):**\\\\\\\\n- Once decided, who implements?\\\\\\\\n- Resources needed\\\\\\\\n- Execution timeline\\\\\\\\n\\\\\\\\n4) **I — Input (Who provides input?):**\\\\\\\\n- Who should be consulted BEFORE the decision?\\\\\\\\n- Input format: asynchronous (document) or synchronous (short meeting)\\\\\\\\n- Deadline to submit input: [SUGGEST]\\\\\\\\n- Rule: input is considered but is not a veto\\\\\\\\n\\\\\\\\n5) **D — Decide (Who decides?):**\\\\\\\\n- ONE person with final authority (not a committee)\\\\\\\\n- What happens if the Decider disagrees with the Recommender?\\\\\\\\n- Decision communication: who informs whom, through what channel\\\\\\\\n\\\\\\\\n**Complete RAPID Map:**\\\\\\\\n- Visual table: Person | Role (R/A/P/I/D) | Specific Responsibility | Deadline\\\\\\\\n\\\\\\\\n**Decision Timeline:**\\\\\\\\n- Day 1-[N]: Input collection\\\\\\\\n- Day [N]: Recommender delivers recommendation\\\\\\\\n- Day [N+1]: Agree validates or vetoes\\\\\\\\n- Day [N+2]: Decider makes the call\\\\\\\\n- Day [N+3]: Communication and execution begins\\\\\\\\n\\\\\\\\n**Future Prevention:**\\\\\\\\n- RAPID template for future decisions\\\\\\\\n- Rule: any decision impacting [CRITERIA] must have RAPID defined before discussion begins\\\\\\\\n- How to document in the Decision Log\\\\\\\\n\\\\\\\\nAdapt the language for your business context, where hierarchy matters but collective decision-making is common.