Back to Details

working-backwards

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Working Backwards (PR/FAQ + Backcasting)

逆向工作法（PR/FAQ + 回溯规划）

Scope

适用范围

Covers
  • Turning a product idea into a customer-centric future press release + FAQ (PR/FAQ)
  • Creating 2–3 divergent PR options to avoid solution lock-in
  • Backcasting a launch: a concrete GTM + operational “machinery” plan from target date back to today
  • Surfacing stakeholders, dependencies, constraints, and risks early
When to use
  • “Write a PR/FAQ for…”
  • “Working backwards from the customer…”
  • “Create a future press release / press release from the future”
  • “Backcast a launch plan / working backwards timeline”
  • “We need alignment on what we’re building before writing a PRD”
When NOT to use
  • You don’t yet understand the problem and need discovery framing (use 
    problem-definition
    )
  • You already have narrative alignment and need detailed requirements (use 
    writing-prds
    )
  • You need a build-ready engineering/design spec (use 
    writing-specs-designs
    )
  • You’re prioritizing among many initiatives (use 
    prioritizing-roadmap
    )
  • You only need marketing copy for an already-built product (this skill is for product decision-making)
涵盖内容
  • 将产品理念转化为以客户为中心的未来新闻稿+常见问题解答（PR/FAQ）
  • 创作2-3种不同方向的PR方案，避免陷入单一解决方案的局限
  • 发布回溯规划：从目标日期倒推至当前的具体GTM+运营“机制”计划
  • 提前识别利益相关者、依赖项、约束条件和风险
适用场景
  • “为……创作PR/FAQ”
  • “从客户视角逆向工作……”
  • “创作未来新闻稿/站在未来视角撰写新闻稿”
  • “回溯发布计划/逆向工作时间线”
  • “在撰写PRD前，我们需要对齐待开发内容”
不适用场景
  • 尚未明确问题，需要进行问题定义时（请使用
    problem-definition
    工具）
  • 已达成叙事对齐，需要撰写详细需求时（请使用
    writing-prds
    工具）
  • 需要可用于开发的工程/设计规格说明书时（请使用
    writing-specs-designs
    工具）
  • 需要在多个项目间进行优先级排序时（请使用
    prioritizing-roadmap
    工具）
  • 仅需为已上线产品撰写营销文案时（本技能用于产品决策阶段）

Inputs

输入要求

Minimum required
  • Product/context + target customer/user segment
  • Problem statement (or symptoms) + why now
  • Candidate solution idea(s) (can be vague; options are welcome)
  • Constraints: timeline/launch target, platform, policy/legal, dependencies
  • Success metrics (1–3) + guardrails (2–5)
Missing-info strategy
  • Ask up to 5 questions from references/INTAKE.md.
  • If answers remain missing, proceed with clearly labeled assumptions and provide 2–3 options (PR variants, scope, rollout).
最低必填项
  • 产品/背景信息 + 目标客户/用户群体
  • 问题陈述（或症状）+ 为何选择现在推进
  • 候选解决方案构想（可模糊，欢迎提供多种选项）
  • 约束条件：时间线/发布目标、平台、政策/合规要求、依赖项
  • 成功指标（1-3个）+ 防护规则（2-5条）
信息缺失处理策略
  • 可从references/INTAKE.md中选取最多5个问题进行询问。
  • 若仍存在信息缺失，基于明确标注的假设推进工作，并提供2-3种选项（如不同PR版本、范围、发布方式）。

Outputs (deliverables)

输出成果（交付物）

Produce a Working Backwards Pack in Markdown (in-chat; or as files if the user requests):
  1. Context snapshot
  2. PR options: 2–3 divergent future press releases (1 page each)
  3. Selected PR: refined future press release
  4. FAQ: customer + internal (business/ops/technical/legal) FAQs
  5. Backcasting plan: milestones to launch (owners, dates, dependencies)
  6. Stakeholder + “machinery” plan: approvals, comms, rollout, support readiness
  7. Success metrics + guardrails (+ instrumentation notes)
  8. Risks / Open questions / Next steps (always included)
