evaluating-trade-offs

Evaluating Trade-offs

Scope

Covers

• Turning an ambiguous “pros/cons” debate into a decision-ready trade-off evaluation
• Comparing options using all-in cost (not just dollars) and explicit opportunity cost
• Using order-of-magnitude estimates (ranges + confidence) instead of false precision
• Stress-testing decisions with thought experiments (pre-mortems, reversibility, “worse first” dips)
• Avoiding sunk-cost traps with a clean stop/continue decision rule

When to use

• “Help me evaluate this trade-off and recommend a path.”
• “Create a pros/cons that actually leads to a decision.”
• “Compare options with cost/impact ranges and key assumptions.”
• “We’re debating speed vs quality—what’s the right trade and how do we manage the dip?”
• “Should we keep investing in this project, or stop? (Sunk cost question.)”

When NOT to use

• You need to clarify what problem you’re solving (use problem-definition).
• You need a full cross-functional decision process with stakeholder alignment and governance (use running-decision-processes).
• You’re prioritizing across many initiatives (use prioritizing-roadmap).
• You’re evaluating a specific technology, vendor, or build-vs-buy for a tool/platform (use evaluating-new-technology).
• You’re cutting scope to hit a date/timebox (use scoping-cutting).
• You need to model feedback loops, second-order effects, or system dynamics (use systems-thinking).
• The decision is personal/legal/HR/financial advice (escalate to qualified humans).

Inputs

Minimum required

• The trade-off / decision statement (one sentence) and a decision date (or “by EOW”)
• 2–4 options you’re choosing between (include “do nothing” if plausible)
• Constraints + non-negotiables (budget, headcount, policy, deadlines, customer commitments)
• What “good” means (success metrics + guardrails) and the time horizon you care about
• What you already know (evidence) + biggest unknowns (assumptions that drive the choice)