Back to Details

startup-pivoting

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Startup Pivoting

创业公司产品转型

Scope

适用范围

Covers
  • Deciding whether to pivot vs persevere when a product/startup is stuck (typically pre- or early-PMF)
  • Turning a pivot debate into an executable Pivot Decision & Execution Pack (not vibes)
  • Designing a time-boxed pivot validation + execution plan with clear decision gates
When to use
  • “Should we pivot?”
  • “We’re stuck pre-PMF / growth has stalled.”
  • “We think the ICP/market is wrong—help us change direction.”
  • “We need a pivot options map and a concrete plan to validate one quickly.”
  • “Make a pivot decision memo we can share with the team/investors.”
When NOT to use
  • You don’t have a product or real customer evidence yet (do discovery/problem framing first, e.g., 
    problem-definition
    )
  • You only need incremental optimization (pricing tests, onboarding tweaks, activation/retention work) and direction is not in question
  • You’re choosing between many roadmap bets within an agreed strategy (use 
    prioritizing-roadmap
    )
  • You want the agent to “pick a new startup idea” from scratch (use 
    startup-ideation
    )
Human checkpoint (required)
  • A pivot is a high-stakes strategic decision. This skill produces decision-ready artifacts and a plan, but a human owner must make the final call.
涵盖内容
  • 当产品/创业公司陷入停滞时（通常是PMF前或早期PMF阶段），判断应该转型还是坚持
  • 将转型讨论转化为可落地的《转型决策与执行包》（而非主观感受）
  • 设计带有明确决策节点的时间限定型转型验证+执行计划
适用场景
  • “我们是否应该转型？”
  • “我们在PMF前陷入停滞/增长已停滞。”
  • “我们认为核心客户群体（ICP）/市场定位有误——帮我们调整方向。”
  • “我们需要一份转型选项图谱，以及能快速验证其中一个选项的具体计划。”
  • “生成一份可与团队/投资人共享的转型决策备忘录。”
不适用场景
  • 你还没有产品或真实客户反馈（先进行需求探索/问题定义，例如使用
    problem-definition
    工具）
  • 你只需要增量优化（定价测试、注册流程调整、激活/留存优化）且方向无争议
  • 你要在已达成共识的战略框架内选择多个 roadmap 优先级（使用
    prioritizing-roadmap
    工具）
  • 你希望从零开始“生成新的创业点子”（使用
    startup-ideation
    工具）
人工审核（必填）
  • 转型是高风险的战略决策。本工具会生成可用于决策的文档和计划，但最终决策必须由负责人做出。

Inputs

输入信息

Minimum required
  • What you sell/build today (product summary + current target customer)
  • The “stuck” symptoms + evidence (metrics, user feedback, pipeline, retention/churn, qualitative signals)
  • Runway/timebox (months of runway or a decision deadline)
  • Constraints/non-negotiables (compliance, brand/trust, margins, platform, team capabilities)
  • Current “theory of winning” (who + problem + why you win)
Missing-info strategy
  • Ask up to 5 questions from references/INTAKE.md.
  • If answers aren’t available, proceed with explicit assumptions and offer 2 scope options (lean 60–90 min analysis vs thorough 1–2 day pack).
最低必填项
  • 当前的产品/业务内容（产品概述+当前目标客户）
  • 停滞的症状+证据（指标、用户反馈、销售线索、留存/流失数据、定性信号）
  • 现金流储备时长（Runway）/时间期限（可支撑的现金流月数或决策截止日期）
  • 不可妥协项（合规要求、品牌信任、利润率、平台限制、团队能力）
  • 当前的“成功假设”（目标用户+解决的问题+核心竞争力）
信息缺失处理策略
  • 从references/INTAKE.md中最多提出5个问题补充信息。
  • 如果无法获取补充信息，基于明确假设继续推进，并提供两种范围选项（精简版60–90分钟分析 vs 完整版1–2天的执行包）。

Outputs (deliverables)

输出成果（交付物）

Produce a Pivot Decision & Execution Pack in Markdown (in-chat; or as files if requested):
  1. Context snapshot (what’s true today; constraints; runway; decision owner)
  2. Stuck diagnosis (symptoms → likely causes → evidence gaps)
  3. Exhaustion check (“have we exhausted the possibilities?”) + the last best non-pivot moves (time-boxed)
  4. Pivot options map (4P pivot grid + 10% vs 200% classification)
  5. Chosen pivot thesis (who/problem/promise) + success metrics + kill criteria
  6. Validation plan (customer learning + experiments; decision gates; what would change your mind)
  7. Execution plan (pivot sprint plan; cut list; resourcing; comms; risks)
  8. Risks / Open questions / Next steps (always included)
