Why Brand Guidelines Fail and How to Write Ones That Don't

The Document Nobody Reads

I've delivered brand guidelines that were beautifully designed, comprehensive, and completely ignored. The marketing team kept using the wrong blue. The social media manager kept stretching the logo. The agency they hired for a campaign went off in a completely different typographic direction.

The guidelines existed. They just didn't work.

After enough of those failures, I started treating brand guidelines as a design problem in their own right — not just a documentation task at the end of the project.

Why Most Guidelines Fail

They're too long. A 120-page brand bible communicates thoroughness, not usability. Nobody opens it when they need a quick answer.

They show the rules without showing the why. "Don't place the logo on a busy background" is a rule. "The logo needs clear space because it loses legibility against complex patterns" is a reason. Reasons are memorable. Rules are not.

They only show what's correct. Showing correct usage without showing common mistakes leaves people to discover those mistakes through experience — usually expensive experience.

They're not accessible to non-designers. Brand guidelines are often used by people who aren't designers: marketing coordinators, sales teams, franchise owners, vendors. If the language assumes design knowledge, it's excluding the people who need it most.

How I Write Guidelines That Work

Lead with principles, not rules. Before any specific usage guidance, I write two or three paragraphs about the brand's personality and visual philosophy. Why does it look the way it looks? What is it trying to communicate? Someone who understands the intent can navigate edge cases the rules don't cover.

Keep it short. The primary guidelines document should fit in 20-30 pages maximum. Everything not essential goes in an appendix or a separate reference document.

Show the wrong thing. The most useful pages in any brand guidelines are the "don't" pages. Show the logo stretched. Show the wrong color applied. Show the type set in the wrong font. These images communicate faster and more memorably than any written rule.

Write for non-designers. I avoid design jargon where plain language works just as well. "Don't change the logo proportions" instead of "maintain aspect ratio." "Use these exact colors" with swatches and values instead of assuming people know how to use hex codes.

Make the assets easy to find. Guidelines without accessible assets are useless. I always link directly to the asset library from the guidelines document, and I organize the assets so the most commonly needed items are in the first folder.

Format Decisions

I've moved away from delivering PDF guidelines as the only format. PDFs are non-interactive, hard to search, and go stale immediately.

For clients who have the infrastructure, I build brand portals — web-based documentation with downloadable assets, search functionality, and the ability to update without redistributing a file. For clients who don't, I structure the PDF to be as navigable as possible: clickable table of contents, clear section headers, consistent page layouts.

The format should match how the brand guidelines will actually be used — which means understanding who uses them and when before deciding how to build them.

The Test

I give the guidelines to someone who has no design background and no prior knowledge of the brand. I ask them to produce a simple brand application — a business card, a social post header.

If they get it roughly right, the guidelines work. If they make the predictable mistakes, the guidelines failed — and I need to figure out where the failure was and fix it.

Documentation is only successful if it produces correct behavior. That's the only test that matters.