Back to Details

evaluating-trade-offs

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

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 (use 
    running-decision-processes
    ).
  • You’re prioritizing across many initiatives (use 
    prioritizing-roadmap
    ).
  • You’re cutting scope to hit a date/timebox (use 
    scoping-cutting
    ).
  • The decision is personal/legal/HR/financial advice (escalate to qualified humans).
涵盖内容
  • 将模糊的“优缺点讨论”转化为可直接用于决策的权衡评估方案
  • 结合全成本（不仅是资金）和明确的机会成本对比不同选项
  • 使用数量级估算（范围+置信度）替代虚假的精确值
  • 通过思维实验（事前验尸、可逆性分析、“最坏情况优先”推演）压力测试决策
  • 借助清晰的终止/继续决策规则规避沉没成本陷阱
适用场景
  • “帮我评估这个权衡方案并推荐行动路径。”
  • “创建一份能真正导向决策的优缺点分析。”
  • “结合成本/影响范围和关键假设对比不同选项。”
  • “我们在争论速度与质量的优先级——正确的权衡是什么？如何应对短期阵痛？”
  • “我们应该继续投入这个项目还是止损？（沉没成本相关问题）”
不适用场景
  • 你需要明确要解决的问题（请使用
    problem-definition
    工具）。
  • 你需要完整的跨职能决策流程（请使用
    running-decision-processes
    工具）。
  • 你需要在多个举措中排序优先级（请使用
    prioritizing-roadmap
    工具）。
  • 你需要削减范围以满足截止日期（请使用
    scoping-cutting
    工具）。
  • 该决策涉及个人/法律/HR/财务建议（请咨询专业人士）。

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)
Missing-info strategy
  • Ask up to 5 questions from references/INTAKE.md (3–5 at a time).
  • If inputs are unavailable, proceed with explicit assumptions and label unknowns that would change the recommendation.
最低必填信息
  • 权衡/决策陈述（一句话）和决策截止日期（或“本周末前”）
  • 2-4个待选选项（若合理，需包含“不采取任何行动”选项）
  • 约束条件与不可协商项（预算、人员编制、政策、截止日期、客户承诺）
  • 成功的定义（成功指标+管控边界）及你关注的时间范围
  • 已知信息（证据）+最大未知项（影响决策的关键假设）
缺失信息处理策略
  • 可从references/INTAKE.md中提出最多5个问题（每次3-5个）。
  • 若无法获取输入信息，基于明确假设推进，并标注会改变建议的未知项。

Outputs (deliverables)

输出成果（交付物）

Produce a Trade-off Evaluation Pack in Markdown (in-chat; or as files if requested) in this order:
  1. Trade-off brief (decision, why now, options, constraints, horizon, stakeholders)
  2. Options + criteria matrix (criteria + weights/guardrails; option notes)
  3. All-in cost + opportunity cost table (money, people/time, eng effort, complexity, displacement)
  4. Impact ranges (order-of-magnitude) (upside/downside ranges, confidence, key assumptions)
  5. Worse-first + mitigation plan (expected dip, leading indicators, mitigations, comms)
  6. Recommendation + stop/continue triggers (decision, rationale, review date, kill/continue criteria)
  7. Risks / Open questions / Next steps (always included)
Templates: references/TEMPLATES.md
Expanded guidance: references/WORKFLOW.md
生成Markdown格式的权衡评估包（可直接在对话中展示；若有需求也可生成文件），内容顺序如下：
  1. 权衡简报（决策内容、当前决策的必要性、选项、约束条件、时间范围、利益相关方）
  2. 选项+标准矩阵（评估标准+权重/管控边界；选项备注）
  3. 全成本+机会成本表（资金、人力时间、研发投入、复杂度、资源挤占情况）
  4. 影响范围（数量级）（收益/损失范围、置信度、关键假设）
  5. 最坏情况优先+缓解计划（预期短期阵痛、领先指标、缓解措施、沟通方案）
  6. 建议+终止/继续触发条件（决策结论、理由、复盘日期、终止/继续标准）
  7. 风险/待解决问题/下一步行动（必须包含）
模板参考：references/TEMPLATES.md
扩展指引：references/WORKFLOW.md

Workflow (7 steps)

工作流程（7个步骤）

