How to Brief a Designer Without 5 Rounds of Revisions

Every designer has lived this story. A founder describes a project in two sentences: “We need a landing page. It should look modern.” A week later the first comp lands. The founder responds with a paragraph that starts with “I like it, but…” — and the project enters a months-long loop of revisions, hedged opinions, and quiet resentment on both sides.

The fix is almost never more revisions. It’s a sharper brief at the start.

A great design brief is not a long document. It’s a small set of decisions made before any pixels move — decisions about who you’re designing for, what you want them to do, and what would make the work a failure. When those decisions are clear, the design tends to come out right the first time. When they’re missing, no number of revisions will save the project.

This is the framework we use with every client. It’s borrowed from advertising legend David Ogilvy, refined through a decade of building digital products, and short enough to fit on one page.

Why most briefs fail

Most briefs read like wish lists. They describe what the founder wants the design to be — modern, clean, premium, bold — but say almost nothing about who it’s for or what it has to do. The result is a designer guessing at intent, and a founder reacting to those guesses without a shared standard for “right.”

A useful brief reverses the order. It locks in the audience and the goal first, then describes the brand voice, and only at the end touches on visual preferences. By the time you’re talking about color and typography, the designer already understands the problem well enough to argue with you — which is exactly what you want.

A brief is a contract about what success means. If you can’t tell the designer how you’ll know the work is good, neither of you should be working on it yet.

The five questions a brief must answer

Skip the templates. Most design briefs you find online ask for fifteen things you don’t have answers to. These five are the ones that matter — and you can usually fill them in during a single coffee.

1. Who is this for?

Be specific. Not “small business owners” — a thirty-eight-year-old marketing director at a B2B SaaS company who has fifteen minutes between meetings to evaluate vendors. The narrower the audience, the easier every design decision gets.

A common failure mode: trying to design for two audiences at once. If you serve both consumers and enterprise buyers, you need two briefs. Trying to merge them produces work that pleases neither.

2. What do you want them to do?

Every page has exactly one job. A pricing page wants you to start a trial. A blog post wants you to subscribe. A case study wants you to book a call. If you’re not sure what the one job is, the design will end up with three CTAs of equal weight and convert none of them.

Write the action as a complete sentence: “After reading this page, I want a qualified buyer to book a thirty-minute intro call.” That sentence is now the rubric for every design decision.

3. What does the audience need to believe?

This is the most overlooked question on a brief. The reader has objections before they arrive — will this work for a team my size? is it really faster than what I use today? can I trust these people? — and the design has to surface answers to those objections in the order they come up.

List the top three objections in order of severity. The hierarchy of your design — what’s above the fold, what’s pulled into a callout, what gets skipped to a footer — should mirror that list.

4. What’s the brand voice?

Three adjectives, not fifteen. Confident but not arrogant. Practical, not preachy. Warm enough to want to meet in person. The point isn’t to write poetry — it’s to give the designer enough character to make consistent micro-decisions about button copy, headline tone, and how friendly the empty states should be.

If you can name three brands whose voice you admire (and one you don’t), you’ve given the designer everything they need.

5. What would make this a failure?

This is the secret weapon. Most briefs describe success in vague terms (“we want it to feel premium”). Inverting the question forces specificity: the design fails if a CTO scrolls past the security section, or if it looks like a fintech startup from 2018, or if a screenshot of it can’t be sent to a board member without context.

If you can name three failure modes, the designer can pre-empt them. If you can’t name any, you’re not ready to write a brief.

What to leave out

A brief is not a design. The most common mistake founders make is to include reference images, font preferences, and color palettes — sometimes even rough mockups — in the brief itself.

Don’t.

References are useful in the kickoff conversation, not in the brief document. Including them in writing locks the designer into your existing taste, when half the value they bring is their ability to see the problem fresh. Save the moodboards for week two, after you’ve agreed on the strategy.

There’s also no need to specify deliverable formats, font files, or stock photo libraries in the brief. Those are project logistics — they belong in a statement of work, not in a strategy document.

How to give feedback that doesn’t waste a week

Once the design lands, the next failure mode is feedback. Most feedback is a list of taste-driven opinions (“can the headline be bigger?”) that ignores the brief entirely. The designer ends up making changes to please you, the design drifts from its strategic intent, and three rounds later nobody remembers why a decision was made.

The fix is to anchor every piece of feedback to the brief.

• “The headline doesn’t answer the first objection from the brief” — that’s actionable feedback.
• “I don’t love the headline” — that’s an opinion, and the designer can’t act on it without making a new guess.

Two rules that keep feedback honest:

1. One person owns approvals. Not a committee. A single decision-maker who can say yes or no without checking with three other people. Committee feedback is where good designs go to die.

2. Group all feedback into one round. Drip-feeding comments across three days produces a Frankenstein design. Sit with the work for twenty-four hours, write your feedback in one document, send it once.

If you can’t do those two things, you don’t have a process problem. You have an organizational problem — and no design brief in the world will fix it.

The brief as a forcing function

The real reason briefs matter is that they force the founder to make decisions they’ve been avoiding. Most projects that go off the rails don’t go off the rails because of the design. They go off the rails because the founder hadn’t actually decided who the product was for, what action they wanted, or what success looked like — and they were hoping the designer would figure it out for them.

A good brief makes the avoidance impossible. Sitting down with the five questions above for forty-five minutes will save you weeks of revision cycles, two designer relationships, and a stack of mockups that almost worked.

That’s a good trade.

Where to go next

If you’re at the stage of writing your first brief — or rewriting one that didn’t work — three things are worth doing now. Pick a single audience and write a one-sentence description of them. Pick the one action the page should produce. List the three objections that audience arrives with. With those three artifacts in hand, you have more than most agencies receive before kickoff.

For a deeper take on what comes after the brief — turning that strategy into a shipped product in four weeks — read From Idea to MVP in 4 Weeks: A Founder’s Playbook.