Abstract geometric composition illustrating your brand guidelines are a museum, not a toolkit

August 2019 ยท Branding

Your Brand Guidelines Are a Museum, Not a Toolkit

A ninety-page PDF that documents what the brand looked like the day it was approved is not the same thing as a system anyone can build with.

A client sent me a PDF last Tuesday and called it a brand system. Ninety four pages. A cover, a letter from the CEO, four pages on the history of the wordmark, a two page spread on clear space with diagrams.

I asked what a headline looks like on an Instagram Story. Nothing in the document.

I asked what happens when the logo has to sit on a photo that is neither light nor dark, which is most photos. Also nothing.

The PDF was not wrong. It was accurate and beautifully typeset. It documented what the brand looked like on the day it got approved, which is a very different job from helping anyone make the next thing.

Guidelines that describe the brand are a museum. Guidelines that let a stranger build something new are a toolkit, and almost nobody ships the second one.

A museum is organized by artifact. Here is the mark. Here is the palette. Here is a photograph of the mark in the palette. A toolkit is organized by decision. What do I do when the headline runs long. What do I do when the product shot is busy. What do I do when legal wants forty words in a space built for twelve.

Look at what actually gets used. Mailchimp put its voice and tone guide on the open web and wrote it as instructions for a human being in a specific situation, not as a description of a personality. Shopify shipped Polaris with working code. IBM did the same with Carbon. None of those are prettier than the PDF on my desk. They are just usable at two in the afternoon by somebody who has a thing due at four.

Here is the part that gets lost. The people who need guidelines most are the ones furthest from the room where the brand got made. A junior designer at a partner agency. A regional coordinator building an event flyer. A sales engineer assembling a deck on a plane. They will not read ninety four pages. They will search for the one answer they need, fail to find it, guess, and ship the guess.

They will search for the one answer they need, fail to find it, guess, and ship the guess.

So write the ugly parts. Document the edge cases, the failures, the two or three things somebody did last year that you never want to see again. Put it somewhere with a search box. Give it an owner who answers questions in an afternoon, because a system without a maintainer is just a file.

Truffles has a brand system. Sit on the warm thing. Every decision she makes follows from it, and she has never once needed a document to explain herself to Barnaby. If your rule cannot survive being said out loud in one sentence, ninety four pages will not save it.