Amazon PRFAQ vs. Six-Pager (Format Guide)

A PRFAQ starts with a proposed customer benefit, then uses questions to test the idea. A Six-Pager builds a connected argument for a broader strategy or decision. Choose based on the decision you need, not a presumed Amazon-wide rule: practices vary by team. In either format, show evidence, label assumptions, explain risks, and state the decision requested.

What should you write when you have a promising idea but need others to judge its value, risks, and cost? The answer depends on what you are asking them to decide. A customer-facing product proposal and a broader strategy may need different kinds of explanation.

I use one test first: Can a reader tell who the decision is for, what is known, what is still uncertain, and what action is being requested? If not, changing the format will not fix the argument.

Purpose and audience: when to use each format

A PRFAQ works backward from a proposed customer outcome. It opens with a hypothetical announcement of the offer and its value, then uses questions to examine concerns and assumptions. A Six-Pager is a connected narrative for a broader argument, such as a strategy, operating plan, or decision proposal.

Use a PRFAQ when you need to make a customer-facing offer clear and test whether it solves a meaningful problem. The imagined press release forces the team to describe the offer in plain language. The FAQ then gives space to challenge the idea: Who would use it? What would it replace? What could go wrong?

Use a Six-Pager when the decision needs a wider explanation. For example, a plan to change how several teams operate may depend on costs, staffing, timing, and trade-offs that do not fit naturally into a launch announcement. A narrative can connect those points and show how they support the requested decision.

Neither format guarantees customer value or sound strategy. Both are prose-first tools, not slide decks. Amazon has publicly discussed narrative documents and silent reading at some meetings, but that does not make one meeting routine or template a rule for every team. Check the local expectations.

Takeaway: Start with the decision and audience. If the central question is “Would this offer solve a customer problem?”, begin with a PRFAQ. If it is “Should we adopt this plan, and why?”, consider a Six-Pager.

Structure, evidence, and required components

A document structure is a sequence that helps readers follow the reasoning. Evidence is the support behind each claim, such as customer feedback, usage data, or cost estimates. In either format, distinguish observed facts from estimates and hypotheses so that readers can judge how strong the case is.

What to include in a PRFAQ

A PRFAQ usually begins with a hypothetical press release. Treat it as a clear description of the proposed customer experience, not proof that the product exists or will launch. State who it serves, what problem it addresses, what the customer can do, and what benefit the team expects.

Then write FAQs that probe the offer from different angles. A useful set may cover:

• Customer need and evidence for it
• How the proposed experience works
• Alternatives customers use today
• Pricing or cost, if relevant to the decision
• Technical and operational dependencies
• Risks, limitations, and unresolved questions
• Measures that would indicate success

The FAQs should not be a place to hide weak evidence. If customer demand is a hypothesis, say so. If a cost estimate has not been checked, label it as preliminary and name what must be done to improve it.

What to include in a Six-Pager

A Six-Pager presents one argument in a readable sequence. A practical structure is:

1. Decision and context: State the choice readers need to make and why it matters now.
2. Problem and evidence: Define the issue and show what supports that definition.
3. Options: Describe realistic alternatives, including the choice to do nothing.
4. Recommendation: Explain why the preferred path is stronger for this situation.
5. Costs, risks, and dependencies: Show what could limit or change the plan.
6. Execution and measures: Name owners, milestones, and ways to check progress.

“Six-Pager” is a name, not a universal public page-count rule. Amazon teams and other organizations may set their own length, format, or review rules. Do not compress important reasoning just to meet a number unless your team requires it. Ask for the current standard before drafting.

Takeaway: In both documents, make the problem, evidence, alternatives, risks, and requested decision easy to find. A clean format cannot replace a clear argument.

A practical drafting and review workflow

A drafting workflow is a set of steps for moving from a decision question to a review-ready document. It helps teams find missing evidence before a meeting, rather than relying on polished language to cover gaps. Keep the audience, local rules, and uncertainty visible at each step.

1. Define the decision. Write one sentence naming the decision-maker, the choice, and the deadline or event that makes the choice relevant. Identify the target customer if the proposal is customer-facing.
2. Choose the format. Use the PRFAQ when the proposed offer and customer outcome are the center of the case. Use a Six-Pager when the reader needs a wider narrative to weigh a strategy or operating choice.
3. Build an evidence list. For each major claim, record its source and status: observed fact, estimate, or hypothesis. Include the date and scope when they affect interpretation. Avoid presenting a small or narrow sample as proof of broad demand.
4. Draft the core argument. For a PRFAQ, write the announcement and then ask what a skeptical reader would need to know. For a Six-Pager, connect the problem, options, recommendation, and execution plan.
5. Challenge the draft. Ask a reviewer to mark unsupported claims, missing alternatives, unclear terms, and risks without an owner. Invite them to state the decision they believe the document requests. If their answer differs from yours, revise.
6. Prepare for the local review. Confirm the required template, length, deadline, and reading time with the meeting owner. Amazon has publicly described silent reading of narrative documents at some meetings, sometimes for up to 30 minutes; do not assume that timing applies to your review.
7. Close the loop. Record the decision, open questions, owners, and next review point. A document that does not say who will do what after the meeting may leave the decision hard to execute.

