Decision Frameworks Library — Starter Index

Decision Frameworks Library — Starter Index

Use this concise library to find a practical mental model or framework that fits the decision you face. Each entry includes a short description, when it helps, core strengths, common weaknesses, and a short example to make applying it straightforward. The goal is clearer, faster, and more reviewable choices—not replacing context, expertise, or ethical judgment.

How to use this index

• Define the decision and the most important constraint or outcome you care about.
• Pick one or two frameworks that match the decision type (tradeoff, prioritization, uncertainty, root cause, etc.).
• Capture assumptions, key data, and a short rationale so the decision can be reviewed and learned from later.

Included frameworks (starter)

• Cost of Delay — Estimates the economic impact of postponing a project or feature.
  • When to use: Prioritizing projects or features with time-sensitive value.
  • Strengths: Focuses attention on timing; helps compare time-sensitive options.
  • Weaknesses: Requires rough value and time estimates; sensitive to assumptions.
  • Example: Choose between two product features when one unlocks revenue sooner.
• RICE prioritization — Scores ideas by Reach, Impact, Confidence, and Effort.
  • When to use: Prioritizing features, experiments, or initiatives across teams.
  • Strengths: Simple, repeatable, balances impact and effort, surfaces confidence explicitly.
  • Weaknesses: Numeric scores can create false precision; input estimates may be biased.
  • Example: Ranking a backlog to decide which experiments to run this quarter.
• Decision tree (make vs buy) — Structured branching of outcomes, costs, and probabilities.
  • When to use: Binary or staged operational/strategic choices with measurable outcomes.
  • Strengths: Makes assumptions explicit; supports expected-value thinking and scenario comparison.
  • Weaknesses: Can become complex; probability estimates are often uncertain.
  • Example: Choosing between building a capability in-house or outsourcing it based on cost, lead time, and risk.
• First principles — Break a problem into fundamental truths and reassemble solutions.
  • When to use: Complex or novel problems where assumptions may be outdated.
  • Strengths: Encourages creative, non-incremental solutions; avoids inherited assumptions.
  • Weaknesses: Time-consuming; may miss practical constraints or institutional knowledge.
  • Example: Reimagining a service workflow by mapping work at its most basic steps rather than copying current practice.
• Weighted scoring / Multi-criteria decision analysis — Rate options against prioritized criteria with weights.
  • When to use: Comparing options across multiple, incommensurate criteria (cost, quality, speed, risk).
  • Strengths: Transparent trade-offs; easy to adapt criteria and weights to context.
  • Weaknesses: Weights introduce subjectivity; results depend on chosen scales.
  • Example: Vendor selection where price, service level, and compliance matter.
• Eisenhower (Urgent–Important) matrix — Categorize tasks by urgency and importance to prioritize action.
  • When to use: Day-to-day task triage and workload decisions.
  • Strengths: Quick, practical; helps avoid firefighting and focus on important work.
  • Weaknesses: Subjective classification; not designed for complex tradeoffs.
  • Example: Deciding whether a reported incident requires immediate resources or scheduled attention.
• OODA loop (Observe–Orient–Decide–Act) — Fast cycles used to adapt under uncertainty.
  • When to use: Rapidly changing situations where speed and learning matter.
  • Strengths: Emphasizes iteration and sensing; supports adaptive decision-making.
  • Weaknesses: Can favor speed over deep analysis; needs good situational awareness.
  • Example: Adjusting production scheduling during a supply disruption.
• Pre-mortem — Assume a decision failed and brainstorm causes to surface risks and mitigations.
  • When to use: High-impact initiatives where blind spots would be costly.
  • Strengths: Reveals hidden risks; encourages proactive mitigation planning.
  • Weaknesses: May bias toward risk aversion if used alone.
  • Example: Before launching a new customer service process, the team lists possible failure modes and safeguards.
• Five Whys — Iteratively ask why to find root causes of a problem.
  • When to use: Diagnosing operational failures or recurring issues.
  • Strengths: Simple, fast way to explore root causes; engages teams in problem solving.
  • Weaknesses: Can stop at superficial answers; facilitator skill matters.
  • Example: Investigating why a shipment was delayed to prevent recurrence.
• Decision journal — Record decisions, assumptions, expected outcomes, and later review actual results.
  • When to use: Any recurring or consequential decisions where organizational learning is desired.
  • Strengths: Builds institutional memory and reduces overconfidence over time.
  • Weaknesses: Requires discipline and a culture that reviews past decisions honestly.
  • Example: Logging hiring decisions with rationale to compare candidate assumptions versus outcomes.

Safety notes: Use frameworks as tools, not as substitutes for judgement. Combine models, call out uncertain assumptions, and avoid numerical precision when inputs are weak. Capture a short rationale so choices can be reviewed and improved over time.