Field note / brand identity / branding / documentation
Designing Brand Guidelines That Actually Get Used
How I write brand guidelines that designers and non-designers alike will actually reference and follow.
- Published
- Sep 17, 2019
- Length
- 3 min read / 522 words
- Topics
- brand identity, branding, documentation
Most brand guidelines I've seen are designed to be admired, not used. They're beautifully produced PDFs with full-bleed photography and elegant typography that live on a server and are never opened except during agency pitches.
Guidelines that get used look different. They're structured around real questions that real users have, not around showing off the brand system.
Who Actually Uses Brand Guidelines
Before writing a single page of guidelines, I identify who will actually use them. The answer is almost never "everyone in the company." It's usually: the internal marketing team, external agency partners, print vendors, and occasionally a non-designer department head who's commissioning a one-off piece.
Each of these users has different questions. The external agency needs complete technical specifications. The internal marketing coordinator needs clear do's and don'ts for quick decisions. The print vendor needs file formats and color specifications. The department head needs to understand what to ask for and what to reject.
Good guidelines serve all of these users without making any of them wade through content that doesn't apply to them.
Structure Around Questions, Not Components
The conventional brand guidelines structure is: logo, color, typography, imagery, examples. This structure organizes the guidelines around what the system contains rather than how to use it.
I prefer structuring around the questions the guidelines need to answer:
- How do I display the logo in this context?
- What colors can I use here?
- How do I choose a typeface for this use case?
- What does approved imagery look like?
- Here are some examples of correct and incorrect usage.
Same content, different organization — and the second organization is dramatically more useful for someone trying to solve a specific problem.
The Minimum Viable Spec
Every element in the brand system needs technical specifications that are complete enough to reproduce it accurately. For color: Pantone, CMYK, RGB, hex. For typography: typeface name, weight, size, tracking, leading. For spacing: relative to a defined unit, not just pixels.
If a specification is missing, someone will guess. Their guess will be wrong. Wrong guesses accumulate into brand drift.
Living Documents
Brand guidelines written as static PDFs are obsolete the moment they're published. Brand systems evolve. New applications emerge. Guidelines need to be updated.
I recommend clients maintain guidelines in a digital-first format — a web-based brand portal, a Notion workspace, a Figma file — where updates can be made without republishing a document. The friction of updating a PDF means updates don't happen, which means the guidelines and the reality of the brand system diverge.
The Examples Are the Most Important Part
Abstract rules are less useful than concrete examples. For every guideline, I include both correct usage examples and incorrect usage examples. The incorrect examples — the "don't do this" section — are often more instructive than the rules themselves.
Showing what the logo looks like with the wrong color, wrong spacing, stretched proportions, or placed on a conflicting background is the fastest way to teach someone what to avoid.