How to write a design brief that gets you what you meant

Why most design goes wrong

People think a design fails because the designer wasn't good enough. Usually that's not it.

Most design problems aren't about design. They're about expectation gaps.

I learned this the embarrassing way — from both sides of the table.

Once I ordered a design for myself. We even started with a moodboard. The designer was genuinely good, did real work, took it seriously. And the result went in a completely different direction than what I had in my head.

Everything was done well. It just wasn't what I meant.

I didn't feel heard. But here's the uncomfortable part: I hadn't actually said the thing clearly enough to be heard.

Then I sat in the other chair. I presented a first concept to my own client and watched their face. It wasn't it. Not even close to what they'd been imagining.

And the strange thing? Both of us were right. We were just designing from two different pictures in our heads.

A brief isn't paperwork. It's the moment two people agree on the same picture before money and hours get spent.

That's what learning how to write a design brief is really about. Not formatting. Alignment.

What a good design brief actually contains

A brief isn't a spec sheet. It's not a list of pixels.

It's context. It's intent. It's enough for a smart designer to make good decisions when you're not in the room.

So when people ask what to include in a design brief, I keep it to the parts that actually change the output:

• The goal. What is this design supposed to do? Sell, explain, reassure, impress?
• The audience. Who looks at this, and what do they already feel?
• The win condition. What would make this a success in your eyes?
• Constraints. Deadline, budget, brand rules, tech limits. The real ones.
• References. Things you love. Things you hate. Both matter.
• The boundary. What's off the table or already decided.

Notice what's missing. There's no "make the logo bigger." That's not your job in the brief. Your job is the why and the what. The how belongs to the designer.

The kickoff questions that close the gap

Here's the move that's saved me the most pain. I don't open a project asking for requirements. I ask one question:

"What would make this project a win in your eyes?"

That single question pulls the picture out of someone's head before they've found the words for it. It surfaces the unspoken thing — the feeling, the fear, the comparison they didn't think to mention.

A few others I lean on:

• What's the one thing this absolutely cannot look like?
• Who do you wish this looked as good as?
• If a stranger saw this for three seconds, what should they think?
• What went wrong last time you ordered design?

If you're the one writing the brief, answer these for yourself first. If you're hiring, a designer who never asks them is a designer guessing.

And translation is the job. Vague words like "clean" or "premium" mean different things to everyone. Someone has to turn them into visuals — that's why questions, options, and check-ins exist.

References and moodboards, used right

Words lie. Images don't.

I can write "modern and trustworthy" and you'll picture something. The designer will picture something else. We'll both be confident. We'll both be wrong about each other.

Three screenshots fix that faster than three paragraphs.

So gather references. Not just ones you love — ones you hate too. "I don't want this" is some of the clearest signal you can give. The contrast tells a designer where your taste actually lives.

One warning, because I've watched this go sideways. References show direction, not a copy order. Don't hand over five sites and expect a Frankenstein of all five. Say what you like about each one. "I want their calm" is useful. "Make it like this" is a trap.

What to leave out of a brief

The instinct, when you've been burned, is to over-specify. Write everything down. Control every detail.

Resist it.

Leave out the how. Don't dictate fonts, layouts, and exact colors unless they're true brand constraints. The moment your brief reads like a build spec, you've hired a pair of hands instead of a designer.

Leave out fake certainty too. If you don't know something yet, say so. "Still deciding on tone" is more honest — and more useful — than pretending you have an answer you'll reverse next week.

A brief that's all instructions and no intent gets you exactly what you asked for. Which, as I learned, is rarely what you meant.

A simple brief template you can copy

You don't need a tool for this. You need a paragraph and a few honest answers. Here's a design brief template I'd happily receive:

1. Project, in one line. What it is and what it's for.
2. The goal. What success does for your business or your day.
3. The audience. Who sees it and what they should feel.
4. What a win looks like. Your answer to the kickoff question.
5. Constraints. Deadline, budget, brand, tech. The non-negotiables.
6. References. Three you love, two you hate, a line on why.
7. Off-limits. What's already decided or out of scope.
8. What's still open. The parts you genuinely haven't figured out.

That's it. Fits on a page. And then — this is the part people skip — write decisions down as you go, and do small check-ins before the big reveal. Frequent five-minute "is this the right direction?" beats one giant presentation where everyone holds their breath.