How to write a design brief: A 2026 step-by-step guide

An estimated 33% of marketing budgets is wasted on work that has to be redone, largely because the original brief didn't hold up (BetterBriefs Project / IPA, October 2021). The same global study, still the largest of its kind, found that 80% of marketers believe they write good briefs, while only 10% of agencies agree.

That gap is where projects actually go wrong, before a single concept is sketched. A brief that's vague, over-stuffed, or missing basic context forces a design team to guess, and every guess shows up later as a missed deadline, a weak first draft, or a revision round that didn't need to happen.

This guide walks through seven steps for writing a brief that avoids that outcome: what to include, how much detail is useful, and where most clients accidentally leave a design team to fill in the blanks. Follow it and you'll hand your next project everything it needs to succeed on the first attempt, not the third.

Key Takeaways

• Describe the problem you need solved, not the design solution. Prescribing an answer up front is the most consistent mistake across agency guidance.
• Set specific, measurable objectives instead of subjective language like "make it modern."
• Disclose your real budget and timeline early. A hidden constraint doesn't protect you; it just produces work that doesn't fit it.
• Go beyond age and location for your audience. Include what they think, feel, and are motivated by.
• Treat briefing as a conversation. Agencies want to ask questions, and a live briefing session catches problems a document alone won't.

What you'll need before you start

Gather these before you sit down to write, and the brief itself takes a fraction of the time.

• A one-sentence problem statement: what's actually going wrong, not what you think the fix should look like
• Business, marketing, or design objectives, ideally specific enough to measure
• Audience input: existing personas, customer research, or at minimum a clear description of who the work needs to reach
• A real budget figure, even if it's a range
• A timeline, including any fixed dates the work has to hit
• Brand assets: logo files, style guide, past creative, and any non-negotiables

Time to prepare: 30 to 60 minutes if the inputs above already exist; longer if you need to pull them together first.
Difficulty: Beginner. Nothing here requires design expertise, just clear internal answers.

Step 1: Describe the problem, not the design solution

A good problem statement gives a design team something to investigate, not just a spec to execute.

The most consistent advice we give clients is also the easiest one to get wrong: describe the underlying problem and let the design team work out how to solve it. Prescribing a fix up front, "redesign the homepage with a hero video" instead of "visitors bounce before they understand what we do", closes off approaches a design team might have found more effective, and often more cost-effective.

This lines up with the Double Diamond, the UK Design Council's process model built around two rounds of divergent and convergent thinking: Discover and Define, then Develop and Deliver. Defining the problem clearly is treated as half the work of solving it (Design Council). The DBA's Jonathan Kirk puts it more bluntly: a creative brief isn't a copy of your business brief, it's a translation of it. It's reduced to its core and turned into plain English a design team can respond to, rather than restate (DBA).

In practice, that means writing "our checkout abandonment rate is highest on mobile and we don't know why" instead of "redesign the mobile checkout with a simpler layout." The first gives a design team a problem worth investigating. The second gives them a spec to execute, and removes the reason to hire experts in the first place.

The gap above isn't limited to whether a brief "feels" good. In the same BetterBriefs/IPA study, 78% of marketers believed their brief provided clear strategic direction, while only 5% of agencies agreed, and 83% believed their language was clear and concise, against just 7% of agencies.

Step 2: Make your objectives specific and measurable

An objective is only useful if a design team can design toward it, and if you can hold the finished work up against it afterward.

Vague objectives produce vague work. A brief that says "make it modern" gives a designer nothing to aim at. "Appeal to buyers aged 25 to 35 who currently see us as outdated" gives them a target. Push objectives to be Specific, Measurable, Achievable, Relevant, and Time-bound (SMART), and connect each level: a business objective like "become the top choice in our market" might translate into a marketing objective of shifting budget toward awareness, which in turn shapes what the design work is actually meant to achieve.

This matters beyond the brief itself: it's what makes the finished work evaluable later. Without a specific target, judging whether creative work "succeeded" becomes subjective, and subjective feedback is what makes revision cycles drag. That gap shows up elsewhere too. Separately, Gartner found that 84% of CMOs report high levels of strategic dysfunction within their own marketing organization, and those teams are 36% less likely to report strong business performance (March 2025). Objectives set at the brief stage are what feedback gets measured against later; skip them, and every review meeting reopens the same argument about what "good" even means.

Step 3: Define your audience beyond demographics

An audience description should give a designer something to design for, not just something to avoid alienating.

Almost every brief we receive has an audience definition in it somewhere. Almost none of them go far enough. Demographics (age, gender, income, location) aren't enough on their own. A strong brief also includes psychographics (attitudes, values, interests) and behavioral insight (how the audience thinks, feels, and acts), because the design team is creating for the end reader, not for the person signing off the brief.

The practical difference is what a design team can do with the information. "Women aged 25 to 40" tells a designer who to avoid alienating. "Time-poor professionals who feel guilty about convenience purchases and respond to reassurance rather than urgency" tells them what tone, imagery, and message will actually land.

Step 4: Put a real number on budget and timeline

Budget and timeline are the two constraints design teams most often end up guessing at.

A hidden or unrealistic budget is self-defeating. A design team working from an unstated budget designs toward its own guess, and if that guess is wrong in either direction, you either see ideas you can't afford or a scope smaller than what you actually paid for. Disclose budget upfront so deliverables can be scoped realistically; picking a cheaper option without adjusting scope is what tends to disappoint later. It's worth breaking the number down by category (creative, production, media) even for a single project, so the team isn't proposing ideas the budget can't support.

Timeline works the same way. Website timelines vary widely by scope, but the pattern is consistent: the tighter and less-defined the brief, the more likely a project drifts toward the long end of its range.