Templates: references/TEMPLATES.md
Expanded guidance: references/WORKFLOW.md
生成Markdown格式的《转型决策与执行包》（可在对话中直接输出；或按需生成文件）：
  1. 当前情况快照（当前状态、约束条件、现金流储备时长、决策负责人）
  2. 停滞原因诊断（症状→可能原因→证据缺口）
  3. 穷尽性检查（“我们是否已尝试所有可能？”）+ 最后的最优非转型方案（时间限定）
  4. 转型选项图谱（4P转型矩阵 + 10%小幅调整 vs 200%大幅转向分类）
  5. 选定的转型假设（目标用户/问题/价值主张）+ 成功指标 + 终止标准
  6. 验证计划（客户调研+实验、决策节点、可推翻假设的条件）
  7. 执行计划（转型冲刺计划、停止事项清单、资源分配、沟通计划、风险应对）
  8. 风险/待解决问题/下一步行动（必含内容）
模板：references/TEMPLATES.md
扩展指南：references/WORKFLOW.md

Workflow (7 steps)

执行流程（7步）

1) Frame the decision (and the clock)

1) 明确决策（及时间限制）

  • Inputs: Request + runway/timebox + references/INTAKE.md.
  • Actions: Define the decision: pivot vs persevere vs shut down (or “pivot A vs pivot B”). Name the decision owner and the decision date. Capture non-negotiables.
  • Outputs: Context snapshot + decision statement.
  • Checks: The decision is binary/explicit and time-bounded (no “let’s think about it”).
  • 输入信息：需求请求 + 现金流储备时长/时间期限 + references/INTAKE.md
  • 执行动作：明确决策类型：转型、坚持或关停（或“转型方案A vs 转型方案B”）。指定决策负责人和决策截止日期。记录不可妥协项。
  • 输出成果：当前情况快照 + 决策声明
  • 校验标准：决策为明确的二选一/多选一，且有时间限制（避免“先想想再说”）

2) Diagnose what’s actually “stuck”

2) 诊断真正的停滞原因

  • Inputs: Metrics, funnel, retention/churn, pipeline, user feedback, win/loss notes.
  • Actions: Summarize symptoms and hypothesize causes. Separate signal (real demand/value issues) from execution (distribution/onboarding/pricing) issues.
  • Outputs: Stuck diagnosis + evidence inventory + top evidence gaps.
  • Checks: You can state the top 1–3 bottlenecks and what data would falsify them.
  • 输入信息：指标、转化漏斗、留存/流失数据、销售线索、用户反馈、赢单/丢单分析
  • 执行动作：总结症状并假设原因。区分信号（真实需求/价值问题）与执行（获客/注册流程/定价）问题。
  • 输出成果：停滞原因诊断 + 证据清单 + 核心证据缺口
  • 校验标准：可明确列出1–3个核心瓶颈，以及可证伪这些瓶颈的数据

3) Run the exhaustion check (Butterfield rule)

3) 执行穷尽性检查（Butterfield法则）

  • Inputs: Stuck diagnosis + constraints + prior attempts.
  • Actions: Use references/TEMPLATES.md to complete the Exhaustion Check: list the most credible non-pivot levers and whether they were tried well. Identify the “last best” 1–3 non-pivot moves worth time-boxing (if any).
  • Outputs: Exhaustion Check + time-boxed “last best tries” plan (or explicit rationale for skipping).
  • Checks: If you recommend pivoting, you can explain why remaining non-pivot levers are unlikely/too slow vs runway.
  • 输入信息：停滞原因诊断 + 约束条件 + 过往尝试
  • 执行动作：使用references/TEMPLATES.md完成穷尽性检查：列出最可信的非转型手段，以及是否已充分尝试。确定1–3个值得时间限定尝试的“最后最优非转型方案”（如有）。
  • 输出成果：穷尽性检查报告 + 时间限定的“最后尝试”计划（或明确的跳过理由）
  • 校验标准：若建议转型，需说明剩余非转型手段为何不可行/相对于现金流储备时长过于缓慢

4) Generate pivot options (require at least one 200% pivot)

4) 生成转型选项（至少包含一个200%大幅转向选项）

  • Inputs: Theory of winning + evidence + constraints.
  • Actions: Create 4–8 options using a 4P pivot grid (Problem, Persona, Product, Positioning/Package). Classify each as ~10% (small tweak) vs 200% (meaningfully different bet). Include at least one 200% option.
  • Outputs: Pivot options map with a short “why this could win” and “what would have to be true”.
  • Checks: Each option is distinct, falsifiable, and has a plausible path to distribution.
  • 输入信息：成功假设 + 证据 + 约束条件
  • 执行动作：使用4P转型矩阵（问题、用户画像、产品、定位/包装）生成4–8个选项。将每个选项分类为~10%（小幅调整）vs 200%（大幅转向）。至少包含一个200%选项。
  • 输出成果：转型选项图谱，每个选项附带简短的“成功可能性”和“必要前提”说明
  • 校验标准：每个选项独特、可证伪，且有合理的获客路径

5) Select a pivot thesis + metrics + kill criteria

