Working Backward

Working Backward is Amazon's approach to developing an idea from a specified customer experience. Its PR/FAQ practice describes the proposed product's benefit and answers customer and operational questions before substantial building begins. The document is intended to clarify the need, expose assumptions, and help the team decide whether and how to proceed; a clear document alone does not establish demand or success.

Working backward turns a proposed outcome into a set of requirements that can be challenged before resources are committed. In Amazon's PR/FAQ version, the imagined announcement makes the customer benefit concrete, while the questions expose what would have to be true for that promise to hold. An unanswered question is useful: it identifies an assumption to investigate, a dependency to resolve, or a reason to abandon the idea.

The practical distinction is between describing a finished activity and describing a changed experience. 'We launched a scheduling tool' says little about whether booking became easier. 'A first-time visitor can book without calling' identifies behavior you can observe. Outside product development, the same planning logic can connect a desired experience to prerequisites, provided the people affected help define the outcome and the plan remains open to revision.

When to use it

When building or iterating on products; when evaluating market opportunities; when deciding resource allocation; when scaling operations.

How it can help

Describe the customer's problem and a proposed finished experience, then identify what would have to be true to deliver it. Use unresolved FAQ questions to guide research and early tests. Revise or discard the proposal when the evidence shows that its benefit, feasibility, or fit is inadequate.