Skip to content
Discovery WaypointDecision-ready discovery
Start WorkspaceSign in
Start Workspace
Sign in
Amazon

Amazon Working Backwards

Borrow the artifact · Primary + examples

Amazon PRFAQ / Working Backwards

Borrow the customer-forcing narrative artifact and the review discipline around it, not the mythology of Amazon memo culture wholesale.

Best opened when

Concepts that need customer-facing clarity before roadmap commitment.

What to steal first

The future press release and the five hardest FAQ questions.

What not to copy

It is not a branding exercise or a substitute for real customer evidence.

Closest move

Concept Poster / Concept Cards

Core artefact

What the document is actually for

The PRFAQ is a two-part internal document: a future-tense press release written as if the product has already launched, followed by a set of hard questions and answers. At Amazon it existed because narrative clarity was the filter. A concept that could not survive being written as a customer-facing announcement — and interrogated by its own FAQ — was not ready for investment.

The part that transfers is not the format. It is the forcing function. The press release demands that you express customer value in specific language before you have built anything. The FAQ demands that you name the hard objections before the room politely ignores them.

What does not transfer: the length, the Amazonian writing bar, the six-page format, and the review ceremony. Strip to the future-state customer narrative and the five hardest questions.

Use it in a session

A clean first pass you can run

Participants
The concept owner who drafts the documents, and 2–4 reviewers who will ask hard questions. Not collaborators — critics. The review session should feel uncomfortable.
Timing
30–45 minutes alone to draft the press release and FAQ. A separate 60-minute review session with reviewers who have read both documents before the meeting starts.
Prep
Draft the press release and FAQ independently before showing them to anyone. The FAQ should contain a minimum of five questions, each one harder than the last. If writing the FAQ feels comfortable, the questions are too soft.
  1. 1Write the press release in future tense. Name the customer specifically. State the problem they had. State what the product did. State why it matters to them — not why it matters to the business.
  2. 2Read it aloud before the review. If it sounds vague or aspirational rather than specific, rewrite it. The press release should be embarrassing to defend with hand-waving.
  3. 3Write the FAQ. Lead with the question you least want to answer. If the FAQ starts with easy questions, you are writing for comfort, not for clarity.
  4. 4Share both documents before the review session. Reviewers read silently. The review session starts with questions, not with a presentation.
  5. 5Check the revision: has the customer value claim changed since the first draft? If the document is identical after review, the review was too polite or the questions were too soft.

You leave with

A press release and FAQ where the hardest customer-value questions have been answered — not avoided or deferred.

First failure point: The review session starts with the author presenting the document rather than reviewers asking questions about it. Presentation mode disables critique mode.

What good looks like

If this is working, these are the signals you should be able to point to

  • The concept narrative changed significantly between the first draft and the version after review.
  • The FAQ section contains at least five questions nobody wanted to answer.
  • The review session opened with reviewers asking questions, not the author presenting.
  • The customer value claim is specific enough that two people can independently judge whether it is true.

How it worked there

The conditions that made it hold

The method worked at Amazon because written clarity was the credibility signal. Senior leaders read the document before the meeting started. The meeting's job was critique, not orientation. A presenter who could not hold their PRFAQ under five minutes of hard questions was not ready to be funded.

The organizational conditions this required: leaders who genuinely read before reacting, a writing culture where vague language was criticized rather than tolerated, and a review process with enough authority to say no. Most adopting organizations have one of these three. They rarely have all three.

What not to copy · Failure modes

What goes wrong when this is copied

The press release becomes aspiration theater. Teams write it as a marketing exercise — optimistic, audience-pleasing, soft. The FAQ answers the questions the author wants to be asked, not the ones that would stop the concept.

The format is imported without the review culture. The memo becomes a compliance artifact. No senior person reads it closely. No one challenges the FAQ claims. The document does not improve because critique does not happen.

It substitutes for customer evidence. The concept is not validated with real users because the PRFAQ already articulates what users want so compellingly. The articulation is mistaken for evidence.

Weak signals to watch for

  • It is not a branding exercise or a substitute for real customer evidence.
  • It is not a substitute for opportunity framing or evidence gathering when those are still weak.
  • Do not import the memo format without the review discipline.
  • Do not assume the artifact recreates Amazon’s culture, incentives, or writing bar.

Closest Waypoint move

What to open next

Primary route

Concept Poster / Concept Cards

Use Waypoint’s lighter narrative artifact when you need the customer-facing discipline without importing a heavier memo ritual.

Use this when you need the customer-facing narrative discipline and can accept a lighter document structure than the original six-page memo.

Sources and confidence

Primary + examples

Reviewed by Discovery Waypoint Editorial Team · 2026-04-04