1) Frame the trade-off (make it decidable)

1) 明确权衡框架（使决策可落地）

  • Inputs: User request; references/INTAKE.md.
  • Actions: Write the decision in one sentence (“We are choosing X vs Y by DATE to achieve GOAL”). List constraints/non-negotiables. Confirm the decision owner and who must live with the outcome.
  • Outputs: Trade-off brief (decision, why now, constraints, stakeholders).
  • Checks: You can answer: “What exactly are we deciding, by when, and for what outcome?”
  • 输入：用户需求；references/INTAKE.md
  • 行动：用一句话明确决策内容（“我们需在[日期]前在X与Y中选择，以实现[目标]”）。列出约束条件与不可协商项。确认决策负责人及需承担决策结果的相关方。
  • 输出：权衡简报（决策内容、当前决策的必要性、约束条件、利益相关方）
  • 校验：能够清晰回答“我们到底要做什么决策？截止日期？要达成什么目标？”

2) Define what you’re optimizing (criteria + horizon)

2) 定义优化方向（标准+时间范围）

  • Inputs: Goals, metrics, guardrails; time horizon.
  • Actions: Pick 4–8 criteria (include at least one guardrail like trust/reliability/cost). Decide weights only if it changes the decision. Explicitly name what you’re not optimizing for.
  • Outputs: Options + criteria matrix (criteria definitions + weights/guardrails).
  • Checks: Criteria reflect real trade-offs (not “everything is important”); horizon is explicit (e.g., 90 days vs 2 years).
  • 输入：目标、指标、管控边界；时间范围
  • 行动：选取4-8个评估标准（至少包含一个如信任/可靠性/成本的管控边界）。仅当权重会改变决策时才设置权重。明确标注不进行优化的方向。
  • 输出：选项+标准矩阵（标准定义+权重/管控边界）
  • 校验：评估标准反映真实的权衡关系（而非“所有事项都重要”）；时间范围明确（如90天vs2年）

3) Build the all-in cost + opportunity cost view

3) 构建全成本+机会成本视图

  • Inputs: Team capacity, budget, dependencies, timelines.
  • Actions: Estimate all-in cost (cash, headcount time, eng effort, maintenance, coordination). List the opportunity cost: what won’t be done if you choose each option.
  • Outputs: All-in cost + opportunity cost table.
  • Checks: Costs include “hidden” items (maintenance/on-call, tooling, cross-team coordination, switching costs).
  • 输入：团队产能、预算、依赖关系、时间线
  • 行动：估算全成本（资金、人力时间、研发投入、维护成本、协调成本）。列出机会成本：选择每个选项后无法开展的工作。
  • 输出：全成本+机会成本表
  • 校验：成本包含“隐性”项目（维护/随叫随到支持、工具成本、跨团队协调成本、切换成本）

4) Estimate impact with ranges (avoid false precision)

4) 用范围估算影响（避免虚假精确）

  • Inputs: Any baseline numbers; evidence; assumptions.
  • Actions: For each option, estimate upside/downside as ranges and note confidence. Prefer order-of-magnitude comparisons (10× vs 1.1×). Identify the 2–3 assumptions that drive the model.
  • Outputs: Impact ranges table (range, confidence, key assumptions).
  • Checks: No fake decimals; uncertainty is explicit; the decision is driven by a few key drivers you can name.
  • 输入：基准数据；证据；假设
  • 行动：针对每个选项，以范围形式估算收益/损失并标注置信度。优先使用数量级对比（如10倍vs1.1倍）。识别驱动模型的2-3个关键假设。
  • 输出：影响范围表（范围、置信度、关键假设）
  • 校验：无虚假小数；不确定性明确；决策由少数可明确的关键驱动因素决定

5) Run “thought experiments” (think more, build less)

5) 开展“思维实验”（多思考，少投入）

  • Inputs: Options, assumptions, risks.
  • Actions: Do a pre-mortem for the top 1–2 options (“It failed—why?”). Identify the cheapest evidence to de-risk the biggest assumption (data pull, customer calls, small prototype, timeboxed spike). Decide if this should be a thought experiment only (no build) vs a real experiment.
  • Outputs: Assumption list + minimal validation plan (if needed).
  • Checks: Proposed tests are the smallest that could change your mind; you’re not shipping an “obvious loser” experiment.
  • 输入：选项、假设、风险
  • 行动：对排名前1-2的选项进行事前验尸（“如果失败了，原因是什么？”）。确定验证最大假设的最低成本证据（数据提取、客户访谈、小型原型、限时探索）。判断这是否仅为思维实验（无需落地）还是真实实验。
  • 输出：假设列表+最小化验证计划（若需要）
  • 校验：提议的测试是能改变决策的最小成本方案；不会开展明显无意义的实验

