How to Write a Design Brief

Eighty percent of clients think they write good briefs.

Only ten percent of agencies agree.

That is not a rounding error—it is the central finding of the BetterBriefs Project, the largest global study ever conducted on brief quality. Researchers surveyed 1,700 marketers and agency professionals across 70 countries and found a perception gap so wide it explains most of what goes wrong between clients and agencies. As Prof. Mark Ritson put it: "90% of marketers fail to brief agencies effectively, and their failures begin with a total lack of strategy."

The financial cost of that gap? An estimated 33% of project budgets are wasted on misdirected work—work that could have been avoided with a clearer starting point. Globally, that is roughly $350 billion set on fire because two groups of people thought they agreed on a direction when they didn't.

For founders, product managers, and solopreneurs about to hire a UX agency—especially for the first time—the brief is the single most important document in the entire engagement. It is more important than the contract. It is more important than the proposal. Because the brief shapes everything that follows: how accurately agencies can scope and price the work, how aligned the team is from day one, and whether the final product solves the right problem.

Get it right, and the project flows. Get it wrong, and you are paying for revisions, misunderstandings, and scope creep for months.

The good news: writing a strong brief isn't complicated. It doesn't require design expertise. It requires clarity about what you are trying to achieve, who you are building for, and what constraints you are working within.

This guide is built from agency research, creative director interviews, and industry data from professionals. Follow it, and you will send a brief that makes agencies want to work with you—not one that makes them sigh and start guessing.

You'll learn:

• What a design brief actually is (and the 5 things it is not)
• The 5 expensive mistakes that waste 33% of project budgets
• The 10 sections every good brief must include
• How to adapt your brief for different project types (mobile app, SaaS, e-commerce)
• Whether to share your budget (and exactly how to frame it)
• European-specific requirements most guides miss (EAA, GDPR, cultural norms)

Don't want to start from scratch?

Use our interactive Brief Builder to structure your brief.

Open Brief Builder →

---

Quick Reference: What Makes a Good Brief

---