Templates: references/TEMPLATES.md
Expanded guidance: references/WORKFLOW.md
生成Markdown格式的逆向工作法包（可在对话中展示；若用户要求，也可作为文件交付）：
  1. 背景快照
  2. PR方案选项：2-3种不同方向的未来新闻稿（每份1页）
  3. 选定PR：经优化的未来新闻稿
  4. 常见问题解答（FAQ）：面向客户及内部（业务/运营/技术/合规）的常见问题
  5. 回溯规划：发布里程碑（负责人、日期、依赖项）
  6. 利益相关者+运营机制计划：审批流程、沟通方案、发布节奏、支持就绪状态
  7. 成功指标+防护规则（含埋点说明）
  8. 风险/待解决问题/下一步行动（必含内容）
模板：references/TEMPLATES.md
扩展指南：references/WORKFLOW.md

Workflow (8 steps)

工作流程（8个步骤）

1) Intake + decision framing

1) 需求摄入 + 决策框架搭建

  • Inputs: user request; references/INTAKE.md.
  • Actions: Clarify the decision (invest vs not, choose approach), audience, and target launch date/timebox. Capture constraints + stakeholders.
  • Outputs: Context snapshot.
  • Checks: You can state the decision and time horizon in one sentence.
  • 输入：用户需求；references/INTAKE.md
  • 行动：明确决策点（是否投入资源、选择何种方案）、受众、目标发布日期/时间范围。记录约束条件和利益相关者。
  • 输出：背景快照
  • 检查标准：可在一句话中明确决策点和时间范围

2) Write the problem paragraph (before any solution)

2) 撰写问题段落（在构思解决方案之前）

  • Inputs: customer segment + evidence; why now.
  • Actions: Draft “Problem today” in customer language. List top pains and current alternatives/workarounds.
  • Outputs: Problem paragraph + alternatives bullets.
  • Checks: Describes pain without specifying implementation; avoids “we want to build X” framing.
  • 输入：客户群体+相关依据；为何选择现在推进
  • 行动：用客户的语言撰写“当前问题”段落。列出核心痛点及当前的替代方案/临时解决办法。
  • 输出：问题段落+替代方案列表
  • 检查标准：仅描述痛点，不提及具体实现；避免使用“我们想要开发X”的表述框架

3) Draft 2–3 divergent future press releases (options)

3) 撰写2-3种不同方向的未来新闻稿（方案选项）

  • Inputs: problem paragraph; constraints.
  • Actions: Create Option A/B/C PRs with different solution shapes. Keep them 1 page each.
  • Outputs: 2–3 PR drafts.
  • Checks: Options are meaningfully different; each promises clear customer value; no internal jargon.
  • 输入：问题段落；约束条件
  • 行动：创作A/B/C三种不同解决方案方向的PR。每份控制在1页以内。
  • 输出：2-3份PR草稿
  • 检查标准：方案之间存在实质性差异；每份都明确承诺为客户带来价值；无内部行话

4) Select the best option and refine to a single PR

4) 选择最优方案并优化为单一PR

  • Inputs: PR options; decision criteria; stakeholder feedback (if available).
  • Actions: Pick a winner (or hybrid) and refine the PR for clarity, boundaries, and a concrete “how it works”.
  • Outputs: Selected PR.
  • Checks: A stakeholder can restate the benefit and “why now” in one sentence; “who it’s for / not for” is explicit.
  • 输入：PR方案选项；决策标准；利益相关者反馈（若有）
  • 行动：选出最优方案（或混合方案），并优化PR的表述清晰度、范围边界及具体“运作方式”。
  • 输出：选定的PR
  • 检查标准：利益相关者可在一句话中重述核心价值及“为何现在推进”；明确说明“适用/不适用人群”

5) Write the FAQ (customer + internal)

