Decision Brief / PR-FAQ

Status: Documented, not shipped · Evidence: V · Family: Decision and option evaluation · Verdict: reject (2026-06-09)

What it is

The Decision Brief / PR-FAQ forces a proposal or decision into a short, structured written memo that a reader can interrogate, instead of into slides or a meeting pitch. Its most famous form is Amazon’s PR-FAQ (“press release / frequently asked questions”), the front half of the “Working Backwards” process: before any design or engineering, the author writes a one-page mock press release describing the finished product as if it had already shipped (customer, problem, solution, the headline benefit), followed by a longer FAQ that answers the hard internal questions (how it is built, the economics, the risks) and the hard external ones (price, availability, how it works). The sibling form is the Amazon six-page narrative memo: a tightly structured prose document, read in silence at the start of a meeting, that the group then discusses.

The durable move people attribute to it has two parts. First, answer-first structured written communication of a position: state the conclusion or the launched-product vision up front, then lay out the supporting case in a fixed, scannable structure a busy reader can descend into. Second, a forcing function: the claim that the discipline of writing the thing in tight prose surfaces weak thinking the author can hide in bullets and live narration. Jeff Bezos’s 2004 internal email put the second part directly - “the narrative structure of a good memo forces better thought and better understanding of what’s more important than what, and how things are related” - and the Working Backwards practitioners put the first part as the “if it is hard to write the press release, you have not done the work” test. The deliverable is a templated document (press release plus FAQ, or a structured multi-section narrative), not a diagram and not a slide deck.

When it helps / when it misleads

It helps when there is a concrete proposal to commit to or to pitch - a new product, a feature, a launch, a meaningful initiative - and the author needs to compress it into a written case a senior reader can read, challenge, and approve. The press-release framing is most at home where the proposal is genuinely a product or customer-facing offering, because the template’s questions (who is the customer, what is their problem, why will they adopt, how big is the market) are product-discovery questions. The forcing-function value is real for a model or a person who would otherwise gloss: writing the launched-state press release in one page exposes a vague customer, a missing mechanism, or an unjustified benefit fast.

It misleads or wastes effort when:

• The customer or the decision is not yet known. The template assumes you have already figured out who the customer is and what the offer is; one practitioner account of a failed attempt is explicit that he “simply didn’t know what solution appealed to them (and therefore couldn’t write it up).” Used before that, the press release becomes confident fiction. Writing a polished launch announcement for a thing you have not validated manufactures false certainty - the mock-press-release format actively rewards a persuasive story over an honest “we don’t know yet.”
• The task wants option comparison, not a single pitch. The PR-FAQ argues for one proposal in its best light; it does not lay out several real options against weighted criteria and surface the tradeoffs. For that, the move is a decision option review, not a brief.
• The work is genuinely exploratory or experiment-first. A recurring, nameable criticism is that the method over-defines up front and can lock a team into a fixed end-state when an MVP / riskiest-assumption-test loop would learn faster. The press release is a vision artifact; treated as a frozen spec, it suppresses the iteration the problem needs.
• Structure is mistaken for soundness. A clean, confident memo can make a thin case read as authoritative - the same false-authority risk every answer-first format carries. The brief composes and pressures a case; it does not certify that the case is correct.
• It is run as ritual. Filling the template for its own sake (a press release nobody will be held to, an FAQ that dodges the hard questions) delivers none of the forcing-function value and produces decision theater.

What the evidence says

The honest grade is V (vendor / single-company doctrine), revised down from the catalog’s earlier P guess. The reason is the source of the evidence, and it is the failure this library exists to prevent: laundering one company’s promoted practice into a “practitioner-validated” grade it has not earned.

What the record supports. The PR-FAQ and the six-page narrative memo are real, durable, and influential. They are documented first-hand by two former Amazon VPs in Working Backwards (Bryar and Carr, 2021) and trace to a dated, attributable internal artifact (Bezos’s 2004 “no PowerPoint” email). They are widely imitated across the product-management community. That establishes provenance and adoption - the method exists, is used, and the people who ran it report it helped.

