A weak brief asks for deliverables. A strong brief explains what needs to change.

That distinction matters. When a design agency understands the business problem, the audience, and the ambition behind the work, it can do more than fulfil a request. It can question assumptions, identify opportunities, and design an answer that holds up beyond launch.

The best briefs aren’t the longest. They’re the clearest. They give the agency enough context to think well, while leaving enough room for the work to evolve.

Here’s how to brief a design agency in a way that creates focus, improves the working relationship, and leads to better outcomes.

Start with the reason the project exists

Before describing what you want made, explain why the project is happening now.

Perhaps the business has outgrown its identity. The website may no longer reflect the quality of the organisation behind it. A new product could be changing how customers understand the brand. Or several years of growth may have left teams working with a fragmented mix of messages, tools, and visual assets.

This context is more valuable than a list of outputs. It tells the agency what the work needs to solve.

A useful problem statement might sound like this:

Our offer has matured, but our brand and website still position us as the company we were three years ago. We need to communicate our value more clearly to enterprise buyers and give our commercial team a stronger platform for growth.

That gives us something meaningful to work with. “We need a new website” doesn’t.

Use AI to organise your thinking, not replace it

AI can help you structure a brief, identify missing sections, or turn a collection of notes into something more coherent. But a brief written entirely by AI isn’t always a better brief, particularly when the person prompting it isn’t clear on what the project is trying to achieve.

The risk is false clarity. The document may read well while relying on vague objectives, untested assumptions, or language that sounds strategic without making a meaningful choice. A polished brief can still be the wrong brief.

Before asking AI to write, make sure you can explain the problem in your own words. What needs to change? Why does it matter now? Who needs to be moved, and what should happen as a result? If those answers aren’t clear, the next step isn’t better prompting. It’s a conversation with the people closest to the business, the customer, and the challenge.

Use AI as an editor, organiser, or critical reader. Keep ownership of the thinking.

Define the outcome, not just the output

Outputs are the things an agency delivers: a brand identity, a website, a design system, or a digital product. Outcomes are the changes those things should create.

The two are connected, but they aren’t interchangeable.

A website could be expected to improve the quality of inbound enquiries, shorten a complex sales journey, make content easier to manage, or help a global organisation present itself consistently across markets. Each goal leads to different strategic, design, and engineering decisions.

Be specific about what success looks like. That might include:

  • A clearer position in a competitive category
  • Greater confidence among investors, partners, or enterprise buyers
  • Higher-quality leads from the website
  • Better conversion through a key user journey
  • A scalable brand system that regional teams can use consistently
  • Faster publishing and less dependence on developers for routine updates

Not every outcome needs a hard number at the start. But the direction should be clear enough to guide decisions and assess the result.

Give the agency the real business context

Good design responds to reality. Share the information that shapes that reality, including the parts that may feel obvious internally.

Who are your priority audiences? What do they care about? What prevents them from choosing you? How does the buying process work? Which competitors are gaining ground, and why? What has changed inside the business? Where is the current brand or platform creating friction?

The agency should also understand the organisation behind the project. A founder-led scale-up with a small decision-making team operates differently from a global business with regional stakeholders, governance requirements, and several layers of approval.

Useful context can include:

  • Business strategy and growth priorities
  • Audience research and customer insight
  • Existing brand strategy or positioning
  • Sales presentations and common customer objections
  • Website analytics and conversion data
  • Technical constraints and required integrations
  • Internal politics, dependencies, and previous attempts to solve the problem

You don’t need to package everything perfectly before sharing it. Raw information can be useful. Just distinguish between evidence, internal opinion, and decisions that have already been made.

Be clear about the audience

“Our audience is everyone” usually means the audience hasn’t been prioritised.

Design becomes more effective when it knows who it needs to move, what those people already believe, and what they need in order to act. A procurement lead assessing risk needs something different from a founder looking for momentum. A CTO evaluating a platform won’t follow the same journey as a prospective employee considering the culture.

Define your primary audience first. Secondary audiences matter, but they shouldn’t dilute the central decision.

For each priority group, clarify:

  • What are they trying to achieve?
  • What questions do they need answered?
  • What objections or anxieties stand in the way?
  • What action should they take?
  • What do they currently misunderstand about the organisation or offer?

