Write the press release before you build the product
Amazon teams write the customer's press release and FAQ before building anything. Here is how it works and what it teaches product managers.

Most teams decide what to build in a meeting, with slides and a lot of enthusiasm. Amazon has a different habit. The team writes the ending first, as a press release, before anything exists.
- A team with a new idea writes a press release and an FAQ before building.
- Both describe the finished product from the customer's point of view.
- Senior meetings start with everyone reading a written narrative in silence.
- The method is described in Working Backwards (2021) by Colin Bryar and Bill Carr, both former Amazon executives.
What happens, in order
The story is a short process. Here it is step by step.
- A team wants to build something new.It does not start with a plan or a design. It starts with a blank page.
- It writes the press release.About one page, written as if the product were finished, from the customer's point of view.
- It writes the FAQ.The hard questions that customers and the business would ask, with honest answers.
- The room reads.Senior meetings begin with everyone reading a written narrative in silence. No slides.

The page itself
The press release is short on purpose. One page leaves no room to hide. Here is the outline, in order. Copy it into a blank document.
- Headline
- Subheading: who it is for and what they get
- Summary paragraph
- The problem
- The solution
- A quote from a leader
- How to get started
- A customer quote
- Call to action
Notice what is missing. There is no architecture, no schedule and no list of features for their own sake. Everything is written for the person who will use the thing.
The questions you would rather skip
The press release is the hopeful part. The FAQ is where the idea gets tested. It answers the hard questions, the ones customers would ask and the ones the business would ask. A good FAQ is uncomfortable to write, because you find out where you do not have an answer.

Then comes the room. Instead of a presenter walking through slides, everyone reads the same written narrative, quietly, before anyone speaks. The discussion starts from the same page.
What it taught
Here is the point, plainly. If you cannot write a press release a customer would care about, the product is not worth building.
Most PR/FAQs never become products. That sounds like waste, but it is the method working. A page that fails costs a few days of thinking. A product that fails costs far more. The paper is where the failures should happen.
The format also takes away the usual cover. A slide can hide a weak idea behind a good layout. One page of plain sentences cannot.
Try it before your next build
You do not need Amazon's process to borrow the habit. Before your next build, do three things.
- Write the one-page press release, using the outline above, for the customer.
- Write the five hardest questions about it, and answer them honestly.
- Read it again the next day, and see whether it survives.
If it survives, you start building with a clear picture of the finish. If it does not, you have lost a page and kept the rest of your time.