What the record does NOT support. There is no controlled, comparative, or quantitative study I can locate showing that writing a PR-FAQ, or a narrative memo instead of slides, improves decision quality or product outcomes. Every nameable source is one of three kinds: Amazon-insider testimony (Bryar and Carr; the Bezos memo), a commercial offering built on the method (the Working Backwards consultancy and PR/FAQ template businesses), or practitioner blog write-ups whose own evidence is introspective - one careful analysis (Commoncog) states plainly that what it reports is “what do these things actually feel like, when you put them to practice,” i.e. introspection, not validation, and contains no studies or outcome comparisons. The headline anecdote (“most of Amazon’s major products since 2004 came through Working Backwards”) is uncontrolled survivorship: it counts the launches that shipped, not the proposals the format killed or the successes other companies got without it. This is why the grade is V, not P: unlike a cross-industry practitioner tool with an independent tradition, the PR-FAQ’s authority is a single company’s doctrine, promoted commercially.

The adjacent research, stated honestly. The forcing-function claim (“writing forces clearer thinking”) has a real but thin and only-adjacent research anchor. Bangert-Drowns, Hurley and Wilkinson’s meta-analysis of 48 school-based writing-to-learn interventions (Review of Educational Research, 2004) found a small positive effect on academic achievement, larger when the writing required metacognition and ran longer - so “writing to think” has measured support in principle. But that literature studied K-12 students learning academic content, not professionals making business decisions, not the PR-FAQ format, and not AI-generated memos; its own reviewers note writing helps only when it is “situationally supported and valued.” It is a plausibility anchor for the mechanism, weaker than the comprehension-research anchor behind the pyramid principle’s answer-first move, and it cannot lift the method above V.

Transfer caveat (required). All of the above is human evidence - human authors at Amazon, human students in the meta-analysis. None of it studies a brief written by or with an AI agent, or whether an agent-produced PR-FAQ improves a human’s decision. The evidence is transferred from human contexts and not validated for AI-augmented use. There is no S- or M-tier research on this move to borrow, so there is no optimistic half to cap; the grade is V on its own merits, and would not rise above P even read generously.

Why it is / is not a skill here

Verdict: Reject as a standalone thinking skill (status pm: its irreducible content belongs to the sibling pm-skills library; its generic cognitive move is already shipped as think-pyramid-principle). This is not a knock on the method’s usefulness - it is a distinctness call, and the Build burden of proof is not met.

The Build test is to name a single durable cognitive move no shipped skill produces, then show no existing skill or chain already makes it. Decompose the PR-FAQ and there are three ingredients, and none survives:

1. Answer-first structured written communication of a position - the genuine cognitive move. This is exactly think-pyramid-principle: state the governing thought first, justify it with a small ordered structure beneath, emit a scannable document a busy senior reader can descend into and challenge. The PR-FAQ’s press release is “state the outcome as if achieved, then justify”; that is the answer-first move applied to a proposal. The FAQ is grouped supporting structure under the headline. The shared working machinery - compress a position into a short, top-down, written artifact built for a busy decision-maker - is well above the ~20% overlap ceiling. The registry’s own prior note (“overlaps pyramid-principle”) was pointing at this, and it is decisive.

2. The press-release-plus-FAQ template with its customer / problem / adoption / market questions - the part that makes a PR-FAQ a PR-FAQ rather than a generic memo. But that is a product-management domain artifact: its questions are product-discovery questions (who is the customer, what is the job, why adopt, how big is the market). The library already routes product-discovery methods to pm-skills (opportunity-solution-tree, value-proposition-contrast, jobs-to-be-done are all pm or flag). A launch-press-release template is squarely that domain, not a general reasoning move.

3. The forcing function (“if it is hard to write, you have not done the thinking”) - the most distinctive-sounding claim, and the only candidate for an orthogonal move. But it is not a separable cognitive operation; it is a general property of writing-to-think (the small-effect, conditional Bangert-Drowns literature), and the library already realizes “write the position down in an inspectable structure so the gaps show” through think-pyramid-principle and, for assumptions specifically, think-what-would-have-to-be-true. A forcing function is a benefit of structured writing, not a method that emits its own distinct artifact.

So the cognitive core is pyramid-principle and the distinctive wrapper is pm-domain - which is precisely the two-failure pattern (a near-twin of a shipped move, dressed in another library’s domain content) the selection bar rejects.

