The Working Backwards Framework (Amazon PR/FAQ) Explained

Working Backwards is Amazon's approach to developing new products, built around writing a mock press release and FAQ document (together called a "PR/FAQ") for a product before it's built — forcing a team to clearly articulate the customer benefit in plain, concrete language before investing any real engineering effort. The core idea: if you can't write a compelling, specific press release for something, you probably don't yet understand it well enough to build it.

Quick facts

• Working Backwards means starting from the customer's perspective and the finished product's announcement, then working backward to what needs to be built.
• The PR/FAQ document has two parts: a mock press release (as if the product just launched) and a detailed FAQ addressing likely questions.
• The exercise is meant to surface unclear thinking early — a vague or unconvincing press release usually means the underlying idea isn't fully thought through yet.
• Popularized publicly through descriptions of Amazon's internal product development process.

The two parts of a PR/FAQ

Why writing a fake press release first is so effective

Writing in the voice of a finished, customer-facing announcement forces genuine clarity that internal planning documents often let teams avoid. A press release has to explain, in plain language a real customer would understand, exactly what problem this solves and why they should care — there's no room for vague internal jargon or unclear value propositions to hide behind. If a team struggles to write a clear, compelling press release, that's a real signal the underlying idea itself isn't yet clear enough to justify building, regardless of how exciting it sounded in a verbal pitch or brainstorm.

A worked example: a mock press release excerpt

Headline: "New Feature Lets Small Business Owners See Cash Flow Forecasts Instantly, No Spreadsheets Required"

Summary: "[Company] today announced [Feature], which automatically forecasts a small business's cash flow 90 days out based on existing invoices and expenses — eliminating the need for manual spreadsheet forecasting that most small business owners currently either skip entirely or do inconsistently."

Customer quote: "I used to dread the end of the month trying to guess if I'd have enough cash to make payroll. Now I just glance at the forecast and I know," said [a representative customer].

Notice how specific and concrete this is — a real problem (uncertain cash flow, skipped or inconsistent forecasting), a real solution (automatic 90-day forecasting from existing data), and a real, plausible customer voice. A team that can't write something this specific and grounded for their idea likely hasn't yet done the thinking needed to actually build it well.

Why the FAQ section matters as much as the press release

The press release captures the customer-facing vision, but the FAQ section is where the harder, more uncomfortable internal questions get addressed directly — what will this actually cost to build, what are the biggest risks, why hasn't this been built already, what happens if a key assumption turns out to be wrong. Skipping the FAQ, or answering it superficially, defeats much of the exercise's value, since it's specifically designed to surface the difficult questions a real launch would eventually force anyway, but much earlier and much more cheaply.

When to use Working Backwards

This method is especially useful for larger, more ambiguous, higher-stakes initiatives — a brand-new product line, a major new feature with real strategic weight — where genuine clarity of thinking matters more than speed. It's less commonly applied to small, well-understood feature additions, where the overhead of writing a full PR/FAQ may exceed its value relative to a simpler PRD.

Common mistakes when using Working Backwards

• Writing a vague, generic press release that could describe almost any product. This defeats the entire purpose — specificity is what makes the exercise valuable.
• Skipping or rushing the FAQ section, avoiding the harder internal questions the method is specifically designed to surface early.
• Using it for every small feature, adding unnecessary overhead relative to its value for lower-stakes decisions.
• Treating a compelling press release as proof the idea will work, rather than as a tool for achieving clarity — a well-written PR/FAQ still needs real validation, not just clear articulation.

FAQ

Is Working Backwards only used at Amazon? While it originated at and is most associated with Amazon, many other companies have adopted similar PR/FAQ-style exercises for major product decisions, recognizing the value of forcing customer-facing clarity before significant investment.

How is a PR/FAQ different from a PRD? A PRD is typically more internally focused, detailing what a team will build and how success will be measured. A PR/FAQ is written from the customer's perspective first, focused on clarity of the value proposition, and is often used earlier, before a team commits to building something at all.

Who should write the PR/FAQ — the product manager alone, or a group? It's often drafted by a product manager or the idea's originator, then reviewed and challenged by others, since the value of the exercise partly comes from having other people probe the FAQ section with hard, skeptical questions.

Does a compelling PR/FAQ guarantee a product will succeed? No — it's a clarity and alignment tool, not a validation tool. A well-written PR/FAQ still needs to be tested against real customer evidence; it just ensures the team is starting from a clearly articulated, customer-grounded idea rather than a vague or internally-focused one.