Back to Details

challenge

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

/em:challenge — Pre-Mortem Plan Analysis

/em:challenge — 事前验尸计划分析

Command: 
/em:challenge <plan>
Systematically finds weaknesses in any plan before reality does. Not to kill the plan — to make it survive contact with reality.
命令： 
/em:challenge <plan>
在计划落地前系统性地找出其漏洞。目的不是否决计划，而是让它能在现实中存活下来。

The Core Idea

核心理念

Most plans fail for predictable reasons. Not bad luck — bad assumptions. Overestimated demand. Underestimated complexity. Dependencies nobody questioned. Timing that made sense in a spreadsheet but not in the real world.
The pre-mortem technique: imagine it's 12 months from now and this plan failed spectacularly. Now work backwards. Why?
That's not pessimism. It's how you build something that doesn't collapse.
大多数计划失败的原因是可预见的，并非运气差，而是假设错误。比如高估需求、低估复杂度、依赖未经质疑的条件、在表格里看似合理但在现实中行不通的时间安排。
事前验尸法：假设12个月后这个计划彻底失败了，现在倒推——原因是什么？
这不是悲观，而是构建不会崩塌的事物的正确方式。

When to Run a Challenge

何时开展Challenge分析

  • Before committing significant resources to a plan
  • Before presenting to the board or investors
  • When you notice you're only hearing positive feedback about the plan
  • When the plan requires multiple external dependencies to align
  • When there's pressure to move fast and "figure it out later"
  • When you feel excited about the plan (excitement is a signal to scrutinize harder)
  • 在为计划投入大量资源之前
  • 在向董事会或投资者汇报之前
  • 当你发现关于计划的反馈全是正面的时候
  • 当计划需要多个外部条件同时满足的时候
  • 当面临“快速推进，之后再解决问题”的压力的时候
  • 当你对计划感到兴奋的时候（兴奋是需要更严格审查的信号）

The Challenge Framework

Challenge分析框架

Step 1: Extract Core Assumptions

步骤1：提取核心假设

Before you can test a plan, you need to surface everything it assumes to be true.
For each section of the plan, ask:
  • What has to be true for this to work?
  • What are we assuming about customer behavior?
  • What are we assuming about competitor response?
  • What are we assuming about our own execution capability?
  • What external factors does this depend on?
Common assumption categories:
  • Market assumptions — size, growth rate, customer willingness to pay, buying cycle
  • Execution assumptions — team capacity, velocity, no major hires needed
  • Customer assumptions — they have the problem, they know they have it, they'll pay to solve it
  • Competitive assumptions — incumbents won't respond, no new entrant, moat holds
  • Financial assumptions — burn rate, revenue timing, CAC, LTV ratios
  • Dependency assumptions — partner will deliver, API won't change, regulations won't shift
在测试计划之前，你需要明确计划所基于的所有假设。
针对计划的每个部分，问自己：
  • 要让这部分可行，哪些条件必须成立？
  • 我们对客户行为有哪些假设？
  • 我们对竞争对手的反应有哪些假设？
  • 我们对自身执行能力有哪些假设？
  • 这个部分依赖哪些外部因素？
常见假设类别：
  • 市场假设——规模、增长率、客户付费意愿、购买周期
  • 执行假设——团队能力、交付速度、无需核心招聘
  • 客户假设——他们存在该问题、自己知道有这个问题、愿意付费解决
  • 竞争假设——现有竞品不会回应、没有新进入者、护城河稳固
  • 财务假设——烧钱率、营收时机、CAC（客户获取成本）、LTV（客户生命周期价值）比率
  • 依赖假设——合作伙伴会交付、API不会变更、监管政策不会调整

Step 2: Rate Each Assumption

步骤2：为每个假设评分

For every assumption extracted, rate it on two dimensions:
Confidence level (how sure are you this is true):
  • High — verified with data, customer conversations, market research
  • Medium — directionally right but not validated
  • Low — plausible but untested
  • Unknown — we simply don't know