Why not the other listed neighbors. think-decision-option-review is low overlap, not a fold home: it compares several real options on weighted criteria and surfaces tradeoffs; the PR-FAQ pitches one proposal and does not. That difference also means the PR-FAQ does not add option-comparison, so it cannot earn its place there either. think-decision-journal is low overlap: it captures a decision plus a dated prediction and explicit confidence for later calibration; the PR-FAQ is a forward pitch with no recorded prediction-to-be-scored. Neither rescues a Build.

Why pm rather than excl or a clean fold. It is not excluded on the merits - it is a genuinely useful method - so excl would misread it. It is not a clean fold-into-pyramid either, because what is left after you remove the pyramid move is not nothing: it is the product-launch template, which is real and belongs somewhere - in pm-skills. Tagging it pm records both truths at once: the thinking move is already shipped (pyramid-principle), and the part that is distinctively a PR-FAQ is product-domain. The learning value of the decision: a celebrated, heavily promoted format can still fail the bar twice over - its reasoning core duplicates a shipped skill, and its distinctive remainder is another library’s domain - and “famous and useful” is not the same as “a distinct, evidenced, in-scope thinking move.”

Lineage and who to read

The PR-FAQ and the narrative-memo culture are Amazon’s, originating under Jeff Bezos: the foundational artifact is his June 2004 internal email banning PowerPoint in favor of “well structured, narrative text,” with the rationale that “the narrative structure of a good memo forces better thought.” The definitive account is Colin Bryar and Bill Carr, Working Backwards: Insights, Stories, and Secrets from Inside Amazon (2021) - both were Amazon VPs (Bryar was Bezos’s “shadow”/technical advisor) - which documents the Working Backwards process and the PR-FAQ as its starting artifact. For the practice and an honest practitioner critique, read Cedric Chin’s Commoncog analysis (which both applies the method and reports where it broke for him). For the forcing-function mechanism’s research footing, read Bangert-Drowns, Hurley and Wilkinson’s writing-to-learn meta-analysis - and read it as the bounded, small-effect, K-12 finding it is, not as validation of the PR-FAQ. “PR-FAQ,” “Working Backwards,” and “six-page memo” are descriptive practitioner terms rather than registered marks, though the method is closely identified with Amazon and is commercialized through books and consultancies; attribute it to Amazon / Bezos / Bryar and Carr.

Named sources

• Colin Bryar and Bill Carr, Working Backwards: Insights, Stories, and Secrets from Inside Amazon (St. Martin’s Press, 2021). The primary first-hand documentation of Working Backwards and the PR-FAQ, by two long-tenured Amazon VPs. Insider testimony, not a controlled study. (V)
• Jeff Bezos, internal Amazon email, June 2004 (“No PowerPoint presentations from now on”), widely reproduced (e.g. CNBC, 2018). The dated origin artifact and the canonical statement of the forcing-function rationale (“the narrative structure of a good memo forces better thought”). Primary doctrine. (V)
• Cedric Chin, “Putting Amazon’s PR/FAQ to Practice,” Commoncog. Practitioner analysis that applies the method and names real failure modes (customer-uncertainty assumption, over-scoping, emotional resistance); explicitly introspective (“what these things feel like in practice”), with no outcome study. (V / practitioner)
• Robert L. Bangert-Drowns, Marlene M. Hurley, and Barbara Wilkinson, “The Effects of School-Based Writing-to-Learn Interventions on Academic Achievement: A Meta-Analysis,” Review of Educational Research 74(1) (2004): 29-58. Meta-analysis of 48 K-12 studies: a small positive effect on achievement, larger with metacognitive prompts and longer exposure. The honest, adjacent anchor for “writing forces thinking” - not a test of the PR-FAQ, business decisions, or AI use. (M for what it actually measured; adjacent, so it does not lift this method’s grade)
• workingbackwards.com / PR-FAQ template businesses. Commercial offerings built on the method; useful as template references, but vendor sources whose claims are not independent validation. (V)

Excluded on the evidence rule: the often-cited “most of Amazon’s major products since 2004 came through Working Backwards” is uncontrolled survivorship (it counts shipped launches, not killed proposals or non-Amazon successes) and is not counted toward the grade. No traceable primary source provides a controlled effectiveness figure for the PR-FAQ; none is used.