How to Write a Design Brief That Gets You Better Agency Work

What Information Should Every Design Brief Include?

A complete design brief needs six essential components. Start with project context: what your company does, your target users, and the specific problem you're solving. Include your business goals—whether that's increasing conversion rates by 25% or reducing customer support tickets.

Next, define the scope clearly. List exactly what deliverables you expect: wireframes, prototypes, visual designs, design systems, or user research. Specify what's included and what isn't. If you only need UX work without visual design, say so upfront.

According to the Nielsen Norman Group, unclear project requirements are responsible for 37% of project failures, making a well-defined scope one of the most critical elements of your design brief.

Add your timeline with key milestones, not just a final deadline. Include your budget range—agencies waste time (yours and theirs) proposing solutions you can't afford. Finally, describe your team structure and decision-making process. Will the agency work with one point person or present to a committee?

How Do You Define Design Requirements Without Being Prescriptive?

Describe the problems you need solved, not the solutions you think you need. Instead of "We need a mobile app with a dashboard," write "Our field staff can't access customer data when they're on-site, leading to delayed service."

Provide constraints that matter: technical limitations, brand guidelines you must follow, accessibility requirements, or compliance needs. But avoid specifying design patterns or interface elements unless there's a genuine requirement.

Share examples of designs you admire, but explain what specifically appeals to you. "We like Stripe's dashboard because the hierarchy makes complex data easy to scan" is useful. "Make it look like Stripe" is not.

Give agencies room to propose creative solutions. The best firms will challenge your assumptions if they see a better approach.

What Context Helps Agencies Understand Your Users?

Agencies need to understand who they're designing for. Include demographic information, but focus more on behaviors, goals, and pain points. "Marketing managers at mid-size B2B companies who are overwhelmed by too many tools" paints a clearer picture than "35-45 year olds with college degrees."

If you have existing user research, share the key findings. Include quotes from customer interviews, usability test results, or support ticket themes. Don't make agencies start from zero if you already have insights.

Describe the user's current workflow and where it breaks down. What workarounds have they created? What tasks take longer than they should? This context helps agencies identify opportunities you might have missed.

If you're targeting multiple user types, prioritize them. Agencies need to know whether to optimize for your end customers or your internal admin team if their needs conflict.

How Should You Communicate About Budget and Timeline?

Be transparent about your budget range. You don't need an exact figure, but "$50-75K" helps agencies propose appropriate solutions. A $50K budget gets different recommendations than a $200K budget.

According to McKinsey research, projects with clearly defined budgets in the initial brief are 2.5 times more likely to be completed on time and within budget compared to those where budget discussions happen later in the process.

If your budget is flexible depending on the approach, say so. Some agencies will show you what's possible at different investment levels.

For timeline, distinguish between "must-haves" and preferences. "We're launching at a conference in October" is a hard deadline. "We'd like to start user testing by Q3" is flexible.

Flag any constraints that affect scheduling: holiday freezes, busy seasons when your team can't provide feedback, or dependencies on other projects. Agencies can work around these if they know upfront.

What Should You Share About Your Company and Team?

Provide background on your company stage and culture. A pre-revenue startup has different needs than a Series B company with product-market fit. Your risk tolerance, speed of decision-making, and feedback style all vary accordingly.

Introduce the team members who'll work with the agency. Who gives feedback? Who makes final decisions? How technical are they? Agencies adjust their communication style and deliverable format based on their audience.

Mention previous design work if relevant. If you're redesigning an existing product, explain what's working and what isn't. If past agency relationships didn't work out, briefly explain why—this helps new agencies avoid the same issues.

Be honest about organizational challenges. If stakeholder alignment is difficult or you're navigating a rebrand, agencies would rather know upfront than discover it mid-project.

How Do You Use a Design Brief to Filter Agencies?

Your brief should help the right agencies self-select. Be specific about what makes your project challenging—technical complexity, tight timelines, or limited budget. Agencies who aren't a fit will pass, saving everyone time.

Ask agencies to address specific questions in their proposals. "Describe your approach to designing for non-technical users" or "How would you handle user research given our eight-week timeline?" Their answers reveal how carefully they read your brief and whether they understand your needs.

A detailed brief attracts agencies who do thorough work. Firms that submit generic proposals probably didn't read it carefully—a red flag for how they'd approach your project.