This gives the agency a sharper basis for brand strategy, content, UX/UI design, and digital engineering. It also makes later conversations less subjective. Instead of debating whether someone “likes” a direction, the team can assess whether it will work for the people who matter.

Separate the fixed points from the open questions

Every project has constraints. The useful thing is to name them early.

A fixed launch date, regulatory requirement, technology stack, existing brand architecture, or legal naming convention can all shape the work. So can budget, internal capability, and the availability of key stakeholders.

At the same time, avoid turning preferences into constraints before the agency has had a chance to investigate them. “The site must use this navigation” is different from “customers need to find these four services quickly.” The first prescribes an answer. The second explains the need.

A strong brief makes three things visible:

  1. What is fixed: decisions or constraints that cannot change.
  2. What is preferred: ideas the team currently favours but is willing to test.
  3. What is open: questions the agency is being asked to help answer.

This prevents wasted effort and creates the right space for strategic thinking.

Share references, then explain them

Reference material can help an agency understand your expectations, but a folder of links without commentary often creates more ambiguity than clarity.

When sharing examples, explain what you respond to. Is it the clarity of the information? The restraint of the visual system? The way motion supports the story? The confidence of the writing? The structure of the user journey?

It’s equally useful to show what feels wrong and say why.

References should open a conversation, not predetermine the design. The goal isn’t to reproduce someone else’s answer. It’s to understand the qualities the work should embody, then create a system grounded in your own strategy and context.

Name the decision-makers

Projects slow down when participation and authority are confused.

Some people need to contribute expertise. Others need to be consulted at key moments. A smaller group should make the final decisions. If everyone has equal approval power, feedback becomes a negotiation between personal preferences.

The brief should identify:

  • The project owner
  • The final decision-maker
  • The core working team
  • Subject matter experts
  • Technical or legal approvers
  • Stakeholders who need visibility but don’t approve the work

Agreeing this structure at the start protects momentum. It also gives feedback a clearer route. The best feedback relates to the agreed strategy, audience, and objectives, rather than proposing isolated visual changes.

Be open about budget and timing

Budget isn’t an awkward detail to reveal after the thinking is done. It is a design constraint, and useful constraints help teams make better choices.

A clear investment range allows the agency to propose the right scope, team, and level of depth. Without it, both sides can spend time developing an approach that was never viable.

The same applies to timing. If a date is immovable, explain why. A public launch, funding round, product release, or industry event creates a different planning context from an internal target that can move.

Be realistic about your own team’s availability too. Workshops, interviews, content reviews, technical decisions, and approvals all require client time. An ambitious schedule only works when the organisation is ready to participate.

Treat the brief as a starting point

A good agency won’t simply accept every line of a brief as fact. It will test the framing, look for gaps, and ask questions that may change the shape of the project.

That isn’t resistance. It’s part of the value.

We see the brief as the beginning of a shared definition process. Early discovery turns assumptions into evidence, clarifies priorities, and creates alignment before significant time is spent on design or engineering.

The strongest client-agency relationships leave room for that process. They combine a clear ambition with a willingness to learn.

What a useful design brief should contain

You don’t need a complicated template. In most cases, a focused brief can cover:

  •  The business and why this project matters now
  • The problem that needs to be solved
  • The primary and secondary audiences
  • The outcomes that will define success
  • The expected scope or known deliverables
  • Relevant research, data, and existing materials
  • Fixed constraints, preferences, and open questions
  • Budget range and target timing
  • Stakeholders, decision-makers, and approval process
  • Reference points, with an explanation of what is relevant

If some of these answers are unclear, say so. An honest gap is more useful than false certainty, and it often reveals where discovery should begin.

Better briefs create better work

The quality of a project isn’t determined by the brief alone. But the brief establishes the conditions in which good work can happen.

Give the agency the problem, the context, the ambition, and the constraints. Be clear about what success means. Then create enough space for the team to challenge, explore, and apply its expertise.

That’s how a brief moves from a request for design to a foundation for impact.

If you’re preparing a brand or digital project and want to sharpen the thinking before the work begins, let’s talk about your project.