A good brief states the business goal, the audience, the scope, the constraints and what success looks like. And leaves the how to the designer. Context beats mood boards.
Every studio has stories of briefs that went wrong. Some arrive as a single sentence. Others arrive as a forty-page document that reads like a corporate annual report. The worst are the ones that describe a colour - "we like blue" - and call it a day.
A good brief is not a wish list. It's a compass. It tells a designer where you're trying to go without dictating every step of the route. When it's done well, it makes the work faster, the output sharper, and the whole relationship more enjoyable for both sides.
Why the brief matters more than you think
Designers are problem-solvers, not mind-readers. Every assumption they have to guess at becomes a revision later. A vague brief doesn't save you time at the start - it spends it threefold at the end, in feedback loops, reworked concepts, and that sinking feeling that you're not quite getting what you pictured.
The brief is where clarity gets built. It's the difference between a designer working from a defined problem and a designer working blind. Give them a defined problem and you'll be surprised what they return with.
A good brief is not a wish list. It's a compass - it shows the direction without dictating every step of the route.
What a great brief contains
You don't need forty pages. You need the following, in plain language. Most strong briefs fit on two pages.
1. Who you are
Start with the business, not the design. What do you do, who do you serve, and how do you make money? A designer who understands your business model makes different choices than one who only understands your logo. If you run a subscription service, say so. If your customers find you through referrals, say that too. Context changes everything.
2. What you're actually asking for
Be concrete about the deliverable. "A new logo" is not a deliverable - it's a category. Do you need a full identity system, or just a wordmark? A website, or a landing page? Naming the actual outputs prevents the painful moment when the work is done and you realise you expected more than you asked for.
3. The problem, not the solution
This is the most important part and the most frequently skipped. Describe the problem you're solving, not the design you imagine. "We lose deals to competitors who look more credible" is a problem. "I want a red logo with a swoosh" is a solution you've already half-decided. When you hand a designer the problem, you let them bring their craft. When you hand them the solution, you've demoted them to a pair of hands.
4. Who it's for
Name the audience with as much precision as you can. Age, industry, buying behaviour, what keeps them up at night. "Everyone" is not an audience - it's an abdication. The tighter the audience, the sharper the design, because the designer now has someone specific to persuade.
5. What success looks like
How will you know this project worked? More enquiries? A stronger impression with investors? A brand your team is proud to put on the wall? Stating the outcome you want gives the designer something to aim for beyond "make it look nice."
What to leave out
Just as important as what you include is what you resist including. Skip the essay on your company's founding values unless they genuinely shape the design. Skip the folder of twenty "inspiration" logos from competitors - they'll only nudge the work toward sameness. And resist the urge to design by committee in the brief itself; a brief with five conflicting opinions already embedded will produce five-way compromise, not good work.
One reference you like is useful. Twenty references is a mood board you should have hired someone to make. Show the designer the thing you love about the reference - the confidence, the warmth, the simplicity - not just the reference itself.
What to tell them about process
Every project needs three answers about how you'll work together, and the brief is the right place to set them. First, who makes the final call - one decision-maker, not a committee. Second, how fast you can turn around feedback; a designer stalled for three weeks waiting on sign-off is a designer whose momentum is gone. Third, what the budget is. A number, not "competitive." Designers can do remarkable things at almost any budget, but only when they know what it is from the start.
The one sentence that matters
If you're stuck, force yourself to write a single sentence that captures the whole project: "We want [audience] to feel [emotion] about [thing] because [reason]." Try it. Most people can't finish it on the first attempt - and the blank space it exposes is exactly where the real work lives. When you can complete that sentence honestly, you have a brief.
How to give good feedback
The brief starts the project, but the feedback keeps it on the rails. Most client feedback falls into one of two traps: it's either so vague the designer has to guess ("it doesn't feel right"), or so prescriptive the designer has no room to solve ("make the logo bigger and change the blue to navy"). Neither helps.
Good feedback names the problem and lets the designer own the solution. "The typography feels too cold for the warmth of our service" is a problem. "Use a serif" is a solution you're paying them to arrive at. The more you can articulate what isn't working and why, the faster a good designer can fix it. The more you micromanage the fix, the less you're getting from the relationship you're paying for.
There's also a rhythm to good feedback. Gather it from the right people, consolidate it into a single voice, and deliver it in one batch. Drip-feeding individual thoughts across a week forces a designer to chase moving targets - and nobody does their best work that way.
What a bad brief looks like
For the avoidance of doubt - a bad brief is one of these: a sentence ("make it modern"), a colour request ("blue, but not too blue"), an ask to copy someone else ("like Nike but cheaper"), a brief written by five people who never aligned ("we combined all our notes into one document"), or no brief at all. If your brief resembles any of these, the single most productive thing you can do is write a better one before you hire anyone.
What to expect back from a good designer
When you've handed over a genuinely strong brief, the designer's response tells you a lot. A good designer asks clarifying questions - not because the brief was unclear, but because they're testing whether you've thought it through. They push back on assumptions. They point out contradictions you hadn't noticed. None of this is friction. It's the sound of someone actually engaging with the problem rather than racing to open a template.
If a designer takes your brief, thanks you, and quotes a price without a single question, be careful. That's often the sign of someone who plans to reuse a template and paste your name on it. The questions are the value. Demand them.
How to Brief a Designer and Get Work You Love: key questions
What makes a good design brief?
Context, goal, and constraints: what the business does and who it serves, what success looks like in one sentence, and the honest boundaries of budget, deadline, and must-haves. Add two or three examples of work you admire and one you reject. The most useful briefs are honest about what the designer knows better than you.
How long should a design brief be?
One to two pages. Length is not rigour; the essentials are who it is for, why now, what great looks like, and what is being delivered. A ten-page brief usually buries the three sentences that matter.
What are the most common brief mistakes?
Prescribing solutions instead of stating the problem, vague objectives like modern or clean, no ranking of what matters most, contradictory input from stakeholders who each wanted their line included, and an undefined budget that forces the designer to guess at scope.
How should I give feedback in design rounds?
Frame every comment against the goal, not the artifact: this reads more corporate than we wanted lands usefully, I do not like orange does not. Consolidate all stakeholder feedback into one voice per round, deliver it in one batch, and include the reasoning so the designer can solve the cause rather than the symptom.
What should I expect to receive from a good designer?
More than files: a rationale connecting the work back to your brief, an organised handover with source files, exports, and usage guidance, and questions during the process. Great designers interview you harder than you brief them, and that is a good sign.
A brief is an act of respect. It says: here's the problem, here's the context, now show me what you can do. Designers who receive that brief will run further with it than you expected - and you'll get work you actually love.