Writing a one-page project brief that holds
Updated

The brief is the contract before the contract: scope, success metric, and what is explicitly out, on a single page.
Every failed engagement I have seen had either no brief or a ten-page brief nobody read. One page, signed, is the whole trick.
The short answer
State the problem with a number, list what is in and what is out, name the success metric with a date, and get a signature. Everything else is appendix.
The anatomy
Problem (3 lines). Who feels what pain, how often, at what cost. One number minimum.
In scope (5 bullets max). Concrete deliverables, each verifiable by looking.
Out of scope (3 bullets min). The three things you will be asked for and will decline. Writing them now saves the fight later.
Success metric. "Lookup under 3 minutes for 9 of 10 cases by 15 March, measured on live labels." Metric, threshold, date, measurement method.
Owners and first step. One name per side, and the smallest shippable slice with its own date.
Worked example: before and after
Weak: "Improve the returns process with modern tooling." Strong: "Cut disputed-return lookup from 35 minutes to under 3 minutes for 9 of 10 cases by 15 March. In: lookup page over the order store, rule table, runbook. Out: warehouse hardware, refund policy changes, mobile app. Owner: ops lead Ayşe plus FDE. First slice: read-only lookup on live labels by 20 January." One of these survives contact with reality.
Checklist: does your brief hold?
- A stranger can state the success metric back to you.
- The out-of-scope list names real temptations.
- The first step ships within two weeks.
- Both owners signed with a date.
Related reading
Straight answers
Frequently asked questions
What goes on the one page?
Problem with a number, in-scope list, out-of-scope list, success metric with a date, owners, and the smallest first step.
Who signs the brief?
The customer owner and you. Unsigned briefs drift; signed briefs protect both sides when scope pressure arrives.
How often does it change?
Expect two or three revisions in week one, then stability. A brief that never changes was written too late.