The brief is the deliverable

When a project goes badly, the post-mortem tends to focus on the middle — the round that went sideways, the feedback that arrived late, the scope that grew by degrees. The cause is almost always earlier than that, in a brief everyone agreed to quickly because they were keen to start.

What a brief is for

A brief is not a summary of what the client said. It is the document that makes disagreement happen early, while disagreement is still cheap. Its job is to state what the project is trying to change, what success would look like in numbers, what is deliberately out of scope, and who decides.

That last one causes more damage than the rest combined. A project with three people who can each reopen a decision does not have a process. It has a queue.

The sentences that cost money

Watch for the phrases that sound like agreement and are not. Make it feel premium. Something modern. We will know it when we see it. Each one defers a decision into the design phase, where it will be resolved through revision rather than conversation, at roughly ten times the cost.

The fix is unglamorous: write the ambiguity down and ask what would have to be true for it to be settled. Half the time the client already knows and has simply never been asked directly.

Slow at the start

A brief that takes a week feels like a week of not designing. It is the cheapest week in the project. Every hour spent making the goal specific removes several hours of work that would otherwise have been produced, reviewed and thrown away.