A useful review check is to inspect every important number. What period does it cover? Is it actual or projected? What assumptions drive it? There is no universal pass score for a PRFAQ or Six-Pager. Set success measures that fit the proposal and agree on them before treating early results as proof.

Takeaway: The goal is not to produce a document that sounds certain. It is to make the decision and the strength of the evidence clear.

Worked examples and common failure modes

A worked example shows how a format can fit a decision; it does not establish a real Amazon project or outcome. The scenarios below are hypothetical. I use examples like these to help teams see where a document’s center of gravity belongs before they invest time in a full draft.

Hypothetical product proposal: A team is considering a service that helps customers track a delivery change. A PRFAQ can describe the proposed customer experience, then test questions about demand, data accuracy, support needs, and failure cases. If customer research has not yet been done, the document should say that the need is not validated.

Hypothetical operating proposal: A company is considering a new process shared by several departments. A Six-Pager may better explain the current problem, options, staffing needs, costs, risks, and rollout steps. A press-release opening could make the change sound like a finished customer offer when the main decision is actually about internal operations.

Watch for these common failures:

• Format mismatch: A PRFAQ may imply launch readiness that evidence does not support. A Six-Pager may become a long proposal without a specific decision.
• Claims without sources: Broad statements about customer demand need evidence or a clear label as a hypothesis.
• No real alternatives: A recommendation is hard to judge if readers cannot see what else was considered.
• Hidden trade-offs: State what the proposal may cost, delay, or make harder, as well as what it may improve.
• Unclear ownership: Name who will resolve open questions and who will track milestones.
• Metrics without meaning: Define how a measure is calculated, its baseline, and when it will be reviewed. Set targets with the people responsible for the work; do not borrow a universal threshold.

Takeaway: A strong document can make an uncertain proposal easier to test. It should not make uncertainty disappear.

Choose, draft, and review with a clear decision in view

The best format is the one that makes the decision easier to understand and test. A PRFAQ gives a customer-facing proposal a concrete shape and exposes questions around it. A Six-Pager gives a broader case room to connect evidence, trade-offs, and execution.

Before you write, check the team’s current standards. Then write for the reader who must decide, not for a page-count target or a familiar template. Make the evidence limits plain, name the risks, and finish with a specific request. Those habits matter more than the label on the document.

Frequently asked questions

These short answers address common format and review questions. Local practices can differ, so use them as a starting point rather than as an official Amazon-wide template. When a team has a current standard, follow it and ask the meeting owner about anything unclear.

What is the main difference between a PRFAQ and a Six-Pager?

A PRFAQ begins with a hypothetical customer-facing announcement and follows with questions about the offer. A Six-Pager presents a connected argument for a broader strategy, plan, or decision.

When should I use a PRFAQ?

Use a PRFAQ when the main task is to describe a proposed customer offer and test whether its value, assumptions, and risks are clear.

When should I use a Six-Pager?

Use a Six-Pager when readers need a broader narrative to assess a strategy, operating plan, or decision with several trade-offs and dependencies.

Is a Six-Pager always exactly six pages?

No universal public page limit applies across all Amazon teams. Confirm the length and format expected by the team reviewing your document.

Does every Amazon meeting use silent reading?

No. Amazon has publicly described silent reading at some meetings, but practices vary. Ask the meeting owner how much reading time is planned and when to submit the document.

Can a PRFAQ be used before customer research is complete?

Yes, if the evidence limits are clear. Label untested customer needs as hypotheses, and explain what research or test would help validate them.

Should a PRFAQ include a launch date?

Only if the date is relevant and supported by the proposal’s readiness and local review process. Do not let a hypothetical announcement make a tentative idea sound committed.

What should both formats include?

Both should make the audience, problem, evidence, assumptions, alternatives, risks, and requested decision explicit. Add owners, milestones, and success measures when the decision involves execution.

How do I avoid writing a Six-Pager with no clear ask?

State the decision near the start and restate it at the end. Make clear which option you recommend, what approval or input you need, and what happens next.

Which format is better for an early-stage idea?

Choose based on the question being tested. A customer offer may suit a PRFAQ; a broader resource or strategy choice may suit a Six-Pager. In either case, mark open questions and avoid implying certainty.

(This article was written by one of our staff writers, James Holloway. Visit our Meet the Team page.)