kill-criteria-exit-ramps

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Kill Criteria & Exit Ramps

Kill Criteria 与 Exit Ramps

Purpose

用途

Kill criteria are pre-defined, objective conditions that trigger stopping a project, product, or initiative. Exit ramps are specific decision points where you evaluate whether to continue, pivot, or kill. This skill helps avoid sunk cost fallacy and opportunity cost by establishing discipline around quitting.

Use this skill when:

Starting new projects: Define kill criteria upfront before emotional/financial investment
Evaluating ongoing initiatives: Decide whether to continue, pivot, or stop
Avoiding sunk cost trap: "We've invested too much to quit now"
Portfolio management: Which projects to kill to free resources for winners
Setting go/no-go gates: Milestone-based decision points
Managing risk: Exit before losses escalate

The hardest decision is often knowing when to quit. Kill criteria remove emotion and politics from stopping decisions.

Kill Criteria是预先设定的、触发项目、产品或计划终止的客观条件。Exit Ramps是用于评估是否继续、pivot或终止的特定决策节点。本技能通过建立严谨的终止决策机制，帮助规避沉没成本谬误与机会成本。

使用本技能的场景：

启动新项目时：在投入情感/资金前预先定义Kill Criteria
评估进行中的计划时：决定是否继续、pivot或终止
避免沉没成本陷阱时：比如出现“我们已经投入太多，现在不能终止”的情况
项目组合管理时：终止哪些项目以将资源释放给更有潜力的项目
设置Go/No-Go关卡时：基于里程碑的决策节点
风险管理时：在损失扩大前退出

最难的决策往往是知道何时终止。Kill Criteria能让终止决策摆脱情感与政治因素的干扰。

Common Patterns

常见模式

Pattern 1: Upfront Kill Criteria (Before Launch)

模式1：预先设定Kill Criteria（启动前）

When: Starting new project, experiment, or product

Process: (1) Define success metrics ("10% conversion"), (2) Set time horizon ("6 months"), (3) Establish kill criteria ("If <5% after 6 months, kill"), (4) Assign decision rights (specific person), (5) Document formally (signed PRD)

Example: New feature — Success: 20% adoption in 3 months, Kill: <10% adoption, Decision: Product VP makes call

适用场景：启动新项目、实验或产品时

流程：(1) 定义成功指标（如“10%转化率”），(2) 设置时间范围（如“6个月”），(3) 确立Kill Criteria（如“6个月后转化率<5%则终止”），(4) 明确决策权限（指定具体负责人），(5) 正式记录（签署的PRD）

示例：新功能 — 成功标准：3个月内实现20%的采用率；Kill Criteria：采用率<10%；决策人：产品副总裁

Pattern 2: Go/No-Go Gates (Milestone-Based)

模式2：Go/No-Go关卡（基于里程碑）

When: Multi-stage projects with increasing investment

Structure: Stage 1 (cheap, concept) → Go/No-Go → Stage 2 (moderate, MVP) → Go/No-Go → Stage 3 (expensive, launch) → Go/No-Go

Example: Gate 1 (4wk, $10k): 15+ customer interviews show interest → GO. Gate 2 (3mo, $50k): 40% weekly active (got 25%) → NO-GO, kill

Benefit: Small investments first, kill before expensive stages

适用场景：分阶段且投入逐步增加的项目

结构：阶段1（低成本，概念验证）→ Go/No-Go决策 → 阶段2（中等成本，MVP）→ Go/No-Go决策 → 阶段3（高成本，正式发布）→ Go/No-Go决策

示例：关卡1（4周，1万美元）：15+客户访谈显示有兴趣 → 继续（GO）。关卡2（3个月，5万美元）：周活跃率达40%（实际仅25%）→ 终止（NO-GO）

优势：先进行小额投入，在进入高成本阶段前终止项目

Pattern 3: Trigger-Based Exit Ramps

模式3：触发式Exit Ramps

When: Ongoing projects with uncertain outcomes

Common triggers: Time-based ("not profitable by Month 18"), Metric-based ("churn >8% for 2 months"), Market-based ("competitor launches"), Resource-based ("budget overrun >30%"), Opportunity-based ("better option emerges")

Example: SaaS — Trigger 1: MRR growth <10%/mo for 3 months → Evaluate. Trigger 2: CAC payback >24mo → Evaluate. Trigger 3: Competitor raises >$50M → Evaluate

Note: Triggers prompt evaluation, not automatic kill

适用场景：结果不确定的进行中项目

