tradeoff-analysis

Topics in the source

• Tradeoff Analysis
• When to use
• Before you start
• Steps
• 1. Options
• 2. Must-haves
• 3. Criteria and weights
• 4. Score

Choose among a small set of real options with the criteria, weights and evidence in plain view. A weighted decision matrix with a sensitivity check and a reversibility check. Picking a library, vendor, architecture, plan, hire, design or build-vs-buy. "A or B?", "compare these", "which should we pick", "is it worth it". A decision the user must defend to others. Skip: generating options from scratch (explore first, then come here), reviewing one plan for flaws, or ranking a long backlog. 1. State in one block: Decision (one sentence), Deadline or cost of delay, and Pass (Options, Must-haves, Criteria, Score, Sensitivity, Reversibility, Recommendation). 2. Gather first. Read docs, benchmarks, pricing, the codebase and constraints before scoring. Every score needs a one-line basis; unsupported scores are marked [ESTIMATED]. Ask up to 3 questions only for goals and constraints tools cannot answer. 3. Light path. Small ask: 2-3 options, 3 criteria, one-line reasons, a one-sentence sensitivity check. 2-5 genuinely different options, including do nothing or keep current when it is real. Hard constraints (budget cap, compliance, deadline). An option that fails one is out; do not score it.

This is an excerpt. Refer to the complete source and its current requirements.