Impact if wrong (what happens if this assumption fails):
  • Critical — plan fails entirely
  • High — major delay or cost overrun
  • Medium — significant rework required
  • Low — manageable adjustment
针对每个提取出的假设，从两个维度评分：
置信度（你对该假设成立的确定程度）：
  • 高——已通过数据、客户访谈、市场调研验证
  • 中——方向正确但未验证
  • 低——看似合理但未测试
  • 未知——我们完全不清楚
错误影响（如果假设不成立会发生什么）：
  • 关键——计划彻底失败
  • 高——严重延迟或成本超支
  • 中——需要大量返工
  • 低——可进行调整解决

Step 3: Map Vulnerabilities

步骤3：绘制脆弱性图谱

The matrix of Low/Unknown confidence × Critical/High impact = your highest-risk assumptions.
Vulnerability = Low confidence + High impact
These are not problems to ignore. They're the bets you're making. The question is: are you making them consciously?
置信度为低/未知 × 影响为关键/高 = 最高风险假设。
脆弱性 = 低置信度 + 高影响
这些不是可以忽略的问题，而是你正在下的赌注。问题在于：你是有意识地在做这些赌注吗？

Step 4: Find the Dependency Chain

步骤4：梳理依赖链

Many plans fail not because any single assumption is wrong, but because multiple assumptions have to be right simultaneously.
Map the chain:
  • Does assumption B depend on assumption A being true first?
  • If the first thing goes wrong, how many downstream things break?
  • What's the critical path? What has zero slack?
许多计划失败不是因为单个假设错误，而是因为多个假设必须同时成立。
梳理依赖链：
  • 假设B是否依赖假设A先成立？
  • 如果第一个环节出错，会有多少下游环节断裂？
  • 关键路径是什么？哪些环节没有缓冲空间？

Step 5: Test the Reversibility

步骤5：测试可逆性

For each critical vulnerability: if this assumption turns out to be wrong at month 3, what do you do?
  • Can you pivot?
  • Can you cut scope?
  • Is money already spent?
  • Are commitments already made?
The less reversible, the more rigorously you need to validate before committing.
针对每个关键脆弱点：如果在第3个月发现这个假设不成立，你会怎么做？
  • 能否转型？
  • 能否削减范围？
  • 资金是否已经投入？
  • 是否已经做出承诺？
可逆性越低，在投入前就需要越严格地验证。

Output Format

输出格式

Challenge Report: [Plan Name]
CORE ASSUMPTIONS (extracted)
1. [Assumption] — Confidence: [H/M/L/?] — Impact if wrong: [Critical/High/Medium/Low]
2. ...

