Here's a brief I've received in various forms dozens of times: "We need a promotional video for the new product. Something modern and engaging, around two minutes, aimed at our target audience. Budget is flexible, ideally done by next month." It sounds like a brief. It has a deliverable, a length, a rough timeline. And it contains almost nothing you could actually make decisions from — because "modern," "engaging," and "our target audience" mean whatever the reader assumes they mean, which is never what the writer assumed.
What happens next is predictable. The work gets made based on a set of reasonable guesses, the client sees it and knows immediately that it isn't right, and nobody can explain why in terms that resolve anything — because the mismatch was baked in at the start, when four undefined words did the work that a real brief should have done. Then come the revision rounds, each one a further attempt to discover by trial and error what the brief could have stated in a paragraph.
The frustrating part is that this is one of the cheapest problems to fix in all of client work. An hour spent making a brief specific routinely saves days of rework, because every ambiguity resolved upfront is a wrong version that never gets built. Yet briefs stay vague, partly because writing a specific one requires making decisions that feel premature, and partly because vagueness feels generous — nobody wants to constrain the creative process, so they leave things open, not realizing that open means guessed.
That instinct is the main thing worth correcting. A specific brief isn't a straitjacket; it's what makes good work possible, because constraints give the work something to be right about. Vague briefs don't liberate anyone — they just move the decisions from the beginning of the project, where they're cheap, to the middle, where they're expensive. Here's how to write one that actually works.
Key Takeaways
- Vague briefs get guessed at. Words like "modern" and "engaging" mean different things to everyone, so the work gets built on assumptions nobody stated.
- Start with the goal, not the deliverable. What the work is meant to achieve matters more than what it is, and it's the thing most briefs never say.
- Name the audience specifically. "Our target audience" is not a description. Who they are and what they care about drives nearly every decision downstream.
- Constraints are helpful, not limiting. Budget, timeline, mandatory elements, and hard no's give the work something to be right about.
- Define what success looks like. If nobody has said how the work will be judged, it will be judged by an unstated standard — and probably fail it.
Lead With the Goal, Not the Deliverable
Most briefs begin and end with the thing being made: a video, a page, a campaign, with dimensions and dates attached. What they leave out is why it's being made — what it's supposed to achieve, what problem it solves, what would be different if it worked. That omission matters more than any other, because almost every decision in the work depends on the goal, and without it those decisions get made on instinct.
Consider how differently the same deliverable turns out depending on purpose. A product video meant to convert people who are already considering buying is a different piece from one meant to introduce the product to people who've never heard of it — different length, different structure, different emphasis, different opening. Both are "a two-minute product video." Only the goal tells you which one to make, and a brief without it is asking someone to choose blindly and then judging them for choosing wrong.
Stating the goal also improves the brief itself, because it exposes assumptions. Quite often, writing down what the work is meant to achieve reveals that the requested deliverable isn't the best way to achieve it — which is a valuable thing to discover before the money is spent rather than after. This is the same reason understanding the real objective is what separates a recommendation from order-taking: the goal is where expertise gets applied. [BACKLINK PLACEHOLDER → suggestion: internal link to article #84, what to ask a new client before you start / clients describe solutions, so find the goal behind the request]
Be Specific About the Audience
The second near-universal gap is the audience, usually gestured at rather than described. "Our target audience," "small business owners," "young professionals" — these are categories, not descriptions, and they don't tell you what you need to know: what these people already understand, what they care about, what they're skeptical of, what would make them act, and where they'll encounter this.
The difference is decisive in practice. Content for someone who already knows your category and is comparing options looks nothing like content for someone encountering the problem for the first time — the first can skip explanation and go straight to differentiation, the second needs the context established before anything else makes sense. Get that wrong and the work fails regardless of how well it's executed, which is why an unspecific audience is one of the most expensive gaps a brief can have.
A useful level of detail is enough for someone unfamiliar with your business to picture a specific person and predict how they'd react. What's their situation, what do they already know, what are they worried about, what's the moment they'd see this? Even a few sentences of that is dramatically more useful than a demographic label, and it settles a large number of downstream decisions before anyone has to guess at them.
Give the Constraints Honestly
People withhold constraints from briefs out of a well-meaning instinct — they don't want to limit the thinking, so they leave budget vague and requirements unstated. In practice this produces work that has to be redone once the real constraints surface, which is worse for everyone. Constraints aren't the enemy of good work; they're the frame that makes it possible to aim.
Include the practical ones plainly: the actual budget or a real range, the actual deadline and what's driving it, where and how the work will be used, and any technical requirements it has to meet. Budget in particular is worth stating honestly, because it determines what's realistically possible and a proposal built for the wrong scale wastes everyone's time. And a stated deadline should distinguish a real fixed date from a preference, since those lead to very different decisions about what to prioritize. [BACKLINK PLACEHOLDER → suggestion: internal link to article #53, most of your urgent deadlines aren't real / distinguishing real deadlines from stated ones]
Then include the constraints people forget: mandatory elements that must appear, brand or legal requirements, things that have been tried and rejected before, and — most usefully — clear no's. Knowing what's off the table is often more valuable than knowing what's wanted, because it eliminates whole directions before anyone invests in them. If there's an approach the client will definitely reject, saying so in the brief saves the round of work that would have discovered it.
🎬 Embed a short before-and-after of a vague brief rewritten with goal, specific audience, honest constraints, and success criteria.
Say What Success Looks Like
Almost no brief states how the work will be judged, and almost every project is judged anyway — usually against a standard that existed only in someone's head. Making that standard explicit is one of the highest-value things a brief can do, because it converts an unstated expectation into a shared target that the work can actually be aimed at.
This means writing down what a good outcome looks like in concrete terms: what the work should accomplish, how you'll know whether it worked, and what would make you consider it a success or a disappointment. Where measurable outcomes exist, name them. Where the judgment is more subjective, describe the impression the work should leave and how it should make someone feel or act — which is harder to write but far better than leaving it unsaid.
The exercise is also diagnostic. If nobody involved can articulate what success looks like, that's important information about the project: it usually means the goal isn't settled, and building something before that's resolved is how you get feedback that keeps changing direction. Better to discover the uncertainty while writing the brief than three weeks into production, since unclear success criteria are one of the main sources of the feedback loops that never converge. [BACKLINK PLACEHOLDER → suggestion: internal link to article #94, how to handle client revisions / undefined expectations are what make revisions spiral]
Writing the Brief When the Client Hasn't
Often no proper brief exists, because the client isn't experienced at writing them and doesn't know what to include. The productive response is to write it yourself and have them confirm it, rather than proceeding on an incomplete one and hoping — and this is genuinely part of a good provider's job rather than an imposition on the client.
The method is straightforward: ask the questions that fill the gaps, then write up what you heard as a brief and send it back for approval. That document becomes the shared reference for the project, and getting explicit confirmation on it is one of the most protective things you can do, because it converts your interpretation into an agreed definition. If your understanding is wrong, this is where it surfaces — cheaply, before anything is built.
Doing this also demonstrates competence in a way that's immediately visible. A provider who returns a clear, well-structured brief after a conversation has shown they listened, understood, and thought about the problem, which is more persuasive than most things you could say about your expertise. And it establishes a working pattern of clarity from the start, which tends to characterize the rest of the engagement. [BACKLINK PLACEHOLDER → suggestion: internal link to article #74, how to onboard a new client well / establishing clarity early sets the tone for everything after]
