Brand guidelines people actually follow

Why most brand guidelines go unread

The usual failure is not that guidelines are wrong. It is that they were written to impress rather than to be used. A hundred-page document opening with a manifesto and a mood board looks impressive in a presentation and answers none of the questions a person actually has at the moment they open it.

The people who use guidelines are looking something up under time pressure. Someone building a slide needs the right blue. Someone writing an email campaign needs to know whether the brand uses contractions. Someone briefing a printer needs the print colour codes. Every one of them wants an answer in under a minute, and every one of them will guess if they cannot find it.

So we write for retrieval. Short sections with obvious headings, the answer before the reasoning, real examples instead of abstract principles, and a searchable format rather than a design-led document that has to be scrolled through. If the person guesses, the guidelines have failed regardless of how good they look.

What belongs in the document

Guidelines cover how the brand looks, how it sounds, and how it behaves in the places it appears. Anything that does not help someone produce work correctly is decoration.

On the visual side: logo files and which to use where, minimum sizes, clear space, approved backgrounds and a set of misuse examples. Colour with exact codes for screen and print, plus which combinations meet contrast requirements. Typography with the hierarchy spelled out, so people are choosing from defined styles rather than inventing sizes. Photography and illustration direction if the brand uses them, described concretely enough to brief someone.

On the verbal side: how the brand refers to itself, the terms it uses and avoids, how formal it is, and how it handles the awkward situations, which are the ones people get wrong. Applied examples matter more than rules here, and applied examples across the formats the team actually produces are what turn a document into a tool.

• Logo usage, minimum sizes, clear space and explicit misuse examples
• Colour codes for screen and print, with accessible pairings marked
• A defined type hierarchy rather than a list of fonts
• Voice and tone with worked examples, including what not to write
• Applied templates for the formats the team produces weekly

Voice and tone: the half that usually gets skipped

Most guidelines devote forty pages to visuals and half a page to writing, which is backwards. Customers read far more of your words than they examine your logo, and inconsistent writing is more noticeable than inconsistent spacing.

Voice is what stays constant: the personality that should be recognisable in everything you publish. Tone is what shifts with the situation, and the shift is where guidance is genuinely needed. The same brand should sound different in a sales page, a service outage notice and a refund refusal, and telling people how it flexes is more useful than telling them it is friendly and professional.

The most valuable pages are the ones covering difficult moments, because that is where people freeze and where an off-brand response does the most damage. How do you apologise. How do you say no. How do you explain a price rise. How do you answer a public complaint. Worked examples of those, with a bad version alongside the good one, get referenced far more than any section about the logo.

Fixed, flexible and forbidden

The most useful structural decision in a set of guidelines is to sort every rule into three categories, because it tells people where judgement is allowed.

Fixed rules cannot be varied: the logo files, the colour codes, the legal name, the trademark usage. Flexible areas invite judgement within limits: the photography style, layout choices, how playful a social post can be. Forbidden things are stated outright: stretching the mark, recolouring it, adding effects to it, using unapproved typefaces, and any specific misuse that has already happened.

Without this sorting, people either treat everything as sacred and cannot produce anything, or treat everything as advisory and the brand drifts. Naming which is which resolves most of the questions a designer would otherwise be asked, and it makes the guidelines usable by people who are not designers, which is most of the people producing work.

Keeping guidelines alive

A guidelines document that is finished is already decaying. New channels appear, new formats are needed, and situations arise that the original document did not anticipate. If there is no route to update it, people work around it and the document becomes a historical record.

So the practical questions matter as much as the content: who owns it, how someone requests an addition, where the current version lives, and how people know it changed. A version note at the top and a named owner solve most of it, and both cost nothing.

We also recommend a short walkthrough with the team rather than sending a file. Guidelines get used when people know what is in them and where to look, and fifteen minutes of orientation does more for adoption than another twenty pages.