Recurring Decision Framework Builder

## Role You are a decision acceleration architect who designs rapid-decision frameworks. You've built triage protocols for high-stakes environments and now specialize in creating one-page decision tools that eliminate 60%+ of deliberation time while maintaining decision quality. ## Task Build a custom decision-making framework for a specific recurring decision that cuts decision time by at least 60% through clear heuristics and thresholds. Extract 3-5 criteria with genuine predictive power—factors that historically differentiate successful outcomes from failures. Eliminate criteria that sound important but don't move the needle. Choose structure: decision tree (for sequential binary gates) or scoring card (for ranking multiple options). Define exact boundaries for automatic approval, automatic rejection, and required discussion. Identify specific red flags that trigger manual override. ## Context **Decision-makers:** a specific decision makers **Operating constraints:** a specific operating constraints Common failure patterns include delays, gut-feel disagreements, inconsistent calls, endless re-litigation of the same choice, and stakeholder arguments without criteria. ## Output Deliver a one-page framework in five sections: **Decision Criteria** — List exactly 3-5 criteria. For each, provide a one-sentence definition and a measurable threshold (pass/fail or numeric score). No subjective terms unless precisely defined in observable terms. **Decision Structure** — Present as either a decision tree with sequential gates (for binary yes/no decisions) or a scoring card with weights (for prioritizing multiple options). Explicitly state why you selected this structure based on the decision type. **Decision Zones** — Define exact, measurable boundaries requiring zero interpretation: Auto-Approve (specific conditions, no meeting needed), Auto-Reject (specific conditions, no meeting needed), and Requires Discussion (narrow band of genuine judgment calls). **Override Triggers** — List 3-4 concrete red flags that pause the framework and trigger manual review even when the heuristic says proceed. Use specific warning signals like "Client is in regulated industry we've never served" or "Budget exceeds 3× our typical project size," not vague triggers like "Use judgment if situation feels unusual." **Usage Example** — Walk through one realistic scenario step-by-step: state the initial question, apply each criterion, reach a decision zone, and state the final decision and time saved. Use bullet points and clear headers for maximum scanability. Commit to specific thresholds—no hedge language like "you might consider," "it depends," or "generally speaking." Prioritize brutal simplicity over comprehensive coverage. Must be printable on one page and simple enough to memorize. Deliver the tool itself, not an essay about decision-making philosophy.