6) Account for “worse first” + sunk costs

6) 考虑“先苦后甜”+沉没成本

  • Inputs: Expected short-term impacts; current investment/sunk costs.
  • Actions: Name any “worse-first” dip (short-term pain) and plan mitigations/leading indicators. Apply a sunk-cost reset: “If we weren’t already doing this, would we start today?” Define stop/continue triggers and a review date.
  • Outputs: Worse-first plan + stop/continue triggers.
  • Checks: The plan anticipates the dip; continuation logic ignores sunk costs and focuses on future ROI and strategic fit.
  • 输入：预期短期影响；当前投入/沉没成本
  • 行动：明确任何“先苦后甜”的短期阵痛，并制定缓解措施/领先指标。重置沉没成本视角：“如果我们尚未投入这个项目，现在是否会启动？”定义终止/继续触发条件及复盘日期。
  • 输出：短期阵痛应对计划+终止/继续触发条件
  • 校验：计划已提前预判短期阵痛；继续投入的逻辑忽略沉没成本，聚焦未来ROI和战略契合度

7) Recommend, commit, and quality-gate

7) 给出建议、确认承诺并通过质量校验

  • Inputs: All artifacts above.
  • Actions: Write the recommendation with rationale and explicit trade-offs (what you will stop doing). Add risks, open questions, and next steps with owners/dates. Run references/CHECKLISTS.md and score with references/RUBRIC.md.
  • Outputs: Final Trade-off Evaluation Pack.
  • Checks: A stakeholder can read this async and make (or support) the decision without re-litigating the debate.
  • 输入：上述所有成果
  • 行动：撰写包含理由和明确权衡的建议（说明将停止哪些工作）。添加风险、待解决问题及明确负责人/日期的下一步行动。使用references/CHECKLISTS.md检查，并通过references/RUBRIC.md评分。
  • 输出：最终权衡评估包
  • 校验：利益相关方可异步阅读并做出（或支持）决策，无需重新争论

Quality gate (required)

质量校验（必填）

  • Use references/CHECKLISTS.md and references/RUBRIC.md.
  • Always include: Risks, Open questions, Next steps.
  • 使用references/CHECKLISTS.md和references/RUBRIC.md。
  • 必须包含：风险、待解决问题、下一步行动

Examples

示例

Example 1 (resource allocation): “Should we invest in SEO or paid acquisition for the next 2 quarters? Build a trade-off pack with all-in cost, ROI speed, and assumptions.”
Expected: all-in cost vs alternatives, order-of-magnitude impact ranges, and a clear recommendation + review date.
Example 2 (speed vs quality): “We can ship v1 next week with rough edges or delay 3 weeks to ship ‘noteworthy’. Evaluate the trade-off and propose a worse-first mitigation plan if we ship now.”
Expected: explicit criteria/guardrails (trust/support load), dip plan, and stop/continue triggers if metrics degrade.
Boundary example: “Help me decide if I should leave my job.”
Response: this skill is for organizational/product leadership trade-offs; suggest a personal decision framework or coach instead.
示例1（资源分配）：“未来2个季度我们应该投入SEO还是付费获客？生成包含全成本、ROI速度及假设的权衡评估包。”
预期输出：全成本与替代方案对比、数量级影响范围、明确建议+复盘日期。
示例2（速度vs质量）：“我们可以下周推出有瑕疵的v1版本，或推迟3周推出‘优质’版本。评估该权衡，并提出若现在发布的短期阵痛缓解计划。”
预期输出：明确的标准/管控边界（信任/支持负载）、短期阵痛应对计划、若指标恶化时的终止/继续触发条件。
边界示例：“帮我决定是否辞职。”
回应：本工具适用于组织/产品管理层面的权衡决策；建议使用个人决策框架或咨询职业教练。