Product Thinking — Part 3: The One-Page Product Brief

maang.io AI-Native Builder Series

📦 Artifacts for this topic — build against these, and check your own with them:
prompt → artifacts/prompts/01-draft-my-brief.prompt.md (copy it) ·
reference → artifacts/reference/streakup-product-brief.md (the worked brief + persona + jobs) ·
check your work → artifacts/verify.md.
Build yours first, then compare — the reference is a mentor's version to verify
against, not an answer key to paste.

What is this?

Before a film crew shoots a single frame, there's a one-page document everyone reads first. It says, in plain language: what this movie is about, who it's for, and why anyone should care. It's short on purpose — if you can't say it on one page, you don't actually know what you're making yet. Every later decision (the casting, the budget, the lighting) gets checked against that page. When someone wants to add a giant explosion, the question is simple: does it serve what's on the page?

A product brief is that one page for your app. It is the single document that captures everything you've figured out in this topic — the problem, the user, the value, the jobs — in a form so tight that anyone (a teammate, a teacher, your AI partner) can read it in two minutes and understand exactly what you're building and why. It's the first official piece of your Spec Package, and it's the page that every requirement, story, and line of code for the rest of the course will trace back to.

The one-line idea: the product brief is the one page that says who your app is for, what problem it solves, and why it matters — short enough to read in two minutes, sharp enough that every later decision traces back to it.

You've done the thinking across Parts 1 and 2. This chapter is where you write it down — and where you produce a complete StreakUp brief you can copy the shape of.