VULNERABILITY MAP
Critical risks (act before proceeding):
• [#N] [Assumption] — WHY it might be wrong — WHAT breaks if it is

High risks (validate before scaling):
• ...

DEPENDENCY CHAIN
[Assumption A] → depends on → [Assumption B] → which enables → [Assumption C]
Weakest link: [X] — if this breaks, [Y] and [Z] also fail

REVERSIBILITY ASSESSMENT
• Reversible bets: [list]
• Irreversible commitments: [list — treat with extreme care]

KILL SWITCHES
What would have to be true at [30/60/90 days] to continue vs. kill/pivot?
• Continue if: ...
• Kill/pivot if: ...

HARDENING ACTIONS
1. [Specific validation to do before proceeding]
2. [Alternative approach to consider]
3. [Contingency to build into the plan]
Challenge分析报告：[计划名称]
核心假设（提取结果）
1. [假设内容] — 置信度：[高/中/低/未知] — 错误影响：[关键/高/中/低]
2. ...

脆弱性图谱
关键风险（推进前需处理）：
• [#序号] [假设内容] — 可能错误的原因 — 错误后的影响

高风险（规模化前需验证）：
• ...

依赖链
[假设A] → 依赖 → [假设B] → 支撑 → [假设C]
最薄弱环节：[X] — 如果该环节断裂，[Y]和[Z]也会失败

可逆性评估
• 可逆赌注：[列表]
• 不可逆承诺：[列表 — 需格外谨慎对待]

终止开关
在[30/60/90天]时，哪些条件成立才继续，哪些条件下需终止/转型？
• 继续条件：...
• 终止/转型条件：...

强化措施
1. [推进前需完成的具体验证工作]
2. [可考虑的替代方案]
3. [需纳入计划的应急预案]

Challenge Patterns by Plan Type

不同计划类型的Challenge分析要点

Product Roadmap

产品路线图

  • Are we building what customers will pay for, or what they said they wanted?
  • Does the velocity estimate account for real team capacity (not theoretical)?
  • What happens if the anchor feature takes 3× longer than estimated?
  • Who owns decisions when requirements conflict?
  • 我们正在构建的是客户愿意付费的产品，还是他们说想要的产品？
  • 交付速度预估是否考虑了团队实际能力（而非理论值）？
  • 如果核心功能的开发时间是预估的3倍，会发生什么？
  • 当需求冲突时，谁来做决策？

Go-to-Market Plan

上市计划

  • What's the actual ICP conversion rate, not the hoped-for one?
  • How many touches to close, and do you have the sales capacity for that?
  • What happens if the first 10 deals take 3 months instead of 1?
  • Is "land and expand" a real motion or a hope?
  • 实际的ICP（理想客户画像）转化率是多少，而非预期值？
  • 成单需要多少次触达，你们的销售团队是否有足够能力应对？
  • 如果前10个订单花了3个月而非1个月才完成，会怎样？
  • “先获客再扩张”是真实可行的策略，还是只是一种期望？

Hiring Plan

招聘计划

  • What happens if the key hire takes 4 months to find, not 6 weeks?
  • Is the plan dependent on retaining specific people who might leave?
  • Does the plan account for ramp time (usually 3–6 months before full productivity)?
  • What's the burn impact if headcount leads revenue by 6 months?
  • 如果核心岗位的招聘耗时4个月而非6周，会发生什么？
  • 计划是否依赖于留住可能离职的特定人员？
  • 计划是否考虑了上手时间（通常需要3-6个月才能达到全产能）？
  • 如果人员招聘早于营收6个月，会对烧钱率产生什么影响？

Fundraising Plan

融资计划

  • What's your fallback if the lead investor passes?
  • Have you modeled the timeline if it takes 6 months, not 3?
  • What's your runway at current burn if the round closes at the low end?
  • What assumptions break if you raise 50% of the target amount?
  • 如果领投方拒绝，你的备选方案是什么？
  • 你是否模拟过融资耗时6个月而非3个月的时间线？
  • 如果融资额仅达目标下限，按当前烧钱率你的现金流还能支撑多久？
  • 如果只融到目标金额的50%，哪些假设会不成立？

The Hardest Questions

最棘手的问题

These are the ones people skip:
  • "What's the bear case, not the base case?"
  • "If this exact plan was run by a team we don't trust, would it work?"
  • "What are we not saying out loud because it's uncomfortable?"
  • "Who has incentives to make this plan sound better than it is?"
  • "What would an enemy of this plan attack first?"
这些是人们常回避的问题：
  • “最坏的情况是什么，而非基准情况？”
  • “如果这个完全相同的计划由我们不信任的团队执行，它能成功吗？”
  • “哪些内容我们因为不舒服而没有大声说出来？”
  • “哪些人有动机让这个计划听起来比实际更好？”
  • “这个计划的反对者会首先攻击哪个点？”

Deliverable

交付成果

The output of 
/em:challenge
is not permission to stop. It's a vulnerability map. Now you can make conscious decisions: validate the risky assumptions, hedge the critical ones, or accept the bets you're making knowingly.
Unknown risks are dangerous. Known risks are manageable.
/em:challenge
的输出不是停止计划的许可，而是一份脆弱性图谱。现在你可以做出有意识的决策：验证高风险假设、对冲关键风险，或者明知故犯地接受这些赌注。
未知风险是危险的，已知风险是可控的。