Underneath both is a cost worth naming directly: scope that isn't agreed upfront tends to expand anyway, and someone absorbs it. A 2018 PMI Pulse of the Profession analysis found that 52% of projects experienced scope creep in the prior year, up from 43% five years earlier (PMI). Unclear communication carries its own cost too: separate research estimates poor workplace communication costs U.S. businesses roughly $1.2 trillion a year, about $12,500 per employee (Grammarly Business and The Harris Poll, 2023). A brief that states budget, timeline, and scope clearly is what lets both sides catch a mismatch before it becomes unpaid extra work on one side or a missed deadline on the other. Go a step further and name how scope creep will actually be handled: who approves a new request, and whether it adds time or cost. That way the conversation happens once, upfront, instead of every time a stakeholder asks for "one more thing." If you're still working out a realistic number, that's a reasonable thing to bring to a scoping conversation before the brief is final.

Step 5: Hand over brand context, competitors, and one key message

A design team that doesn't know your market well enough can end up unintentionally repeating what's already out there.

A brief also needs to hand over what an agency can't be expected to know without you: your brand, your market, and the single thing you most need communicated. Competitor and market context is a core brief component, not an optional extra, and it earns its own paragraph rather than a passing mention folded into "brand." A design team working blind to what else exists in your category is more likely to produce something that unintentionally echoes a competitor or misses a gap you'd have wanted them to fill.

The message side is one of the hardest parts of briefing to get right. Briefs tend to get overstuffed with everything the business wants to say, when the strongest ones commit to a single key message and let features support it as proof points, rather than leading with something the audience doesn't yet care about. Brand guidelines and mandatories belong here too: logo usage, color, typography, imagery style, tone of voice, and any non-negotiables like partner logos or size constraints. Leaving these out doesn't give a design team creative freedom; it just means they'll design something you'll later ask them to redo once they discover a constraint you already knew about.

Step 6: List deliverables and who signs off

Everyone involved should know exactly what's being made and who has the final word on it.

Spell out the specific formats and outputs you expect: a homepage design, a five-page site, a full design system, source files, or all of the above. "A website" means something different to every stakeholder in the room, and a vague deliverables list is a quiet source of scope creep. Alongside deliverables, name the approval stakeholders and at which stages they weigh in. One clear decision-maker per review stage avoids the slowest failure mode in creative work: feedback from five people that contradicts itself, with no one able to say which note wins.

Step 7: Treat briefing as a conversation, not a handoff

Treated well, the brief stops being a document and becomes the start of a working relationship.

The last piece of this is less about what's written and more about how it's delivered. A live briefing meeting, rather than a document sent and walked away from, surfaces questions and problem-solving early, while they're still cheap to act on. The DBA's research backs this up directly: 30% of clients said they actively want their agency to ask more questions and push back on the brief, rather than accept it at face value (DBA).

A brief that invites questions tends to produce a stronger project than one that discourages them, not because the client did something wrong, but because a brief is a starting point for a conversation, not a finished contract. Being willing to have that conversation, and to be pushed back on, is itself part of briefing well.

This also covers the case where you don't have a full brief ready to hand over. If your inputs are thin, an agency worth hiring will draft the brief together with you, working from a discovery conversation instead of waiting for a polished document. Not having every answer up front isn't a reason to delay the kickoff call; it's often the reason to have it sooner.

Common mistakes to avoid

1. Prescribing the solution instead of the problem. This happens because it feels more concrete and easier to write than describing an open problem. Fix it by naming the symptom (what's failing, and how you know) and leaving the "how" to the people you hired to solve it.
2. Leaving the budget unstated or unrealistic. Clients often do this to avoid anchoring the design team low, but the opposite happens: without a number, teams either propose work you can't afford or assume a budget smaller than you actually have. State a real range, even an uncomfortable one.
3. Writing demographics without psychographics. Age and location are the easiest facts to gather, so briefs stop there. A designer can't design tone or imagery from a birth year alone; add what the audience feels, wants, and is skeptical of.
4. Sending the document and disappearing. A written brief feels complete, so it's tempting to treat it as the finish line. It's the start line. Schedule a kickoff conversation before work begins, not after the first draft disappoints someone.

Benefits of writing a design brief

A brief takes an afternoon to write, and it buys back time everywhere else in the project:

• Fewer redone rounds. A design team that isn't guessing at the problem, audience, or budget starts closer to what you actually wanted, which is largely where the wasted-budget statistic at the top of this guide traces back to.
• Work you can actually evaluate. Stated objectives give feedback something to check against, so "did this work?" gets answered by the brief, not by whoever argues loudest in the room.
• Fewer late surprises. A named budget, timeline, and approval process means nobody discovers a mismatch after the work is already done, when it's expensive to fix.

None of this replaces the conversation that should happen once the brief is written. It just makes that conversation shorter, and the work that comes out of it closer to what you needed the first time.

The design brief checklist

• Problem: the issue to solve, not the design solution itself
• Objectives: business, marketing, or design goals, ideally SMART
• Audience: demographics, psychographics, and behavioral insight
• Budget: a realistic figure, ideally broken down by category
• Timeline: target dates and any hard constraints behind them
• Brand context: guidelines, mandatories, competitors, one key message
• Deliverables: specific formats and outputs expected
• Approval stakeholders: who signs off, and at which stages

Not every project needs all eight in equal depth; a small refresh and a full rebrand call for different levels of detail. But leaving one out entirely is usually where later friction traces back to.

Write the brief, then talk it through

A good brief doesn't need to be long. It needs a real problem statement, objectives you can measure, an audience described beyond demographics, honest numbers on budget and timeline, and a named decision-maker for sign-off. Get those right and most of the friction that usually derails a project never shows up.

If you're starting from a blank page, Behold Design will help you build the brief itself. Get in touch and we'll work through it together before any design work starts.