Back to Details

working-backwards

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Working Backwards

反向工作（Working Backwards）

What It Is

什么是反向工作

Working Backwards is Amazon's product development methodology. The core insight: start with the customer problem and work backward to the solution, not the other way around.
Most teams work forward: "We have this technology/capability/idea — what can we build with it?" Working Backwards inverts this: "What problem does the customer have? What would the ideal solution look like? Now, how do we build it?"
The mechanism: Write an internal press release and FAQ before building anything. If you can't write a compelling press release, you don't have a compelling product.
As Jeff Bezos put it: "We took it as an article of faith — if we served customers well, if we prioritized customers and delivered for them, things like sales, revenue, and free cash flow would follow."
反向工作是亚马逊的产品开发方法论。核心理念：从客户问题出发，反向推导解决方案，而非相反方向。
大多数团队采用正向思维：“我们拥有这项技术/能力/想法——可以用它构建什么？”反向工作则颠覆了这一逻辑：“客户面临什么问题？理想的解决方案是什么样的？现在，我们该如何构建它？”
实施机制：在开始任何构建工作之前，先撰写一份内部新闻稿和FAQ。如果无法写出有吸引力的新闻稿，说明你的产品不具备吸引力。
正如杰夫·贝佐斯所说：“我们坚信——如果我们能很好地服务客户，优先考虑客户并为他们创造价值，那么销售额、收入和自由现金流等成果自然会随之而来。”

When to Use It

何时使用

Use Working Backwards when you need to:
  • Define a new product or major feature before committing resources
  • Evaluate competing product ideas and choose which to build
  • Align stakeholders on what you're building and why
  • Force clarity on vague product concepts
  • Prevent building solutions in search of problems
  • Create a shared vision that engineering, design, and leadership can rally around
  • Decide whether an idea is worth pursuing at all
当你需要以下场景时，可使用反向工作法：
  • 在投入资源前定义新产品或重大功能
  • 评估竞品产品创意并选择要构建的方向
  • 让利益相关方就构建内容及原因达成共识
  • 厘清模糊的产品概念
  • 避免为了解决问题而强行创造解决方案
  • 创建一个能让工程、设计和领导层共同追随的共享愿景
  • 判断某个创意是否值得投入资源

When Not to Use It

何时不使用

  • The work is incremental optimization (A/B tests, bug fixes)
  • You're executing on an already-defined product
  • The scope is too small to warrant the overhead
  • 工作内容为增量优化（如A/B测试、Bug修复）
  • 正在执行已定义好的产品工作
  • 范围过小，不值得投入相应的精力

Resources

参考资源

Books:
  • Working Backwards by Bill Carr and Colin Bryar
  • The Everything Store by Brad Stone
书籍：
  • Bill Carr和Colin Bryar所著的《Working Backwards》
  • Brad Stone所著的《The Everything Store》