Skip to content
POW XD
Journal
Practice

How to brief a design studio

1 July 20265 min read

How to brief a design studio · Article banner

The quality of the work you get back usually reflects the quality of the brief you send. Here is how to write one that helps.

The quality of the work a studio sends back is set, more than anyone likes to admit, before the studio has done anything at all. It is set by the brief. Most briefs describe what the client wants made: a website, a rebrand, an app with these features. The better ones describe what the client is trying to achieve, and the difference is not pedantry. A studio can only solve a problem it has been allowed to understand.

So begin with the business, not the design. What are you actually trying to change. More enquiries of a better quality. A higher average order value. A stronger position against a competitor who is beating you on presence rather than substance. Say it plainly, in the language you use internally when the agency is not in the room. A studio worth hiring will work backwards from that outcome to the design, which is the right direction of travel. A brief that opens with the artwork has already given away the most useful thing it knew.

Be honest about constraints, all of them, including the awkward ones. The real budget, not a coy version of it. The timing, and what is driving it. The people who will need to approve the work, and what they tend to react to. The things that genuinely cannot change, whether a brand mark, a platform, or a promise already made to customers. Constraints are not the enemy of good design. They are the frame that makes it possible, and a studio told the truth early will spend its energy on the problem rather than discovering the walls by walking into them.

Share what you already know, and share the unflattering parts. The customer research gathering dust. The feedback the sales team repeats until they are tired of it. The pages where people leave, the questions they keep asking, the objections that come up on every call. This kind of evidence is worth more than any opinion about colour or layout, because it is the ground truth a good studio will design towards. Withholding it to see whether the agency can guess is a way of paying for work and then hiding the answer.

Say what good looks like to you, and what you want to avoid, with examples. Three or four references, each with a sentence on what specifically you admire or dislike, will teach a studio more about your taste in an afternoon than a page of adjectives ever could. Adjectives are treacherous. Everyone means something different by clean, premium, or bold. A concrete example pinned to a reason removes the guesswork and saves a round of work that would otherwise be spent triangulating your vocabulary.

Constraints are not the enemy of good design. They are the frame it needs.

This matters more now that so much can be generated in seconds. It is easy to produce a plausible logo, a passable page, a dozen directions at the push of a button, and that ease has quietly raised the value of knowing what you are trying to do. When making something is cheap, the scarce and decisive skill is judgement: choosing the right problem, recognising the right answer, saying no to the merely competent. A sharp brief is where that judgement starts, and no tool will supply it for you.

The best clients have understood the shift. They no longer treat a brief as a specification to be executed, but as the clearest possible statement of the problem to be solved, and then leave room for the studio to solve it. That is the relationship that gets the most from senior people, and increasingly from the tools those people use. Direction is the thing in short supply. Production is not.

It is worth saying what a good studio does with a brief like this, because it is not simply obedience. A strong partner reads the brief for the problem beneath the request, and will sometimes tell you that the thing you asked for is not the thing you need. That conversation is uncomfortable and enormously valuable, and it can only happen if the brief gave them the real objective to push against. A specification invites execution. A problem invites thought, and thought is the expensive part you are actually paying for.

In practice a page or two is plenty. A clear problem, a real outcome, honest constraints, the evidence you already hold, and a concrete sense of your standard. Give a studio that, and you have done half the work before the first conversation, and made the other half far more likely to be good. A vague brief buys vague work at full price. A sharp one is the cheapest quality you will ever purchase.

The best working relationships in this field feel less like a client issuing instructions and more like two people solving the same problem from different sides. That is what a considered practice is set up to offer, and what a sharp brief unlocks. Give experienced people a clear problem and the room to solve it, and you tend to get back something better than you knew how to ask for, which is the whole reason to hire them rather than dictate to them.

UX Companion

The UX dictionary in your pocket.

UX Companion is our UX-dedicated app. A carefully written glossary of the tools, terms and theories every UX professional should know. Each entry pairs a plain-language definition with practical implications you can apply in your work.