PR/FAQ: Amazon product management format explained

A PR/FAQ is a two-part document: a one-page fictional press release written as if the product has already launched, followed by a FAQ section split into external questions (what customers will ask) and internal questions (what leadership must answer before approving investment). Jeff Bezos originated the format in the early 2000s when he banned PowerPoint at Amazon and required all proposals in narrative prose. It forces the author to name a specific customer, a specific problem, and a specific outcome before a dollar is spent.

The press release section

Six elements, in order: heading (product name and who it is for), subheading (benefit in one sentence), summary paragraph, problem paragraph from the customer’s perspective, solution paragraph(s) with competitive differentiation, and a quote block with one company quote, one hypothetical customer quote, and a call to action. No charts, images, or bullets.

The customer named in the subheading must be specific. “Small business owners” fails. “Maria, who runs a 12-person furniture studio and loses six hours a month reconciling supplier invoices” passes. If every sentence could appear in a press release for a different product, the author has not done the work.

The FAQ section

External FAQs answer what a customer or journalist would ask at launch: how it works, what it costs, how it differs from alternatives, how to start. Typically 5 to 10 questions with publicly defensible answers.

Internal FAQs are where most candidates fail. They must cover:

What solutions customers use today and why those fall short
TAM calculation and whether the payback justifies investment
Top three failure risks: the specific bets that could be wrong
Capabilities the company or team currently lacks
Business dependencies: partners, platform agreements, data access
Regulatory, legal, or privacy constraints
Unit economics at scale

If every internal FAQ has a positive answer, the author has not done the work. Interviewers describe these submissions as “a sales pitch, not a product document.” Some products required multiple PR/FAQs: Fulfillment by Amazon used two documents, one for sellers and one for buyers, because the economics and problems differ fundamentally for each customer type.

How Amazon evaluates the written submission

The 2026 interview loop written assessment is 2 to 3 pages, due within 48 hours, with no charts or images (rejection if included). Reviewers score on four dimensions: example relevance, logical structure, leadership principle alignment, and data-grounded reasoning. The seven evaluation questions are:

Is the customer clearly defined?
Is the problem clearly defined?
Does the solution address the stated problem?
Would customers change their current behavior to adopt it?
How is it better, cheaper, or faster than alternatives?
Is the TAM and payback period sufficient?
What constraints must be solved before this ships?

Questions 4 and 6 trip the most candidates. One underdeveloped internal FAQ can sink an otherwise strong submission.

The meeting format

At Amazon, documents are not pre-read. The PR/FAQ is circulated at meeting start. Attendees read silently for 15 to 20 minutes, then debate for 40 minutes. PMs who write for top-line presentation rather than sustained analytical reading produce documents that fall apart under adversarial cold-read scrutiny.

PR/FAQ vs PRD

A PRD documents how a decided product will be built. A PR/FAQ precedes that decision: it is a structured argument that the product is worth building at all. Conflating them signals the candidate does not understand the working-backwards sequence. For the full framework, see working backwards.

The 2026 reframe

Bezos created the PR/FAQ when feasibility was the constraint. In 2026, agentic coding tools produce a working demo faster than a complete six-page PR/FAQ. Amazon’s own reporting described this as “upending” the working-backwards tradition. That makes the document more important, not less, but the weight shifts entirely.

The press release still requires a specific customer and a specific outcome. The internal FAQ’s hardest questions are no longer about buildability. They are about viability (will people pay for this, is the market large enough?) and lovability (will they change behavior to use it rather than their current approach?). For AI-native products, the top three failure risks are almost never technical. They are behavioral adoption, willingness to pay, and regulatory exposure. Amazon Connect’s 2026 expansion into four agentic AI products originated through the working-backwards process; the PR/FAQs had to make the case for viable markets and behavior change, not build feasibility.

A PM who writes a tight internal FAQ for an AI product, one that honestly addresses TAM, unit economics, and top failure risks, is proving they can hold the viable/lovable bar when build cost has collapsed. That is what AI-era Amazon interviewers are testing.

strong

"A PR/FAQ has two parts: a fictional press release written from the customer's perspective as if the product shipped, and a FAQ split into external and internal sections. The internal FAQ is where the real work lives: TAM and payback, unit economics, the top three failure risks, capabilities the team lacks, and regulatory exposure. If every internal FAQ answer is positive, I haven't done the work. For an AI product, the hard questions are viability and behavior change, not buildability. I'd also flag the meeting format: no pre-reading, 15 to 20 minutes of silent reading at meeting start, then 40 minutes of challenge. The document has to hold up analytically."

weak

"A PR/FAQ is a press release you write before building, plus some FAQs. It helps you think customer-first." This misses the internal FAQ entirely, says nothing about TAM or failure risks, and treats the document as a marketing artifact. Interviewers describe submissions like this as "a sales pitch, not a product document." The tell: every FAQ has a positive answer.

For the viable/lovable lens on AI products, see feasibility is free and proving viability. For the document that follows the PR/FAQ in the build sequence, see PRD.