📘 How do you write a brief before you build?
Problem, evidence, and constraints—how a brief makes being wrong cheap before two sprints are reserved.
What you’ll learn
- Why a Brief ExistsExplain why a short written brief is the cheapest place to be wrong, and how narrative writing surfaces a bet before anyone builds.A product brief aligns a team on the problem and the bet before expensive work. Bezos banned S-Team slide decks on 9 June 2004 and kept six-page narrative memos as the meeting artifact; McAllister described the related PR/FAQ in 2012. Short is a tax on the writer. The page is a living proposal, not a contract.
- Anatomy of a BriefIdentify the sections of a brief and the decision each one supports, with the credits for JTBD, job stories, SMART, and the North Star kept straight.Cagan's 2006 ten questions are the skeleton: problem, who, size, alternatives, why us, why now, go-to-market, metrics, what must be true, go or no-go. A one-pager folds those into problem and evidence, user and job, goals, scope and non-goals, risks, a light approach, and open questions. Christensen popularized hiring a product to do a job (2003); Ulwick's ODI is a related method; Intercom wrote the when/I want/so I can job story. Doran's 1981 SMART letters were specific, measurable, assignable, realistic, time-related. Ellis's North Star is one value metric, not a substitute for a target.
- Writing It CrisplyWrite brief content that leads with a checkable problem, separates know/believe/don't-know, and does not confuse a brief with a PRD.Solutioneering jumps to a feature and closes better answers. Cagan's empowered-team test is problems, not feature lists. Cut filler. Make claims a skeptic can break. Separate evidence, assumptions, and open questions. The brief asks whether the problem is worth solving; the PRD specifies the chosen solution later. Tie the page to vision, strategy, and 'why now.'
- Guided Project: Write a Product BriefDraft a short brief for an at-risk-projects scenario and leave with one sentence a skeptical VP could fund.Learners write a one-page brief for a project-management tool where managers miss slipping work until the date is gone. Problem and labeled evidence first; one user and an Intercom job story; an outcome metric with baseline, target, and date; explicit non-goals; the riskiest assumption first; a rough approach; honest open questions. The last move is not a recap. It is one sentence, tonight, and the VP question.
Questions this course answers
What is the primary purpose of a product brief?
A brief's job is upstream alignment and forcing clarity about the problem and the bet before building. Documenting every requirement is the later PRD or spec. It is a proposal, not a contract, and it does not replace later docs.
Why does writing a brief in prose tend to surface flawed thinking better than a slide deck?
Bezos's 2004 S-Team email argued that narrative structure forces you to say what is more important than what. Connected sentences reveal muddy reasoning that bullets can paper over. Prose is not always shorter or faster, and slides can hold data.
Why is a short brief treated as a feature rather than a limitation?
Length is a tax on the reader and a hiding place for the writer. Amazon's S-Team memos run to six pages; many briefs aim at one. The point is a document someone can finish and still see the bet — not a claim about build complexity, and not a ban on evidence or disagreement.
A brief states the target as 'all users who want a better experience.' What is the main problem with this?
An overly broad user makes every downstream choice mushy. A sharp user and a specific job sharpen scope and metrics. It is the opposite of too specific, it is not a job, and a target user is not a non-goal.
The sentence 'When I ___, I want to ___, so I can ___' is best credited to which source?
Intercom (Paul Adams; Alan Klement later named it) wrote the when / I want / so I can job story as a way to capture situation, motivation, and outcome. Christensen popularized 'hire a product to do a job' in 2003; Ulwick developed Outcome-Driven Innovation. Those are related ideas, not that sentence.
Which of these is a well-formed success metric for a brief?
A strong metric is specific and measurable, with a baseline, a target, and a timeframe, and it measures an outcome. 'Improve the experience' and 'make users happier' are wishes. 'Ship the dashboard' is an output.
Grounded in trusted sources
- 2017 Letter to Shareholders — Jeff Bezos, Amazon.com, Inc., Exhibit 99.1 to Form 8-K (18 April 2018) — six-page narrative memos; no PowerPoint; study-hall reading — https://www.sec.gov/Archives/edgar/data/1018724/000119312518121161/d456916dex991.htm
- A 2004 email from Jeff Bezos explains why PowerPoint presentations aren't allowed at Amazon — Madeline Stone, Business Insider, 28 July 2015 — S-Team email of 9 June 2004; 4-page narrative vs 20-page deck — https://www.businessinsider.com/jeff-bezos-email-against-powerpoint-presentations-2015-7
- Applying Amazon's Working Backwards Process — for Leaders — Ian McAllister — 2012 Quora post on PR/FAQ; review starts with the problem paragraph — https://www.linkedin.com/pulse/applying-amazons-working-backwards-process-leaders-ian-mcallister
- Assessing Product Opportunities — Marty Cagan, Silicon Valley Product Group, 13 December 2006 — ten questions; opportunity not solution; look before you leap — https://www.svpg.com/assessing-product-opportunities/
- Empowered Product Teams — Marty Cagan, SVPG, 31 October 2018 — assigned problems to solve, not lists of features; outcomes not output — https://www.svpg.com/empowered-product-teams/
- How we accidentally invented Job Stories — Paul Adams, Intercom, 28 June 2016 — When / I want to / So I can; named later by Alan Klement — https://www.intercom.com/blog/accidentally-invented-job-stories/
Every Wunder lesson is built from real, reputable sources — never invented.
Related courses
Wunder is a personalized learn-anything platform — tell it any topic and it builds a beautiful, fact-checked course in minutes, with narration, a knowledge check, and a college-style University track.
© 2026 Wunder Learning LLC · Terms & Privacy