常见触发条件：时间触发（“18个月内未盈利”）、指标触发（“连续2个月流失率>8%”）、市场触发（“竞争对手发布竞品”）、资源触发（“预算超支>30%”）、机会触发（“出现更优选择”）

示例：SaaS产品 — 触发条件1：连续3个月MRR增长率<10% → 启动评估；触发条件2：CAC回收期>24个月 → 启动评估；触发条件3：竞争对手融资超过5000万美元 → 启动评估

注意：触发条件仅提示启动评估，而非自动终止

Pattern 4: Pivot vs. Kill Decision

模式4：Pivot vs. 终止决策

When: Project isn't working as planned — should you pivot or kill?

Framework:

Pivot if:

Core insight is valid but execution is wrong
Customer pain is real, solution is wrong
Market exists, go-to-market is wrong
Learning rate is high (discovering new insights rapidly)
Resource burn is sustainable (not desperation mode)

Kill if:

No customer pain (nice-to-have, not must-have)
Market too small (can't sustain business)
Burn rate too high relative to progress
Team doesn't believe in vision
Better opportunities available (opportunity cost)
Regulatory/legal blockers

Example: Mobile app with low engagement

Situation: Launched fitness app, 10k downloads, 5% weekly active (target was 40%)
Pivot option: Interviews reveal users want meal tracking not workout tracking → Pivot to nutrition app
Kill option: Users don't care about fitness tracking at all, market saturated → Kill, reallocate team

Decision: Pivot if hypothesis valid but execution wrong. Kill if hypothesis invalid.

适用场景：项目未按计划推进时 — 应该pivot还是终止？

决策框架:

选择Pivot的情况:

核心洞察有效但执行有误
客户痛点真实但解决方案错误
市场存在但上市策略有误
学习效率高（快速发现新洞察）
资源消耗可持续（非紧急止损状态）

选择终止的情况:

无真实客户痛点（只是锦上添花，而非必需）
市场规模过小（无法支撑业务）
资源消耗速率与进展不匹配（消耗过高）
团队不认同愿景
存在更优机会（机会成本）
存在监管/法律障碍

示例：低活跃度的移动应用

场景：推出健身应用，下载量1万，周活跃率5%（目标为40%）
Pivot选项：用户访谈显示用户需要的是饮食追踪而非健身追踪 → 转型为营养应用
终止选项：用户根本不关心健身追踪，市场已饱和 → 终止项目，重新分配团队

决策逻辑：如果假设成立但执行有误则Pivot；如果假设不成立则终止。

Pattern 5: Portfolio Kill Criteria (Multiple Projects)

模式5：项目组合Kill Criteria（多项目）

When: Managing portfolio of projects, need to kill some to focus

Process:

Rank by expected value: ROI, strategic fit, resource efficiency
Define minimum threshold: "Top 70% of portfolio gets resources"
Kill bottom 30%: Projects below threshold, regardless of sunk cost
Reallocate resources: Winners get resources from killed projects

Example: Company with 10 projects, capacity for 7

Rank by: (Expected Revenue × Probability of Success) / Resource Cost
Kill: Projects ranked #8, #9, #10 (even if they're "almost done")
Reallocate: Engineers from killed projects to top 3

Principle: Opportunity cost matters more than sunk cost. "Almost done" doesn't justify continuing if better alternatives exist.

适用场景：管理多个项目组合，需要终止部分项目以聚焦核心

流程:

按预期价值排序：ROI、战略契合度、资源效率
设定最低阈值：“项目组合中排名前70%的项目获得资源”
终止后30%的项目：无论已投入多少，终止低于阈值的项目
重新分配资源：将终止项目的资源调配给更有潜力的项目

示例：公司有10个项目，仅能支撑7个

排序依据：（预期收入 × 成功概率）/ 资源成本
终止对象：排名第8、9、10的项目（即使它们“接近完成”）
资源调配：将终止项目的工程师调配给排名前3的项目

原则：机会成本比沉没成本更重要。如果存在更优选择，“接近完成”不能成为继续的理由。

Pattern 6: Sunk Cost Trap Avoidance

模式6：避免沉没成本陷阱

When: Team resists killing project due to past investment

Technique: Pre-mortem inversion

Ask: "If we were starting today with zero investment, would we start this project?"
If answer is "No" → Kill (sunk costs are irrelevant)
If answer is "Yes, but differently" → Pivot
If answer is "Yes, exactly as-is" → Continue

Example: Failed enterprise sales push

Situation: 18 months, $2M spent, 2 customers (need 50 for viability)
Inversion: "If starting today, would we pursue enterprise sales?" → "No, we'd focus on self-serve SMB"
Decision: Kill enterprise sales, pivot to SMB (sunk $2M is irrelevant)

Trap: "We've invested so much, we can't quit now" → This is sunk cost fallacy Escape: Only future costs and benefits matter. Past is gone.

适用场景：团队因过去的投入而抗拒终止项目时

技巧：事前反向分析（Pre-mortem inversion）

提问：“如果我们今天从零开始，是否会启动这个项目？”
如果答案是“否” → 终止（沉没成本无关紧要）
如果答案是“是，但方式不同” → Pivot
如果答案是“是，完全按当前方式” → 继续

示例：失败的企业级销售推进

场景：投入18个月、200万美元，仅获得2个客户（需要50个才能维持业务）
反向分析：“如果今天从零开始，我们会推进企业级销售吗？” → “不会，我们会聚焦自助式SMB客户”
决策：终止企业级销售，转型为SMB客户（已投入的200万美元无关紧要）

陷阱：“我们已经投入太多，现在不能终止” → 这是沉没成本谬误 应对方法：只有未来的成本和收益才重要。过去的投入已无法挽回。

Workflow

工作流程

Use this structured approach when defining or applying kill criteria:

□ Step 1: Define success metrics and time horizon
□ Step 2: Establish objective kill criteria
□ Step 3: Assign decision rights and governance
□ Step 4: Set milestone gates or trigger points
□ Step 5: Document formally (signed agreement)
□ Step 6: Monitor metrics regularly
□ Step 7: Evaluate at gates/triggers
□ Step 8: Execute kill decision (if triggered)

Step 1: Define success metrics and time horizon (details) Specify quantifiable success criteria (e.g., "20% conversion") and evaluation period (e.g., "6 months post-launch").

Step 2: Establish objective kill criteria (details) Set numeric thresholds that trigger stop decision (e.g., "If <10% conversion after 6 months"). Make criteria objective, not subjective.

Step 3: Assign decision rights and governance (details) Name specific person who makes kill decision. Define escalation process. Avoid "team consensus" (leads to paralysis).

Step 4: Set milestone gates or trigger points (details) For multi-stage projects: define go/no-go gates. For ongoing projects: define triggers that prompt evaluation.

Step 5: Document formally (details) Write kill criteria in PRD, project charter, or investment memo. Get stakeholders to sign/approve before launch (prevents moving goalposts).

Step 6: Monitor metrics regularly (details) Track metrics weekly/monthly. Dashboard with kill criteria thresholds clearly marked. Automate alerts when approaching thresholds.

Step 7: Evaluate at gates/triggers (details) When gate or trigger hit, conduct formal evaluation. Use pre-mortem inversion: "Would we start this today?" Decide: continue, pivot, or kill.

Step 8: Execute kill decision (details) If kill triggered: communicate decision, wind down project, reallocate resources, conduct postmortem. Execute quickly (avoid zombie projects).

定义或应用Kill Criteria时，请遵循以下结构化流程：

□ Step 1: Define success metrics and time horizon
□ Step 2: Establish objective kill criteria
□ Step 3: Assign decision rights and governance
□ Step 4: Set milestone gates or trigger points
□ Step 5: Document formally (signed PRD)
□ Step 6: Monitor metrics regularly
□ Step 7: Evaluate at gates/triggers
□ Step 8: Execute kill decision (if triggered)

步骤1：定义成功指标与时间范围 (详情) 明确可量化的成功标准（如“20%转化率”）与评估周期（如“发布后6个月”）。

步骤2：确立客观的Kill Criteria (详情) 设定触发终止决策的数值阈值（如“6个月后转化率<10%”）。确保标准客观，而非主观判断。

步骤3：明确决策权限与治理规则 (详情) 指定负责终止决策的具体人员。定义升级流程。避免“团队共识”（这会导致决策瘫痪）。

步骤4：设置里程碑关卡或触发点 (详情) 对于分阶段项目：定义Go/No-Go关卡。对于进行中项目：定义触发评估的条件。

步骤5：正式记录 (详情) 将Kill Criteria写入PRD、项目章程或投资备忘录。在启动前获得相关方的签署/批准（防止后续随意更改标准）。

步骤6：定期监控指标 (详情) 每周/每月跟踪指标。使用仪表板清晰标记Kill Criteria的阈值。当接近阈值时自动发送警报。

步骤7：在关卡/触发点进行评估 (详情) 当到达关卡或触发条件时，开展正式评估。使用事前反向分析：“我们今天会启动这个项目吗？” 决定：继续、pivot或终止。

步骤8：执行终止决策 (详情) 如果触发终止：传达决策、逐步结束项目、重新分配资源、开展事后复盘。快速执行（避免“僵尸项目”）。

Critical Guardrails

关键准则

1. Set Kill Criteria Before Launch (Not After)

1. 在启动前设定Kill Criteria（而非启动后）

Danger: Defining kill criteria after project starts leads to moving goalposts

Guardrail: Write kill criteria in initial project document, before emotional/financial investment. Get stakeholder sign-off.

Red flag: "We'll figure out when to stop as we go" — this leads to sunk cost trap

风险：项目启动后再定义Kill Criteria会导致标准被随意更改

准则：在投入情感/资金前，将Kill Criteria写入初始项目文档，并获得相关方的签署同意。

危险信号：“我们边做边想何时终止” — 这会导致沉没成本陷阱

2. Make Criteria Objective (Not Subjective)

2. 确保标准客观（而非主观）

Danger: Subjective criteria ("team feels it's not working") are easy to ignore

Guardrail: Use quantifiable metrics (numbers, dates, milestones). "5% conversion" not "low adoption". "6 months" not "reasonable time".

Test: Could two people independently evaluate criteria and reach same conclusion? If not, too subjective.

风险：主观标准（如“团队感觉项目进展不佳”）容易被忽视

准则：使用可量化的指标（数字、日期、里程碑）。例如“5%转化率”而非“采用率低”；“6个月”而非“合理时间”。

检验方法：两个独立的人评估标准后能否得出相同结论？如果不能，则标准过于主观。

3. Assign Clear Decision Rights

3. 明确决策权限

Danger: "Team decides" or "we'll discuss" leads to paralysis (everyone has sunk cost)

Guardrail: Name specific person who makes kill decision. Define what data they need. Escalation path for overrides.

Example: "Product VP makes kill decision based on 6-month metrics. Can be overridden only by CEO with written justification."

风险：“团队决定”或“我们再讨论”会导致决策瘫痪（每个人都有沉没成本）

准则：指定负责终止决策的具体人员。定义他们所需的数据。明确 override 的升级路径。

示例：“产品副总裁基于6个月的指标做出终止决策。仅CEO可通过书面说明进行 override。”

4. Don't Move the Goalposts

4. 不要随意更改标准

Danger: When kill criteria approached, team lowers bar or extends timeline

Guardrail: Kill criteria are fixed at launch. Changes require formal process (written justification, senior approval, new document).

Red flag: "Let's give it another 3 months" when 6-month criteria not met

风险：当接近Kill Criteria时，团队会降低标准或延长时间

准则：Kill Criteria在启动时即固定。更改标准需要正式流程（书面说明、高层批准、更新文档）。

危险信号：“6个月的标准未达成，再给3个月时间”

5. Sunk Costs Are Irrelevant

5. 沉没成本无关紧要

Danger: "We've invested $2M, can't stop now" — sunk cost fallacy

Guardrail: Use pre-mortem inversion: "If starting today with $0 invested, would we do this?" Only future matters.

Principle: Past costs are gone. Only question: "Is future investment better here or elsewhere?"

风险：“我们已经投入200万美元，不能终止” — 这是沉没成本谬误

准则：使用事前反向分析：“如果今天从零开始投入0美元，我们会做这个项目吗？” 只有未来才重要。

原则：过去的投入已无法挽回。唯一的问题是：“未来的投资投在这里还是其他地方更好？”

6. Kill Quickly (Avoid Zombie Projects)

6. 快速终止（避免僵尸项目）

Danger: Projects that should be killed linger, draining resources ("zombie projects")

Guardrail: Kill decision → immediate wind-down. Announce within 1 week, reallocate team within 1 month.

Red flag: Project in "wind-down" for >3 months — this is zombie mode, not killing

风险：应终止的项目持续存在，消耗资源（“僵尸项目”）

准则：做出终止决策后立即启动收尾。1周内宣布决策，1个月内重新分配团队。

危险信号：项目处于“收尾”状态超过3个月 — 这是僵尸模式，而非真正的终止

7. Opportunity Cost > Sunk Cost

7. 机会成本 > 沉没成本

Danger: Continuing project because "almost done" even if better opportunities exist

Guardrail: Portfolio thinking. Ask: "Is this the best use of these resources?" If not, kill even if 90% done.

Principle: Opportunity cost of not pursuing better option often exceeds benefit of finishing current project

风险：因为“接近完成”而继续项目，即使存在更优机会

准则：用项目组合思维思考。提问：“这是这些资源的最佳用途吗？” 如果不是，即使完成90%也要终止。

原则：不追求更优机会的机会成本往往超过完成当前项目的收益

8. Postmortem, Don't Blame

8. 事后复盘，不追责

Danger: Kill decisions seen as "failure", teams avoid them

Guardrail: Normalize killing projects. Celebrate disciplined stopping. Postmortem focuses on learning, not blame.

Culture: "We killed 3 projects this quarter" = good (freed resources for winners), not bad (failures)

风险：终止决策被视为“失败”，团队会避免做出此类决策

准则：将终止项目正常化。为严谨的终止决策庆祝。事后复盘聚焦于学习，而非追责。

文化：“本季度我们终止了3个项目” = 好事（为更优项目释放了资源），而非坏事（失败）

Quick Reference

快速参考

Kill Criteria Checklist

Kill Criteria checklist

Go/No-Go Gate Template

Go/No-Go关卡模板

Gate	Investment	Timeline	Success Criteria	Decision
Gate 1: Concept	$10k	4 weeks	15+ customer interviews showing strong interest	GO / NO-GO
Gate 2: MVP	$50k	3 months	40% weekly active users (50 beta users)	GO / NO-GO
Gate 3: Launch	$200k	6 months	10% conversion, <$100 CAC	GO / NO-GO

关卡	投入	时间线	成功标准	决策
关卡1：概念验证	1万美元	4周	15+客户访谈显示强烈兴趣	GO / NO-GO
关卡2：MVP	5万美元	3个月	40%周活跃用户（50个测试用户）	GO / NO-GO
关卡3：正式发布	20万美元	6个月	10%转化率，CAC<100美元	GO / NO-GO

Pivot vs. Kill Decision Framework

Pivot vs. 终止决策框架

Factor	Pivot	Kill
Customer pain	Real but solution wrong	No pain, nice-to-have
Market size	Large enough	Too small
Learning rate	High (new insights)	Low (stuck)
Burn rate	Sustainable	Too high
Team belief	Believes with changes	Doesn't believe
Opportunity cost	Pivot is best option	Better options exist

因素	Pivot	终止
客户痛点	真实但解决方案错误	无痛点，只是锦上添花
市场规模	足够大	过小
学习效率	高（不断发现新洞察）	低（陷入停滞）
资源消耗速率	可持续	过高
团队信念	调整后认同愿景	不认同愿景
机会成本	Pivot是最佳选择	存在更优机会

Resources

资源

Navigation to Resources

资源导航

Templates: Kill criteria document, go/no-go gate template, pivot/kill decision framework, wind-down plan
Methodology: Sunk cost psychology, portfolio management, decision rights frameworks, postmortem processes
Rubric: Evaluation criteria for kill criteria quality (10 criteria)

模板：Kill Criteria文档、Go/No-Go关卡模板、Pivot/终止决策框架、收尾计划
方法论：沉没成本心理学、项目组合管理、决策权限框架、事后复盘流程
评估标准：Kill Criteria质量的评估标准（10项）

Related Skills

Examples in Context

场景示例

Example 1: Startup Feature Kill

示例1：初创公司功能终止

Context: SaaS launched "Advanced Analytics", kill criteria: <15% adoption after 3 months

Result: 12% adoption → Killed feature, reallocated 2 engineers to core. Saved 6 months maintenance.

场景：SaaS公司推出“高级分析”功能，Kill Criteria：3个月后采用率<15%

结果：采用率12% → 终止该功能，将2名工程师重新分配到核心功能。节省了6个月的维护成本。

Example 2: Enterprise Sales Pivot

示例2：企业级销售转型

Context: B2B SaaS, pivot trigger: <10 customers by Month 12

Result: 7 customers → Pivoted to self-serve SMB. Hit 200 SMB customers in 6 months, 4× faster growth.

场景：B2B SaaS公司，转型触发条件：12个月内客户数<10

结果：客户数7 → 转型为自助式SMB客户。6个月内获得200个SMB客户，增长速度提升4倍。

Example 3: R&D Portfolio Kill

示例3：研发项目组合终止

Context: 8 R&D projects, capacity for 5. Ranked by EV/Cost: A(3.5), B(2.8), C(2.5), D(2.1), E(1.8), F(1.5), G(1.2), H(0.9)

Decision: Killed F, G, H despite F being "80% done". Top 3 projects shipped 4 months earlier.

场景：8个研发项目，仅能支撑5个。按EV/成本排序：A(3.5), B(2.8), C(2.5), D(2.1), E(1.8), F(1.5), G(1.2), H(0.9)

决策：终止F、G、H项目，尽管F已完成80%。排名前3的项目提前4个月上线。