Why Working Backwards and not a regular PRD?

A regular PRD starts with what you want to build. Working Backwards starts with the customer and the outcome, then makes you justify the build. You catch weak ideas in a document instead of in production.

Do I need to know Amazon's methodology?

No. The tool walks you through every step — the press release, the FAQs, and the “so what” test — and explains each one as you go. Prior knowledge helps, but it isn't required.

How long does it take?

A first draft takes about 15–20 minutes. Sharpening the inputs until the “so what” holds up is where the real work happens — usually a few focused sessions.

What if my answers are vague?

Vague answers are the signal. The format surfaces them immediately, so you can tighten the customer, the problem, and the value before spending a single engineering hour.

Yes. You can write your first PR/FAQ and run the full process at no cost. No credit card required to start.

Working Backwards — Launch Products the Amazon Way

Launch products
the amazon

Working Backwards is the Amazon process behind Kindle, Prime, AWS, and the most-cited product memos in tech.

What Can You Get With 7 Steps?

A Verdict

Four dimensions scored: customer clarity, problem sharpness, evidence strength, and risk. You'll know exactly where your idea holds and where it breaks.

A Press Release

Headline, problem, solution, and customer quote — written as if the product already shipped. The format Amazon uses to align teams before a line of code gets written.

An FAQ

What your future customer will ask, and what your board will challenge. Honest answers to both, surfaced before they become blockers.

A PRD

Vision, goals, requirements, and milestones — structured so an engineer can open it and start working without a single clarification call.

The Working Backwards loop: Idea, then Write PR/FAQ, Align, Build, Launch — and Learn back to the start

What Is The Working Backwards Philosophy?

Working Backwards is a process for deciding whether to build something, and how to build it, by writing the press release before writing any code. Jeff Bezos and the Amazon leadership team developed it around 2004. Most of Amazon's biggest products since then came through it.

The idea is simple. Before you build anything, you write the press release for the launch. You write it from the customer's perspective. You write the FAQ a customer would ask, and the FAQ a board would ask. You write all of it as if the product already exists. Then you read it and ask: so what?

If the document does not describe a product that is meaningfully better, faster, easier, or cheaper than what is already out there, you do not start. You change the inputs and write it again.

Authors

Two former Amazon executives, Colin Bryar and Bill Carr, documented the full process in their 2021 book Working Backwards: Insights, Stories, and Secrets from Inside Amazon. This guide pulls from that book, public Amazon press releases, and primary-source artifacts from companies that adopted the same approach.

Working Backwards: Insights, Stories, and Secrets from Inside Amazon — book cover

Why It Works

Prose forces precision.

Slides let you wave your hands. A press release does not. If you cannot write a clear sentence about who the customer is and why they care, you do not understand the problem yet.

Customer-first by structure.

When the format starts with "for the customer," you cannot start anywhere else. Willpower is not required. The artifact does the work.

The "so what" is brutal and fast.

A bad PR/FAQ takes 30 seconds to read and reject. A bad product takes 18 months to build and reject. The asymmetry is the point.

The PR/FAQ also has a known failure mode. It does not save bad inputs. The Fire Phone team wrote one. They built against it. The product still failed because the "customer" was a fantasy and the "problem" was Amazon's, not the customer's. The format is not magic. The honesty of the inputs is.

Launch productsthe amazon