Working Backwards
We try to work backwards from the customer, rather than starting from what we're good at making and figuring out where to sell it. Working backwards from customer needs often demands that we acquire new competencies and exercise new muscles, never mind how uncomfortable and awkward-feeling those first steps might be.
Working Backwards is Amazon's customer-obsessed product development methodology, codified by Colin Bryar and Bill Carr from their years inside Amazon. Instead of starting with available technology or internal capabilities, teams write a fictional press release announcing the finished product — from the customer's point of view — before a single line of code is written. This PRFAQ discipline forces rigorous clarity on who the customer is, what problem they have, and why the solution matters, eliminating costly pivots later.
“We want to build an AI-powered expense reporting tool for finance teams. We have the ML infrastructure already, so we figured we could…”
Write the press release before you write the code — start at launch day
Working Backwards centers on the PRFAQ — a Press Release plus Frequently Asked Questions document — written before development begins. The press release has eight prescribed sections (heading, subheading, summary, the problem, the solution, an internal leader quote, a getting-started description, and a customer testimonial quote) and must be written entirely from the customer's perspective in plain language. Paired with it are External FAQs (questions real customers would ask) and Internal FAQs (business, cost, risk, and dependency questions). A separate artifact — the Six-Pager Narrative Memo — replaces PowerPoint for every significant meeting or proposal; attendees read it in silence before discussion begins ('the study hall'). The methodology also defines Single-Threaded Leadership, where every initiative is owned end-to-end by one undistracted person, and prescribes tracking input metrics (the leading indicators teams control) rather than output metrics (lagging results).
Most product teams build what they can build, then look for customers — a pattern Bryar and Carr call 'working forwards.' The result is roadmaps driven by engineering availability, features nobody asked for, and expensive late-stage pivots when the product reaches real users. Without a forcing function that makes teams articulate the customer's problem and the emotional payoff of the solution before any resources are committed, strategy documents remain vague and alignment stays shallow.
By writing the press release first, you lock in a customer-first definition of success that every stakeholder has reviewed and approved — so the team builds toward a concrete launch narrative, not a moving target.
- A product idea, feature proposal, or initiative you want to define
- A description of the target customer and the problem they face (even a rough one)
- Any business constraints or context relevant to the Internal FAQ (cost assumptions, team size, timeline)
- An existing spec, deck, or brief you want to convert into Working Backwards format
- A complete, section-by-section PRFAQ document ready for stakeholder review
- An External FAQ that anticipates real customer objections and questions
- An Internal FAQ that surfaces business risks, P&L assumptions, and operational dependencies
- A Six-Pager Narrative Memo suitable for a strategy meeting or leadership review
- A mapped list of input metrics you can directly control, separated from lagging output metrics
Watch the methodology work.
Three specimens from a single real session: the same situation, unaided and calibrated, the full transcript, and the skill answering live in the channel where the work happens.
“Your team has a compelling product idea and a capable engineering team. You've written a 15-slide deck with a market opportunity slide, a feature list, and a go-to-market section. The slides look polished, but in the review meeting three executives ask three different questions about who the target customer actually is — and you realize nobody's written it down in a sentence anyone agrees on.”
“After a Working Backwards session, you have a one-page PRFAQ with a customer testimonial section that reads: 'I used to dread month-end close. Now I open it like any other morning.' Every stakeholder has reviewed and marked up the document before a sprint was planned. Your Internal FAQ has forced you to write down the build cost estimate and the biggest technical risk — in writing, with mitigations. The team is building toward a specific launch announcement they can all recite.”
The same skill, where the work happens.
No new app to learn. The methodology runs over the WhatsApp Business API, so the answer lands as a reply in the thread you’re already in — same rigour, zero context-switch.
What it does, specifically.
Each capability is a distinct move drawn straight from the source methodology — not a generic assistant guessing.
PRFAQ Builder
Guides you section by section through the full PRFAQ document: heading, subheading, summary, the problem paragraph, the solution paragraph, the internal leader quote, the getting-started description, and the imagined customer testimonial. Each section is reviewed against Bryar's standards — plain language, customer perspective, no jargon — before moving to the next.
Working-Forward Detector
Analyzes your product idea or existing spec to identify 'working-forward' assumptions — places where the logic starts from a capability, technology, or business constraint rather than from a customer need. Reframes each one using the customer-back lens.
Six-Pager Narrative Workshop
Helps you write a complete Six-Pager Narrative Memo — Amazon's required format for meetings, proposals, and strategy reviews — structured as full prose paragraphs that build a coherent argument, not bullet-point slides. Includes coaching on the silent 'study hall' reading protocol for distributing the memo in meetings.
External & Internal FAQ Drafting
Separately drafts the two FAQ sections of the PRFAQ: External FAQs anticipate real customer questions about pricing, availability, and how the product works; Internal FAQs surface the hard business questions — estimated cost to build, P&L implications, organizational dependencies, risks, and mitigation plans.
Input Metric Identification
Works with you to define the input metrics — the leading-indicator activities your team directly controls — and distinguish them from output metrics (revenue, NPS, retention) that are lagging results you can only influence. Maps controllable inputs to each desired output.
Graded before it shipped.
Every skill is scored against independent scenarios for methodology fidelity before it goes live — not vibes, a rubric.
Working Backwards PRFAQ Document
A complete, submission-ready PRFAQ with all eight press release sections plus annotated External and Internal FAQ sections — formatted so it can be dropped directly into a team review or stakeholder approval process.
Six-Pager Narrative Memo
A full narrative prose memo covering the strategic situation, proposed approach, key tradeoffs, and recommended decision — structured for a silent-read meeting opening and written to stand alone without the author presenting it.
Input vs. Output Metrics Map
A structured table separating the metrics your team can directly control (inputs) from the lagging outcomes you're trying to move (outputs), with suggested tracking cadences and owners for each input.
Single-Threaded Owner Charter
A one-page charter defining the scope, decision rights, success criteria, and resource commitments for a Single-Threaded Owner (STO) leading a new product initiative — built to clarify accountability from day one.
Grounded in the original work.
Every answer traces back to a real source and the practitioner who wrote it — not a secondhand summary. Here is the source of record.
Colin Bryar
Colin Bryar served as Jeff Bezos's Chief of Staff and Technical Advisor — Amazon's 'shadow' role — from 2003 to 2005, giving him a front-row seat to how Amazon's core management practices were forged and applied. He subsequently led multiple Amazon divisions before leaving to co-author 'Working Backwards' (2021) with former Amazon VP Bill Carr. The book draws on insider case studies including the launches of Amazon Prime, Kindle, and AWS.
Working Backwards: Insights, Stories, and Secrets from Inside Amazon
Be first to run it.
Working Backwards is being built right now. Leave your email and we’ll tell you the moment it goes live.