A design brief is about business goals, not the boss's preferences.

A good design brief is a document that describes a business problem, with enough context for the designer to make informed choices rather than guess. A list of favorite colors, or the names of competitors you want to “look like,” is not a good brief. The difference between these two kinds of brief determines the quality of the entire project, from approval speed to the real value the design creates.

Why most briefs don't work

Most briefs are written from the perspective of the person commissioning the work, not from that of the end user or the market. The central question is usually “what do we want to see” instead of “what does the target customer need to feel in order to act.” As a result, the designer receives a list of aesthetic requirements and has to infer the business context, or simply doesn't and just follows the list.

Marty Neumeier, in The Brand Gap, defines a brand as the customer's perception, not a logo or a tagline. By the same logic, a good brief doesn't describe the form you want. It describes the perception that needs to be created, and the business reason behind it. When a brief skips this layer, the design may look beautiful but won't work in the real market.

Design is not decoration. Design is solving problems in a way that people want to see.

Wally Olins, On Brand

Portrait of a brief that is in the right place

A workable brand design brief answers six questions in order. Not all of them need long answers, but all of them must be asked before design begins.

• What is the business problem. The question is not just "we want a new logo". It is: who are we losing customers to, for what reason, and at what point in that chain can design step in?
• Who is the target customer and what are they thinking. Don't stop at generic demographics. You need to know what they face when making a purchase decision and what is stopping them from choosing you.
• How do we want to be positioned. The answer is not just "professional, trustworthy, creative". It is: compared with the options your customers are weighing, what specifically do we need to be remembered for?
• What does success look like. The approval criterion cannot be "I like it". It has to be: does this design communicate X to Y group of people?
• What are the constraints. Budget, timeline, existing assets to keep, and the channels where the work will be deployed.
• Who makes the final decision. This question is rarely written into a brief, yet it determines the pace of the entire project.

The most common mistake: preferences replacing strategy.

A scenario repeats across many brand design projects: the brief has no answer to the business problem, but plenty of aesthetic references. “I like brand A's color tone, brand B's typeface, a feeling that's minimal but warm.” The designer does the work. The client approves by taste. The final result is something nobody really objects to, but that doesn't solve anything either.

This is what Sinh Vũ calls “the boss likes it, so we do it.” It's when a design decision is made by the highest-ranking person in the room, not by data about the market or the target customer. A business owner's taste doesn't outweigh the perception of the person who will spend money to buy.

These two numbers are not about beautiful design. They are about design that solves the right problem. And the right problem only emerges when the brief asked the right questions from the start.

The hardest part: defining success criteria.

This is the section most often left blank in a brief, and also the most important one when the approval round arrives. Without objective criteria, the approval meeting turns into a debate about taste. Every opinion carries equal weight because there is nothing to measure against.

Success criteria do not need to be complex. A few specific questions are sufficient: When this design is placed alongside three main competitors, does it stand out clearly? For someone unfamiliar with the brand, can they identify the industry and segment within five seconds? How do decision-makers in the industry react when they see it for the first time?

These questions can be tested. They transform the approval meeting from a vote on preferences into an evaluation based on previously agreed-upon objectives.

The brief is not the client's job alone

A common misconception is that the client writes the brief alone and sends it to the studio. In reality, the best brief is the product of a conversation. The studio needs to ask enough questions to understand the context, and the client needs to openly share real business information, not just aesthetic requirements.

This is why the discovery phase (exploring and understanding the business) is a required step before opening any design file, not a formality. In that phase, the goal is to clarify the business problem so well that both sides can restate it to each other without looking at the paper, not to collect visual references.

When a brief reaches that level of clarity, every later design decision can be explained through business logic instead of “I feel it should be like this.” That applies to color, typography, or how information is arranged. When a design can be explained, it can also be defended against revision requests that have no grounding.

Start with the right questions.

If you are preparing a design project, answer this question yourself before sending a brief to any studio. The question is: “If this design performs as expected, what will change in our business over the next 12 months?”

If the answer is “we'll have a nicer logo,” the brief isn't ready. If the answer is “we'll be recognized in segment X, spend less time explaining ourselves to new customers, and be able to start charging more without further justification,” that is the foundation for writing a brief with real value.

Design cannot solve a problem that has not been posed. The job of a brief is to pose that problem honestly and specifically enough that the work can actually begin.