The Brief Is the Product.

Why the Quality of a Brief Determines the Quality of Everything That Follows

There is a belief, common across many creative engagements, that the brief is the starting pistol. The thing you fire before the real work begins. Something to get through so the interesting part; the designing, the writing, the building; can start.

This belief produces consistently mediocre work. Not bad work. Mediocre work. Finished on time, delivered as agreed, roughly in the right direction, but without the specificity that makes it genuinely useful to anyone.

What a Brief Actually Is

A brief is a set of decisions. Not instructions. Not a wish list. Decisions: about what you are trying to achieve, for whom, in what context, and by what measure.

The difference matters. Instructions describe what you want. Decisions describe why you want it and what success looks like. One gives a designer a task. The other gives them a problem to solve.

The best creative work almost always emerges from the second type of brief. Not because talented people need freedom, they do, but that is a separate point, but because a brief that contains real decisions also contains real constraints. And constraints, counter-intuitively, are where creative work gets interesting.

Tell someone to make a presentation that feels confident and clear. They will do their best. Tell them the audience has ten minutes, three competing priorities, and a tendency to skim rather than read — and now the problem has edges. The work can push against something. The designer can make a choice and justify it. The outcome has a better chance of being right.

Where Briefs Go Wrong

Most poor briefs share a few characteristics worth naming.

They describe the output rather than the outcome. 'We need a brand refresh' is not a brief. 'We need our materials to land credibly with institutional investors who currently perceive us as a smaller operation than we are' is considerably closer. The first tells someone what to make. The second tells them what problem to solve. These lead to entirely different work.

They contain contradictions that nobody has resolved. 'Premium but approachable. Authoritative but not corporate. Traditional but forward-looking.' Each of these is a real tension with a real answer. Leaving them in the brief does not make them go away, it passes the responsibility for resolving them to the people doing the work, who will resolve them differently every time, producing inconsistent output that nobody is quite satisfied with.

They treat the audience as an afterthought. The audience is not context for the brief. The audience is the brief. Everything else: the tone, the hierarchy, the level of complexity, the choice of what to include and what to leave out; flows from a specific, honest understanding of who you are communicating with and what they need to do or believe as a result.

They are written by the wrong person at the wrong time. The brief should be written by the person who owns the outcome; not delegated to whoever has capacity, and not assembled from a series of disconnected contributions from different stakeholders who have not been asked to agree with each other first.

How To Write One That Works

Start with the decision you are trying to influence. Not the document you are commissioning. The decision.

What do you need someone to believe, feel, or do as a result of encountering this work? Write that down in one sentence. If you cannot write it in one sentence, you do not yet know what the work is for.

Then describe the audience in enough detail that someone who has never met them could make reasonable creative choices on their behalf. Not 'senior decision makers', that describes half the working population. What do they already know? What do they already believe? What are their objections likely to be? What does scepticism look like for this particular group, and what would move them?

Then describe the context. Where will this work appear? On a screen, on a page, in a meeting room, shared by email to someone who was not in the original conversation? How much time will the reader give it? These are not production questions. They are design questions. The answer changes everything.

Then define what good looks like. Not aesthetically. Functionally. If this works, what happens next? If it fails, what went wrong?

That is the brief. Everything else: timelines, file formats, revision rounds, delivery specifications; is project management. Important, but downstream.

The brief is the product. The rest is how you make it. Organisations that understand this tend to produce better work, spend less on revisions, and get to the right answer faster. Those that do not tend to spend more on everything and arrive somewhere approximately right after a lot of unnecessary pain.