Briefs

Neither of you is lying. A conversation leaves two versions of itself, and only the written one survives. The brief is that written version, and skipping it is what turns a fixed price into an argument.

The cost lands late and lands on you. Work gets approved by nobody, because the approver was never named. A deadline appears that was always there, attached to a trade show nobody mentioned. A second language arrives in week three and nothing moves to make room for it.

What a Brief Is

A client sends three paragraphs about a new website. A product manager shares a one-page document called a product one-pager. An agency account manager hands you something labeled a creative brief. All three are the same object, and only one of them is called a brief.

A brief is a short written statement of what needs to happen and why, agreed before the work starts.It exists to hold two people to the same idea after the conversation is over, which is why the useful part is always the agreement rather than the document.

Where the Format Came From

The creative brief comes out of advertising. In 1968, Stephen King at J. Walter Thompson in London and Stanley Pollitt at Boase Massimi Pollitt separately built what became account planning. The role put research between the client and the creative team.

That role needed an artifact, and the brief was it. One page that turned a client's request into a problem a creative team could work on. One page meant one page, roughly 250 to 400 words, which is still the right length. The shape it settled into, audience, problem, message, constraint, is still the shape a good design brief has.

The Four You Will Meet

The client brief is what a client sends you, unprompted. It describes a deliverable and rarely names an outcome, which is what makes the first conversation necessary.

The creative or design brief is what you write back. It restates the problem, the audience, the scope and the measure of success in one page, and it is the version both sides approve.

The project brief covers the commercial frame: deliverables, dates, dependencies, who approves, and what the work costs.

The product one-pager or PRD is the in-house version of the same thing. Nobody calls it a brief, and it does the same job: one document that says what problem this solves, for whom, and how anybody will know it worked.

Who Writes It, and Who Signs It

A brief only works when two people agree to the same page.The client or the product manager supplies the problem and the constraints. You supply the version that can be worked from, which is why the write-back exists as its own step.

That agreement is also what makes the document worth keeping. A brief nobody approved is a set of notes, and notes lose every argument they are brought to.

Pro tip: If a brief has no date and no approver, it is not a brief. It is a wish, and it will collect changes until somebody stops it.

Where a Brief Stops

A brief covers a project; it does not cover a change.It says the checkout should lose fewer people and names the target, and it never says which control to use on the shipping step. That level goes in a ticket, which is a different object with a different job.

That boundary matters most in-house, where teams often skip the brief and go straight to tickets. The result is twenty small decisions with nothing to check them against, and no way to tell whether the release worked.