BRAND / FIELD NOTE 01
How to write a useful brand identity brief
A useful brief is not a list of preferred colors. It is a compact decision-making tool that explains what the business needs to achieve, who it needs to reach, and what the finished identity must do in the real world.
Start with the change you need
“We need a logo” describes a deliverable, not the problem. Explain what has changed or what must change. Perhaps a new business needs credibility, an established company has outgrown an inconsistent identity, or a product must enter a more competitive category. A designer can make stronger choices when the business situation is visible.
State one primary outcome in plain language. Examples include improving recognition among a specific audience, unifying several services under one master brand, or building a flexible identity that works in an application interface and on physical packaging.
Describe the business precisely
Include what you offer, how customers buy it, where you operate, your price position, and the qualities that make the offer meaningfully different. Avoid broad claims such as “high quality” unless you can explain how customers experience that quality.
Share your short-term reality and longer-term direction. An identity designed only for today’s single product may become restrictive if five related products are planned next year.
Define the audience as people, not demographics alone
Age and location are useful, but behavior and motivation are more useful. What problem brings the customer to you? What do they already believe? What makes them hesitate? Where will they encounter the brand, and what do they need to understand in the first few seconds?
If there are several audiences, rank them. A visual identity cannot communicate everything equally to everyone. Clear priority produces clearer design.
Map the competitive context
List direct competitors, alternatives, and visual conventions in the category. Explain which conventions support recognition and which make every company look interchangeable. The goal is not automatic opposition to competitors; it is knowing where differentiation creates value.
Include links or screenshots and note exactly what you think works or fails. “I like this” is less actionable than “the strong hierarchy makes the service easy to understand on mobile.”
List the real applications
Identify where the identity must perform during the first year: website header, social avatar, proposals, invoices, uniforms, packaging, vehicle graphics, storefront signage, app icon, presentation slides, or event materials. Note technical limitations such as one-color printing, small engraving, embroidery, or screens with limited space.
This list shapes the system. A single beautiful logo file is not enough when the brand needs multiple responsive configurations, readable type, practical colors, and rules for photography or illustration.
Separate requirements from preferences
A requirement is a condition the project must satisfy: an existing name, a legal line, accessibility contrast, or compatibility with a parent brand. A preference is a direction you currently favor. Labeling them honestly gives the designer room to test better answers without ignoring genuine constraints.
Clarify process, ownership, and feedback
Name the final decision-maker and the people who provide input. Agree on how feedback will be collected so the project does not become a sequence of conflicting personal reactions. Useful feedback refers to the brief: audience fit, clarity, differentiation, usability, and business goals.
Also state the target launch, expected deliverables, budget range, required file formats, and any licensing or ownership needs. These details affect scope and should be settled before design production expands.