A Better Design Brief Starts With the Problem, Not the Solution

Design brief worksheet, geometric sketches, color samples and pencil arranged on a warm sunlit desk

When a business commissions a logo, website or product, it often begins by collecting references, moodboards and examples it likes. Some teams prepare extensive presentations of colors and styles yet struggle to explain the problem the project is meant to solve. A design brief should do more than describe a desired appearance. It should establish why the work is necessary and what the business needs it to accomplish.

Why a collection of references may not be a good brief

A company preparing a new brand identity might send examples of global brands and request a minimal, premium, modern appearance. Those words communicate taste, but not why the current identity fails. Is the business entering a different market? Does its image fail to reflect product quality? Has its service portfolio expanded? Different problems call for different solutions even when the visual references are identical. References should support a discussion, not replace a problem statement.

Four things a design brief should explain

1. Business problem

Start with what is not working as intended. Customers may struggle to distinguish products, find services on a website or connect the existing brand with a new market. Separate observed evidence from assumptions. Not every project begins with quantitative research, but it should be clear which claims are verified and which still need investigation.

2. Project objective

Describe the outcome sought: make services easier to understand, establish a coherent identity across channels or improve a product for its intended users. Objectives should connect to the problem and provide criteria for evaluating proposals. Existing analytics and user research may help, but design alone cannot guarantee every commercial outcome.

3. Deliverables and constraints

Identify known uses, launch dates, budget ranges and technical or production limits. A branding project may need packaging, web and signage applications; product design may be constrained by materials, dimensions or manufacturing processes. If deliverables are uncertain, make their definition part of discovery rather than pretending every answer is already known.

4. Design preferences

Visual preferences matter, but explain why. Perhaps a typeface is preferred because it is legible, or a material is unsuitable because of maintenance requirements. The reasoning behind a reference allows designers to explore alternative solutions to the same need.

Turn design instructions into business problems

Compare “We want a minimal website like an international brand, with big typography and lots of animation” with “New customers struggle to understand our services. We need a site that explains each service clearly and makes contacting the team easier while maintaining a contemporary, professional image.” The first prescribes an appearance; the second identifies a problem and leaves room to explore layout, content structure, typography and interaction. Clients can still share ideas, but should distinguish objectives from suggested solutions.

How specific should a brief be?

The brief need not answer everything before kickoff. It should make the objective, audience, key constraints and decision authority clear. Some design decisions should remain open for professional investigation. Excessive prescription can restrict better options, while an overly vague brief leaves evaluation to personal taste. Define the challenge clearly without unnecessarily dictating the answer.

Use the brief throughout the project

A brief should not be filed away after kickoff. Revisit it when reviewing concepts and feedback. Ask whether new comments support the agreed objective or introduce a new requirement. If business priorities change, document the reason, approval and impact on scope and schedule. The brief then becomes a decision-making tool rather than merely an attachment to a quotation.

Before sending the brief

Check whether the company can explain the problem, objective, audience, initial scope, budget and key limitations. Where answers are missing, state the uncertainty and consider discovery or research with the agency. A productive engagement is not about writing the longest list of instructions. It is about building a shared understanding of the problem that design expertise should help solve. A better brief begins with why the work needs to exist, not simply what it should look like.

Related reading

Your Website Looks Great, But Why Aren’t Customers Enquiring?

References

Allinclusive, Design Project Brief (28 September 2026) · Fieldtrip, Creative Brief Template (2 September 2026) · Creative Project Management Association (12 May 2026)