5) 撰写FAQ（客户+内部）

  • Inputs: selected PR; constraints; dependencies.
  • Actions: Draft FAQs in sections: customer, business, technical/ops, legal/compliance. Include out-of-scope, risks, and measurement.
  • Outputs: FAQ section.
  • Checks: Top objections are answered; open questions are explicitly labeled; no “we’ll figure it out later” hand-waving.
  • 输入：选定的PR；约束条件；依赖项
  • 行动：分模块撰写FAQ：客户模块、业务模块、技术/运营模块、合规模块。涵盖超出范围的内容、风险及衡量指标。
  • 输出：FAQ模块
  • 检查标准：核心异议已得到解答；待解决问题已明确标注；无“我们之后再解决”之类的模糊表述

6) Backcast: build the launch and “machinery” plan

6) 回溯规划：制定发布及运营机制计划

  • Inputs: target launch tier/date; FAQ dependencies.
  • Actions: Create a milestone plan working backward (design, eng, data, legal, docs, support, comms). Define launch tiers and rollback.
  • Outputs: Backcasting plan + launch tiers/rollback plan.
  • Checks: Each milestone has an owner + success criteria; major dependencies have a plan.
  • 输入：目标发布阶段/日期；FAQ中的依赖项
  • 行动：从目标日期倒推制定里程碑计划（涵盖设计、开发、数据、合规、文档、支持、沟通环节）。定义发布阶段及回滚机制。
  • 输出：回溯规划+发布阶段/回滚计划
  • 检查标准：每个里程碑都有负责人+成功标准；主要依赖项都有应对计划

7) Stress-test: pre-mortem + metrics + guardrails

7) 压力测试：事前复盘+指标+防护规则

  • Inputs: PR/FAQ + backcasting plan.
  • Actions: Run a pre-mortem. List failure modes (trust/safety/quality/cost). Define success metrics + guardrails + instrumentation needs.
  • Outputs: Risks + metrics/guardrails + validation notes.
  • Checks: Each major risk has a mitigation/monitor; metrics are computable and owned.
  • 输入：PR/FAQ + 回溯规划
  • 行动：开展事前复盘。列出可能的失败模式（信任/安全/质量/成本）。定义成功指标+防护规则+埋点需求。
  • 输出：风险清单+指标/防护规则+验证说明
  • 检查标准：每个主要风险都有缓解/监控措施；指标可量化且有负责人

8) Quality gate + finalize pack

8) 质量关卡+最终确定工作包

  • Inputs: full draft pack.
  • Actions: Run references/CHECKLISTS.md and score with references/RUBRIC.md. Ensure final section includes risks/open questions/next steps.
  • Outputs: Final Working Backwards Pack.
  • Checks: Pack is decision-ready and shareable async (no meeting required).
  • 输入：完整的工作包草稿
  • 行动：使用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 (B2B SaaS): “Write a PR/FAQ and backcasting plan for ‘Role-based dashboards’ for enterprise admins, with a beta in 8 weeks.”
Expected: 2–3 PR options, selected PR/FAQ, and a milestone plan covering security review, instrumentation, docs/support.
Example 2 (Consumer): “Work backwards for ‘Saved routes’ in a navigation app; propose two alternative product concepts and pick one.”
Expected: divergent PRs that surface trade-offs, clear metrics (repeat usage, retention), and guardrails (privacy, battery, safety).
Boundary example: “Write a PR/FAQ for ‘use AI’ (no user problem).”
Response: ask intake questions, redirect to 
problem-definition
if needed, and do not pretend to have customer clarity.
示例1（B2B SaaS）：“为企业管理员的‘基于角色的仪表盘’创作PR/FAQ和回溯规划，8周内推出测试版。”
预期成果：2-3种PR方案选项、选定的PR/FAQ，以及涵盖安全评审、埋点、文档/支持的里程碑计划。
示例2（消费级产品）：“为导航应用的‘路线保存’功能进行逆向工作；提出两种不同的产品构想并选出最优方案。”
预期成果：体现权衡取舍的差异化PR、明确的指标（重复使用率、留存率）及防护规则（隐私、电量、安全）。
边界示例：“为‘使用AI’创作PR/FAQ（未提及用户问题）。”
应对方式：询问需求摄入问题，必要时引导至
problem-definition
工具，不得假装已明确客户需求。