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

An ideal design brief is not a list of favorite colors and names of competitors to "look like." It is a document that describes a business problem, providing enough context for the designer to make informed choices rather than guessing. The difference between these two types of briefs determines the overall quality of the project, from approval speed to the actual value that the design creates.

Why most briefs don't work.

Most briefs are written from the perspective of the client, not from the perspective of the end user or the market. The central question often is "what do we want to see" instead of "what does the target customer need to feel in order to take action." As a result, the designer receives a list of aesthetic requirements and must infer the business context, or simply follow the instructions without understanding.

Marty Neumeier, in his book The Brand Gap, defines a brand as "the gut feeling of the customer, not the logo or tagline." Following that logic, a good brief does not describe the desired form but rather the feeling that needs to be created, along with the business reason behind that feeling. When a brief overlooks this layer, the design may look visually appealing but fails to operate in the real market.

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

Wally Olins, On Brand

The portrait of a well-placed brief.

A usable brand design brief answers six questions in order. Not all need lengthy answers, but all must be asked before starting the design.

• What is the business problem. Not "wanting a new logo" but rather: who are we losing customers to, for what reasons, and where can design intervene in that chain.
• Who is the target customer and what are they thinking. Not general demographics but rather: they are facing a purchasing decision, what is preventing them from choosing us.
• How do we want to be positioned. Not as "professional, reputable, creative" but rather: compared to the options that clients are considering, what do we need to be remembered for specifically.
• What does success look like. Approval criteria cannot be "I like it." It must be: does this design communicate X to Y group of people?
• What are the limits. Budget, timeline, existing assets to retain, channels to be implemented.
• Who makes the final decision. This question is rarely written in the brief but determines the speed of the entire project.

The most common mistake: preferences replacing strategy.

There is a recurring scenario in many brand design projects: the brief lacks answers to the business problem but contains numerous aesthetic references. "I like the color tone of brand A, the font of brand B, a minimalist yet warm feel." The designer will execute it. The client will approve based on personal taste. The final result is something no one truly opposes, but it also fails to address anything.

This is the point Sinh Vũ refers to as "the boss likes it, so we do it": when design decisions are made by the loudest voice in the room, not by data about the market or target customers. The aesthetic taste of the business owner does not outweigh the feelings of those who will spend money to buy.

These two numbers do not speak to beautiful design. They speak to design that solves the right problem. And the right problem only emerges when the brief has asked the right questions from the start.

The hardest part: defining success criteria.

This is the most frequently overlooked item in the brief, yet it is the most important when it comes to the approval stage. Without objective criteria, the approval meeting will turn into a debate about aesthetic taste. Each 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 just the client's responsibility.

A common misconception is that clients write the brief themselves and send it to the studio. In reality, the best brief is the product of a dialogue. The studio needs to ask enough questions to understand the context, and the client needs to be open to sharing real business information, not just aesthetic requests.

This is why the discovery phase is not a mere formality but a mandatory step before opening the design file. During this phase, the goal is not to gather visual references but to clarify the business problem to the extent that both parties can articulate it to each other without looking at paper.

When the brief achieves that level of clarity, every subsequent design decision, from colors and typography to information layout, can be explained through business logic rather than "I feel this way." And when the design can be justified, it can also withstand unfounded revision requests.

Start with the right questions.

If you are preparing a design project, try to answer this question before sending a brief to any studio: "If this design works as expected, what will change in our business in the next 12 months?"

If the answer is "we will have a better logo," the brief is not ready. If the answer is "we will be recognized in segment X, reduce the time needed to explain to new customers, and can start charging higher prices without further justification," that is the foundation for writing a valuable brief.

Design cannot solve a problem that has not been articulated. The task of the brief is to articulate that problem honestly and specifically enough for the work to truly begin.