What a Design Brief Actually Is (and Isn't)

Before you type a single word, you need to understand the function of this document.

A design brief is a strategic alignment document. It tells the agency what you are trying to achieve and why—it does not tell them how to design it. The UK Design Council puts it perfectly: "Designers are only as good as the brief you give them," but they critically warn clients not to "be tempted to say what you think the design should be."

What a brief is NOT:

• It is not a 25-page specification document. Long briefs often signal a lack of strategic focus rather than thoroughness.
• It is not a feature list. A laundry list of requirements ("we need a blog, a forum, a chatbot, and a dark mode") without context is not a brief; it is a shopping list.
• It is not a dictation of the solution. If you already know exactly what the interface should look like, you don't need a UX agency; you need a production artist. You hire a UX agency to solve problems, not to color within lines you have already drawn.

The Single Most Important Mental Shift

The goal is to describe the problem and the desired outcome, leaving creative space for the "how." You must pick the one outcome the work must achieve.

The best briefs align stakeholders before the project starts. They give agencies enough context to propose smart solutions. They set clear success criteria so both sides know what "done" looks like. And most importantly, they save time and money by preventing the expensive "I'll know it when I see it" loop of endless revisions.

💡 Pro Tip

Before you start writing, complete this sentence: "We need a UX agency to [design X] for [user type] to [achieve specific goal]." If you can't fill in all three blanks, you're not ready to brief.

---

Why Briefs Fail — The Expensive Mistakes

Bad briefs are not just annoying; they are financially toxic.

Not interested in bad briefs and mistakes? Skip to the next section.

A McKinsey/Oxford study of 5,400 IT projects found that large projects run 45% over budget and deliver 56% less value than predicted. The root cause of roughly 50% of these cost overruns? An inability to master strategy and stakeholder requirements upfront. Similarly, the PMI Pulse of the Profession report notes that 47% of unmet project goals trace back to poor requirements management.

When agencies look at a bad brief, they see risk. They see a client who doesn't know what they want, which means the project will likely go over budget due to scope creep. Here are the most common mistakes agencies see, and why they happen.

Mistake 1: Jumping to Solutions Instead of Problems

This is the number one error. Clients describe the feature they want to build rather than the problem they need to solve.

• Bad Brief: "We need a modern dashboard with dark mode."
• Good Brief: "Our users spend 20 minutes finding data that should take 2 minutes. We need to redesign the reporting flow to reduce time-on-task."

Design Tennis (Nov 2025) highlights this perfectly: "The #1 mistake is writing 'We need a new CMS' instead of 'Our marketing team can't update content without involving a developer.'" If you ask for a CMS, the agency will price a CMS. If you ask to save time, they might propose an automation tool that costs half as much.

Mistake 2: The Priority Trap

If everything is a priority, nothing is. You cannot have "fast, cheap, highest quality, and innovative" all as top priorities.

• Agency Insight: John Kovacevich of Agency SOS notes, "If the word 'and' or 'also' is in your proposition, you haven't succeeded."
• The Fix: Force yourself to rank your goals. If the budget is cut, what is the one thing that must survive? That is your priority.

Mistake 3: The "Apple" Fallacy

Agencies see this constantly. Unless you are selling premium consumer electronics to a mass market with a trillion-dollar brand equity, copying Apple’s minimalist aesthetic might destroy your conversion rate. Designing for your boss’s taste instead of your user’s needs is a guaranteed way to fail.

Mistake 4: The Kitchen Sink

This happens when stakeholders from every department add their requirements to the document. "We need a chatbot," says Sales. "We need a press section," says PR. The brief becomes a Frankenstein monster of conflicting goals. PMI data shows that 52% of projects experience scope creep. This usually starts right here, in the brief, by failing to say "no" to secondary features.

Mistake 5: Missing the Problem Statement

It sounds obvious, but it is often absent. Anna Vogt, CSO at VMLY&R, says: "The question most often missing from client briefs is a very pure, very simple understanding and definition of the problem." Without this, the agency is just decorating, not designing.

💡 Key Insight

Every mistake above traces back to one thing: the brief focused on what the client wants to build instead of what the user needs to accomplish. Flip that framing, and most problems disappear.

---

What Every Good Brief Includes

This is the core of your document. Whether you are using a slide deck, a Notion doc, or a PDF, these ten elements are the consensus requirements from industry leaders like Figma, the Design Council, and the IPA.

1. Problem Statement (The Most Important Section)

What is broken? What opportunity exists? Why now? If you get this wrong, the solution will be wrong.

• Bad: "We want to improve our app."
• Good: "Our SaaS onboarding has a 60% drop-off rate at step 3. Users who complete onboarding retain at 85%. We need to redesign the onboarding experience to reduce drop-off below 25%."

2. Goals and Success Metrics

What does success look like? How will both sides measure it? Avoid vague terms like "modernize" or "engage." Use numbers.

• Examples: Increase conversion rate by 0.5%, reduce support tickets by 20%, improve System Usability Scale (SUS) score to 80+.
• Constraint: Limit this to one primary goal and maximum two secondary goals.

3. Target Audience / Users

Who uses this product? Be mercilessly specific. "Everyone" is not a target audience.

• Bad: "Busy professionals aged 25–45." (That’s a category, not a target).
• Good: "Mid-level project managers at companies with 50–200 employees. They manage 5–8 concurrent projects, primarily use desktop during work hours, and are highly stressed by notification overload."
• Include: Tech sophistication, context of use (office vs. on the go), and their primary motivation.

4. Scope — What is In and What is Out

Using the "In Scope / Out of Scope" framework is your best defense against scope creep.

• In Scope: "Redesign of the checkout flow, user profile, and order history."
• Out of Scope: "The homepage, the blog, and the native mobile app." Being explicit about what you are not doing is just as important as what you are doing.

5. Budget Range

We will cover the strategy of sharing this in detail later, but it must be included.

• Requirement: Share a range (e.g., €40k–€60k).
• Context: State if this is approved budget or aspirational.
• Detail: Note if this covers design only or design + development.

6. Timeline

• Deadlines: Are they hard (e.g., "Must launch before Black Friday") or flexible?
• Reality Check: A simple project takes 6–10 weeks; complex projects take 16–24 weeks. If you need a complex platform in 4 weeks, you are setting the project up to fail.
• Team: When can you start, and who is available for feedback?

7. Brand Context and Existing Assets

Do you have brand guidelines? A design system? A logo? Or does the agency need to create these?

• Why it matters: If an agency assumes they can use your existing component library, but you actually need them to build one from scratch, their quote could be off by 40%.
• Assets: List what already exists (current product, previous designs).

8. Competitors and References

List 3–5 competitors to study. Tell the agency what they do well and where they fail.

• References: Provide examples of products (even outside your industry) that capture the "feel" you want.
• Be Specific: Don't just paste a link. Say, "We love the navigation structure of Stripe, but we hate their color palette."

9. Technical Constraints

• Tech Stack: React? Vue? Webflow? Shopify?
• Platform: iOS, Android, Responsive Web?
• Integrations: Must it connect to Salesforce, HubSpot, or a legacy ERP system?
• Accessibility: (See the European section below—this is non-negotiable).

10. Decision-Making Process

Who approves the designs? How many stakeholders give feedback?

• Bad: "The team."
• Good: "The Product Manager is the day-to-day lead. The CMO gives approval at the wireframe stage and final visual design stage."

How long should it be? Most agencies agree that 2–5 pages is the sweet spot. If it is longer than that, you haven't synthesized your thoughts enough.

---

Adapting Your Brief by Project Type

"We need a website" is a phrase that can result in proposals ranging from €15k to €150k. The more specific the brief is to your project type, the more accurate the proposals you will receive.

---

The Budget Question — Should You Share It?

This is the standoff. Clients don't want to show their hand for fear of being overcharged; agencies don't want to spend three days scoping a proposal for a client with no money.

Why agencies ask (and they're not wrong): Todd Anthony, an industry veteran, notes bluntly: "Budget determines outcome. There are projects that could cost $2,000 or $1,000,000." Without budget context, agencies can't scope appropriately. You will get wildly different proposals that are impossible to compare. Good agencies scope honestly to the budget or tell you it's unrealistic. Hiding the budget wastes weeks on mismatched proposals.

The honest counterpoint: Some clients fear price inflation—and it does happen. Clients new to agency hiring genuinely don't know what things cost and want to see the agency's floor price.

The practical recommendation:

Sharing a range gives the agency enough to scope without pinning you to a ceiling. If scope is uncertain, a paid discovery phase (€5k–€15k) is the safest way to de-risk a build.

⚠️ Important Note

Nearly every “share your budget” article is written by an agency. They benefit from knowing. That’s worth acknowledging. But the practical reality holds: without any budget signal, you’ll waste time on both sides.

---

Briefing European Agencies — What's Different

If you are hiring within Europe or targeting European customers, there are two massive factors that generic US-centric guides miss. One is legal, the other is cultural.

Legal Requirements Most First-Timers Miss

1. The European Accessibility Act (EAA) Effective June 28, 2025, the European Accessibility Act requires that almost all new digital products and services in the EU must be accessible.

• The Standard: WCAG 2.1 Level AA (via EN 301 549).
• The Risk: Penalties vary by member state but can be severe (up to €900,000 in Sweden).
• Action: Your brief must list "WCAG 2.1 Level AA Compliance" as an explicit requirement. If you leave this out, you are building a product that may be illegal to operate in the EU by the time it launches.

⚠️ Warning

The EAA applies to almost all new digital products sold or used in the EU—regardless of where your company is based. Non-compliance penalties vary by member state but can reach €900,000. If your brief doesn't mention accessibility, your agency may deliver a product that's illegal to operate.

2. GDPR & Privacy by Design In Europe, privacy is not a checkbox; it is a design constraint. Consent flows, "right to be forgotten" dashboards, and cookie settings must be designed from the start—not bolted on later. Fines can reach 4% of worldwide turnover. Your brief should mention GDPR compliance as a core design constraint.

Cultural Briefing Differences

The Adobe Blog notes that European design culture generally favors "design thinking, research, and academic rigor" over the "move fast and break things" approach often seen in the US. European agencies tend to expect more thorough, well-researched briefs and value a deeper discovery phase.

---

Send It, Then Talk About It

The brief is a conversation starter, not a final decree.

The IPA/BetterBriefs guidance states: "A brief sent only via email is an opportunity wasted." The document you write is just the artifact. The briefing is the process. Once you send the brief, schedule a call.

The best agencies will challenge your brief. They will ask "why" five times. They might even suggest that the problem you think you have isn't the real problem. That is a sign of a good agency, not a difficult one. Yves Béhar, the legendary designer, said, "I don't believe in briefs. I believe in relationships." He means that a piece of paper cannot replace the alignment that happens when two teams discuss a problem.

A Clearleft case study showed that even thoroughly written briefs often turn out to have "incomplete problem statements" once an agency does proper discovery. That is normal and expected. A brief that survives first contact with an agency unchanged probably wasn't challenged enough.

💡 Pro Tip

Send the brief 48 hours before the first call. Ask the agency to review it and come with questions, not a proposal. The quality of their questions will tell you more about their fit than the polish of their pitch deck.

---

Closing

Don't be on the wrong side of that 80% vs 10% gap.

The difference between a project that spirals 45% over budget and one that delivers high ROI often comes down to the first few pages of text you exchange. A good brief forces you to clarify your strategy, respect your budget, and focus on the user—three things that guarantee a better product.

Ready to write your brief?

Build your brief in 15 minutes. Our free Brief Builder structures everything covered in this guide into a step-by-step process.

Related Guides:

• How to Hire a UX Agency in Europe — Complete Guide
• How Much Does a UX Agency Cost in Europe?
• Questions to Ask When Hiring a UX Agency