5) 选定转型假设 + 指标 + 终止标准

  • Inputs: Options map + decision criteria (runway, strengths, market, moat).
  • Actions: Pick the best option (or top 2). Write a Pivot Thesis Card and define success metrics (North Star + 2–5 leading indicators) plus guardrails. Define kill criteria and a decision gate date.
  • Outputs: Pivot thesis + metrics + kill criteria.
  • Checks: Metrics are computable; kill criteria are real (not “keep going until it works”).
  • 输入信息：选项图谱 + 决策标准（现金流储备时长、核心优势、市场规模、护城河）
  • 执行动作：选择最优选项（或前2个）。撰写转型假设卡片，定义成功指标（北极星指标 + 2–5个前置指标）及边界条件。定义终止标准和决策节点日期。
  • 输出成果：转型假设 + 成功指标 + 终止标准
  • 校验标准：指标可量化；终止标准明确（而非“直到成功为止”）

6) Build the validation + execution plan (Todd Jackson rule)

6) 制定验证+执行计划（Todd Jackson法则）

  • Inputs: Pivot thesis + runway + team capacity.
  • Actions: Create a time-boxed pivot sprint: customer learning plan, experiments, build scope, and what to stop building. Include a comms plan (team/investors/customers) and a rollback/exit plan if results fail.
  • Outputs: Validation plan + execution plan (owners, timeline, decision gates).
  • Checks: Plan fits runway; includes a cut list; includes at least one “hard truth” test that could disconfirm the thesis.
  • 输入信息：转型假设 + 现金流储备时长 + 团队能力
  • 执行动作：制定时间限定的转型冲刺计划：客户调研计划、实验、开发范围、停止开发事项。包含沟通计划（团队/投资人/客户）及验证失败后的回滚/退出计划。
  • 输出成果：验证计划 + 执行计划（负责人、时间线、决策节点）
  • 校验标准：计划适配现金流储备时长；包含停止事项清单；包含至少一个可推翻假设的“硬核验证”测试

7) Quality gate + finalize pack

7) 质量校验 + 最终定稿

  • Inputs: Full draft pack.
  • Actions: Run references/CHECKLISTS.md and score with references/RUBRIC.md. Add Risks / Open questions / Next steps and confirm the human checkpoint (decision owner/date).
  • Outputs: Final Pivot Decision & Execution Pack.
  • Checks: A stakeholder can read it async and understand: (a) why you’re pivoting, (b) what you’ll do, (c) how you’ll know, (d) when you’ll decide.
  • 输入信息：完整的执行包草稿
  • 执行动作：使用references/CHECKLISTS.md检查，并通过references/RUBRIC.md评分。添加风险/待解决问题/下一步行动，并确认人工审核环节（决策负责人/日期）。
  • 输出成果：最终版《转型决策与执行包》
  • 校验标准：利益相关者可异步阅读并理解：(a) 为何需要转型，(b) 具体执行内容，(c) 如何判断成功，(d) 决策截止日期

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 (B2B SaaS stuck pre-PMF): “We built an AI support copilot for SMBs. Trials convert, but retention is poor and sales cycles are long. We have 6 months of runway. Should we pivot, and if so how?”
Expected: a Pivot Decision & Execution Pack with an exhaustion check (pricing/onboarding/ICP), 4–8 pivot options including at least one 200% pivot, a chosen thesis with metrics/kill criteria, and a 4–6 week pivot sprint plan.
Example 2 (Consumer plateau): “Our language learning app growth stalled and D30 retention is low. We suspect our promise is wrong. Create a pivot options map and a validation plan.”
Expected: a 4P pivot grid that includes positioning/package changes and at least one new persona/problem angle, plus a time-boxed validation plan with decision gates.
Boundary example: “Just tell us what to pivot to—no metrics, no customers, no constraints.”
Response: explain that pivoting without evidence is guesswork; ask 3–5 intake questions, propose a discovery/validation sprint, and only then produce a pivot thesis and plan.
示例1（B2B SaaS在PMF前陷入停滞）：“我们为中小企业（SMBs）打造了AI客服 copilots。试用用户有转化，但留存率低且销售周期长。我们有6个月的现金流储备时长。我们是否应该转型？如果是，该如何转型？”
预期输出：一份《转型决策与执行包》，包含穷尽性检查（定价/注册流程/核心客户群体）、4–8个转型选项（至少一个200%大幅转向）、选定的转型假设（含指标/终止标准）、4–6周的转型冲刺计划。
示例2（C端产品增长停滞）：“我们的语言学习应用增长停滞，30日留存率低。我们怀疑价值主张有误。生成一份转型选项图谱和验证计划。”
预期输出：一份4P转型矩阵（包含定位/包装调整及至少一个新用户画像/问题方向），以及带决策节点的时间限定验证计划。
边界示例：“直接告诉我们该转型到什么方向——没有指标、没有客户、没有约束条件。”
回应：说明无证据支撑的转型是猜测；提出3–5个补充问题，建议先进行需求探索/验证冲刺，之后再生成转型假设和计划。