Almost every troubled project I have ever seen was in trouble before it started. The cause was not the team, the timeline, or the client. It was the brief. Or rather, the thing everyone called a brief that was actually just a conversation with a deadline attached.
A real brief answers five questions: what are we making, who is it for, what does success look like, what are the constraints, and who decides. If any of those answers is vague or missing, you do not have a brief. You have a hope.
How do you know your brief is not a brief?
Read it and try to disagree with it. A real brief is specific enough to argue with. It says the audience is marketing directors at B2B software firms, not people. It says success means 30 qualified calls, not awareness. If you read your brief and find yourself nodding along because it could mean anything, it means nothing. Vague briefs feel agreeable. That is what makes them dangerous.
The test I use: could two good teams read this brief and produce completely different work? If yes, the brief has not done its job. All the important decisions are still hiding inside it, waiting to ambush the project later.
This is where budgets quietly die. Every ambiguity in the brief becomes an assumption, every assumption becomes rework, and rework is the most expensive work there is. I wrote about the money side in why creative projects go over budget.
What goes into a brief that works?
Five things, in this order. The job: what exactly are we making, in one paragraph. The audience: who is it for, described like a real person. The outcome: what changes if this works, stated as a number where possible. The constraints: budget, timeline, and anything that is fixed. The decider: one named person whose yes means yes.
Notice what is not on the list: the solution. A brief that prescribes the answer is not a brief, it is a shopping list. Your job is to describe the problem so well that the right solution becomes obvious. If you are briefing a contractor, there is a longer version of this in how to brief a contractor for a brand project.
Write it down. Briefs given verbally evaporate. The meeting felt clear. The notes say something else. Two weeks later everyone remembers a different conversation. If it is not written, it was not briefed.
Who writes the brief?
Whoever wants the project to succeed. Sometimes that is the client. Often, honestly, it is the delivery person, because they are the one who will pay for its gaps. I regularly rewrite client briefs in the first week of an engagement. Not because clients are bad at writing, but because they are too close to see what is missing.
A good delivery lead treats the brief as the first deliverable, not as paperwork. Getting it sharp is the highest leverage week of any project.
What if the brief keeps changing?
Then you do not have a scope problem, you have a decision problem. Changing briefs usually mean the decider was never named, or the outcome was never agreed. Go back to the five questions. The one you cannot answer is the one that keeps moving.
And when the brief genuinely needs to change, because the world changed, that is fine. Change it in writing, note what moves, agree it with the decider. A brief is a living document. It is not a rumor.
Working with Avy
The first thing I do on any engagement is stress test the brief. Most of the time we rewrite it together in week one, and the project gets easier from there. If your projects keep wobbling at the start, book a call and bring your brief. We will read it like it is guilty until proven innocent.
Or start with the words themselves. The brand glossary defines the terms that cause most briefing confusion, in plain English.
Need someone to get your project over the line?
Project delivery support for brand, digital, and creative teams that need clearer direction and smoother progress.