Definition
Working Backwards is a product development methodology pioneered at Amazon where teams begin by writing a press release and FAQ document describing the finished product as if it were launching today. The press release is written from the customer's perspective, in plain language, and must clearly articulate the problem being solved, who it is for, and why the solution is better than alternatives. Only after the press release is approved does the team proceed to technical design and implementation.
The approach was introduced by Amazon VP Ian McAllister and became a core part of Amazon's product development culture. The idea is deceptively simple: if you cannot write a compelling press release for your product, you do not understand the customer value well enough to build it. The document forces product teams to resolve fundamental questions early. Who exactly is the customer? What specific problem are we solving? Why will they choose this over what they do today? These questions are much cheaper to answer in a document than in code.
Working Backwards complements other customer-centric approaches like Jobs to Be Done and customer development. Where JTBD gives you a framework for understanding customer motivations and customer development gives you a research methodology, Working Backwards gives you a forcing function for synthesizing that understanding into a clear product vision. It also serves as a lightweight alternative to a full PRD in the early stages of product definition.
Why It Matters for Product Managers
The most expensive mistakes in product development happen at the beginning, when teams commit to building the wrong thing. Working Backwards catches these mistakes early by requiring teams to articulate value before investing in solutions. Writing a press release exposes fuzzy thinking. If the headline is vague, the value proposition is unclear. If the customer quote sounds forced, the product probably does not solve a real pain point. If the FAQ section is full of "we'll figure that out later," the team is not ready to build.
The document also serves as an alignment tool. In a typical product development process, the PM, designer, engineering lead, and executives may each have a different mental model of what the product is. The Working Backwards document puts everyone's assumptions on paper where they can be examined and debated. Teams that align on the press release before starting technical work spend less time renegotiating scope during development.
How to Apply It
Write the press release first, targeting 1-1.5 pages. Start with a headline that would make your target customer stop scrolling. Follow with a subheading that names the customer segment and the primary benefit. Write two to three paragraphs covering the problem, the solution, and why now is the right time. Include a fictional customer quote that captures the emotional benefit, not just the functional one. End with a call to action explaining how customers can get started.
Then write the FAQ section, which is often the most valuable part. Include external FAQs (what customers would ask) and internal FAQs (what engineers, finance, and leadership would ask). Address pricing, competitive positioning, technical feasibility, and key risks honestly. Share the document broadly for feedback and iterate until the press release is compelling enough that you would actually want to read it. Use it alongside your product vision document and reference it throughout development to prevent scope drift. For a structured approach to building the roadmap that follows your Working Backwards document, see the roadmap building guide.