Amazon 6-Pager & PR/FAQ

The 6-pager and the PR/FAQ are Amazon's two signature decision documents. Together they replaced PowerPoint in most Amazon meetings starting in the early 2000s, and have since been adopted by companies like Coinbase, Shopify, Dropbox, and many others. They are less about formatting and more about a discipline: force the author to think, force the reader to engage deeply, and work backward from the customer.

Origin

Jeff Bezos banned PowerPoint from S-team meetings in 2004 with an internal email that included this line: "The reason writing a good 4-page memo is harder than writing a 20-page PowerPoint is because the narrative structure of a good memo forces better thought." The memo length grew to 6 pages as a cap on length, not a target. The PR/FAQ format emerged alongside as the required starting point for any new product or feature: write the press release first, then the FAQ, and if either is weak, do not build the thing.

The two formats embody Amazon's "working backwards" principle: start from the customer's experience and work backward to what must be true for it to exist.

The Frameworks

A 6-pager is a 6-page (max), single-spaced, narrative document describing a decision, proposal, or status review. It is read in silence at the start of the meeting — typically 20-30 minutes — then discussed.

Common structure (varies by topic):

1. Summary / TL;DR        (1 paragraph, the decision being asked for)
2. Background / Context   (what's the world, what's the problem)
3. Analysis               (data, alternatives, tradeoffs)
4. Recommendation         (what we should do and why)
5. Risks & Mitigations    (what could go wrong, how we handle it)
6. Appendix               (supporting data, deep detail, FAQ)

The silent read is a non-negotiable ritual:

- Meeting starts on time, full attendance
- Everyone reads the document in silence
- Typically 20-30 minutes depending on density
- No phones, no laptops for other work, no "I'll read it later"
- After reading, discussion begins — not before

The silent read is radical because it solves two pervasive problems: people who do not read the pre-read, and people who talk over people who did.

The PR/FAQ

A PR/FAQ is the document you write before you build anything. It has two parts:

Part 1: Press Release (1 page)
  - Headline:        What the product is called
  - Subheadline:     Who it is for and what it does
  - Summary:         The customer problem and our solution
  - Problem:         The pain point in the customer's voice
  - Solution:        How the product solves it
  - Leader quote:    Internal executive on why this matters
  - Customer quote:  A fictional (but realistic) customer on why they love it
  - How to get it:   Call to action

Part 2: FAQ (3-5 pages)
  Internal FAQ:   What will skeptics inside the company ask?
                  (How much will it cost? Why now? Who is the team?)
  External FAQ:   What will customers ask?
                  (How do I use it? What does it cost? How is it different?)

The PR/FAQ tests whether the product is worth building before anyone commits capital or effort. If the press release is not compelling, the product is not compelling.

How to Use It

1. Write a skeleton in bullets. Spend 30 minutes here.
2. Convert bullets into narrative prose. The transition from bullets
   to sentences forces logic gaps to surface.
3. Cut ruthlessly to fit in 6 pages. Brevity is forcing function.
4. Have someone read it cold — if they need clarification, the doc is
   not ready.
5. Anticipate the top 10 questions in an appendix FAQ.

1. Everyone arrives on time.
2. The author does not "walk through" the document. It stands alone.
3. Silent read (20-30 min). Attendees can mark up paper or take notes.
4. Discussion starts, structured around:
   - Questions / clarifications
   - Concerns / disagreements
   - Decisions / next steps
5. Author captures decisions and follow-ups in writing before adjourning.

Writing a PR/FAQ

1. Write the headline and subheadline in the customer's language.
   If you cannot describe the benefit in 10 words, you do not have one.
2. Draft the customer's pain point as a direct quote. Use their actual
   words from interviews or support tickets.
3. Write the solution as if it ships tomorrow. Specific. Tangible.
4. Work backward: what must be true for the PR to be writable truthfully?
   Those are the requirements.
5. Stress-test with the FAQ. If you cannot answer the hard questions,
   the product is not ready to build.

Tech & Company Example

A fintech company is considering launching a new "bill pay" feature.

PR/FAQ (excerpt):

  Headline: FinCo Launches Bill Pay — Pay Every Bill from One App

  Subheadline: FinCo customers can now pay utility, credit card, and
  rent bills directly from their FinCo account, with automatic reminders
  and no fees.

  Summary: Until today, FinCo customers paid bills through a mix of
  their bank's website, their biller's website, and paper checks.
  Starting today, any bill with a US mailing address or account number
  can be paid from FinCo in under 30 seconds. Payments are free,
  reminders are automatic, and the first 90 days are backed by a
  "missed bill guarantee."

  Customer Quote (fictional but realistic):
  "I was paying my electric bill at my bank, credit card at a separate
  site, and rent via paper check. Now it's all in FinCo. I haven't
  missed a bill since switching." — Elena R., FinCo customer since 2022

  Internal FAQ:
  Q: What is the expected cost to run this?
  A: ~$0.18 per payment (ACH + reminder infra). Gross margin neutral
     at current free tier; we monetize via adjacent features (float,
     credit products).

  Q: Why now?
  A: Our data shows 68% of customers have at least one recurring
     external payment. Competitors X and Y launched similar features
     in Q2; our internal NPS cited bill management as top pain point.

  External FAQ:
  Q: Is there a fee?
  A: No. Bill Pay is free for FinCo customers.

  Q: How long do payments take?
  A: 1-2 business days via ACH. Same-day option coming in 2024-Q4.

The team writes this before the roadmap. If leadership rejects the PR/FAQ, 6 months of work is saved. If it is approved, the team has a customer-centric North Star for the build.

When It Works

New product or feature decisions (PR/FAQ)
Strategy, investment, or roadmap reviews (6-pager)
Cross-functional decisions with multiple stakeholders
Operational reviews (Amazon's famous WBRs — Weekly Business Reviews)
Organizations willing to invest in writing culture

When It Does Not Work

Cultures without reading discipline (the silent read fails)
Pure-engineering decisions (RFC/ADR are better fits)
Time-critical decisions (6-pagers take days to write well)
Small teams where a conversation would suffice
Environments where writing is low-prestige or seen as ops overhead

Common Failure Modes

"PowerPoint in prose" — bullets linked by "therefore" and "furthermore" but without actual narrative logic
Vague TL;DR — a first paragraph that does not state what decision is being asked for
Defensive appendix — 40 pages of appendix to "cover" all questions, defeating the point of brevity
No silent read — the author walks through slides disguised as a memo, losing the entire benefit

PR/FAQ Failures

Aspirational quotes — customer quotes that are too polished; they read like marketing copy, not real users
Feature-list PR — press releases that are actually feature announcements with no customer benefit
Soft FAQ — internal FAQ that ducks the hard questions (cost, cannibalization, competitive response)
Fictional numbers — estimates presented as facts; be explicit about confidence levels

Meta-Failures

Ritual without rigor — Adopting the format without the underlying culture. A 6-pager read by skimmers, discussed superficially, is worse than a good PowerPoint.
Author apology — Opening the discussion with "sorry for the length" or "this is a rough draft" undermines the document. If it is not ready, do not hold the meeting.

2-pager / 1-pager — Shorter variants for smaller decisions. Same principles, less space.
Working Backwards — The broader Amazon principle; PR/FAQ is its written expression.
RFC / Design Doc — Technical cousin of the 6-pager; more implementation-heavy, less customer-focused.
Minto-structured 6-pager — Some teams combine the two: Minto-style hierarchy inside a 6-page narrative.
Pre-FAQ — The FAQ without the press release; used when a product already exists but needs clarification.