Brand Guidelines Nobody Follows: What to Write Instead

The guidelines were signed off in June. In November a sales deck goes out with a stretched logo, a colour that is nearly but not quite right, and a headline written in a voice the business dropped two years ago. Nobody was careless. The person who built that deck opened the document, failed to find the answer in about four minutes, and did the reasonable thing.

Which is the whole diagnosis. Brand guidelines that nobody follows are a documentation failure, not a discipline failure. The usual response is to send the document round again with a firmer email attached. That has never worked and it is not going to start.

The position here is straightforward and slightly unpopular with the people who make beautiful brand books: length is not a measure of quality, and a document organised as a tour of the identity is organised for its author. It should be organised for somebody with a deadline, one specific question, and no interest whatsoever in the thinking behind the colour palette.

What follows is the shape we would use instead: guidance written as decisions, wrong examples given equal billing with right ones, rules delivered into the software where the work happens, and a short, honest list of what genuinely needs a rule at all.

Why the long PDF fails

Start by being fair to it. A long brand book is usually correct. Everything in it is true, considered and internally consistent. It fails anyway, and it fails for two reasons that have nothing to do with its content.

It is organised for the author

The standard structure runs: story, values, positioning, logo, colour, typography, photography, tone, applications. That is the order the work was done in. It is not the order anybody needs it in. A person opening the file has one question, phrased in the language of the artefact they are making, and the document is indexed by the language of the identity.

So the search fails. Someone wants to know whether they may set white text over a photograph on a poster. The document has a page called "Photography" and a page called "Colour" and a page called "Legibility", and the answer lives across all three, none of which is titled the way the question was asked. Four minutes later, a judgement call ships.

It lives where work does not happen

The second failure is physical. Work happens in a slide deck, a design file, a component library, a CMS field, an email builder. The rules live in a PDF on a shared drive, one context switch away. That gap gets crossed while people are still keen, and stops being crossed roughly a month after launch.

The result is drift, and drift is not a cosmetic problem. It is the mechanism by which a business slowly stops being recognisable, and by the time anyone notices, the fix has become expensive. Our parent company has written about what actually gets sold when a brand stops working, and a good share of those situations began as small, defensible, undocumented decisions taken under time pressure.

The moment a guideline is actually needed

Write for the moment of use. That moment is remarkably consistent: somebody is making something, they are near the end, they have hit a case the template did not anticipate, and they have a few minutes before the thing goes out.

Everything follows from taking that moment seriously. They will not read a rationale. They will not compare three pages. They will read one answer if it is where they are already looking, and otherwise they will decide for themselves and be slightly wrong in a way that compounds.

This also explains why guidance written before anything has been made tends to be the least useful kind. It answers imagined questions. Guidance written after the first serious application, whether a campaign or a site build, answers real ones. That is a separate matter from what should freeze before a website build starts, where the point is that certain decisions must be settled early precisely so the build does not settle them by accident.

Write guidance shaped like a decision

Most brand documentation describes states. "The logo is available in three variants." True, and useless at the point of use, because the reader has to convert a description into a choice on their own, and that conversion is where the errors enter.

Write the choice instead. Every unit of guidance should be a small if this, then that, titled with the situation rather than the asset. "Putting the logo on a photograph" is a better heading than "Logo variants", because it is what somebody would type into a search box at four minutes to five.

The form that works

Each entry gets four parts and no more.

• The situation, in the reader’s words. "Writing a subject line." "Choosing a colour for a chart." "Naming a feature." Not "Verbal identity", and definitely not "Secondary palette".
• The answer, in one sentence. A sentence somebody can act on without reading the next paragraph. If it needs a condition, the condition goes in the same sentence.
• One right example and one wrong example, side by side. Real artefacts, not diagrams of artefacts. The wrong one does more work than the right one, which is the next section.
• Who to ask when it does not fit. A role, not a name, so the entry survives someone leaving. Guidance without an escalation route produces silent improvisation.

The verbal side works the same way, and it is where description does the most damage. "Confident but approachable" cannot be applied to a sentence. A rewrite can. That is the whole argument behind a tone of voice document that actually changes copy: the useful artefact is a column of real sentences taken from your own website, rewritten, with a line about why the second version is the one you keep.

Show the wrong version, not only the right one

Almost every brand book shows correct usage. Very few show incorrect usage, and the ones that do usually limit it to a grid of logo abuses nobody was going to commit anyway: rotated forty-five degrees, filled with a gradient, squashed to half height.

That grid is the wrong kind of wrong. The mistakes that actually happen are near misses. A colour sampled from a screenshot rather than taken from the palette. A headline in sentence case where the system uses title case. A photograph that is technically on brief and emotionally somewhere else. A third-party template with the logo dropped in and everything else left exactly as the vendor shipped it.

So collect the near misses from your own history and publish them, with one line explaining what went wrong and one line explaining what to do instead. This feels uncomfortable, because it means putting flawed internal work in a document people outside the team will see. Do it anyway. A person recognises a mistake far faster than they recognise a rule, and the near miss is the only kind of wrong they are ever likely to make.

A rule that cannot be applied in the two minutes before something ships is not a rule. It is an opinion with a page number.

What brand guidelines actually need to cover

A rule has a cost. It has to be written, found, understood, applied and maintained, and every rule that exists makes the next rule slightly harder to find. So the question is not what could be standardised. It is what breaks when it varies.

Our test: rule the things that carry recognition, and the things with a technical consequence. Leave everything else to judgement and a good example. The recognition half is why distinctiveness beats differentiation matters here: the assets that make you identifiable at a glance are the ones worth defending in writing, and they are usually fewer than a brand team would like.

The rules with a technical consequence

Two areas deserve a rule for reasons no brand book usually gives. The first is colour pairing. A palette that looks confident in a presentation can produce text nobody can read on a phone in daylight, so publish the approved pairs and their contrast results rather than the swatches alone. WCAG 2.2 sets the thresholds, and the quick reference turns them into something a designer can check in a minute. A palette shipped without that table will produce inaccessible work forever, politely and at scale.

The second is typography, specifically the weights. Every weight named in the guidelines is a font file somebody has to load, and each one costs download time and risks a visible reflow when it arrives. Name the weights you have licensed and loaded, say plainly that nothing else exists, and note that a browser asked for a missing weight will fake it badly. The connection to Cumulative Layout Shift is direct, and this detail belongs in a brand document precisely because the brand document is what created the requirement.

Naming is the other place where a rule earns its keep, because a bad naming decision is close to permanent. What you want is not an approved list but a test and an owner, which is the substance of brand architecture for a small company.

Deliver the rules into the tools

Here is the part that changes outcomes more than the writing does: a rule embedded in a default is worth ten rules written down. If the only colours available are the ones in the palette people can pick from, the rule about colour has been enforced without anybody reading it.

So the deliverable list should include artefacts, not only a document. Design library components with the right spacing already applied. A slide template where the title slide cannot be built wrong. Locked text styles. A logo folder with variants named for the situation rather than the file format, because "logo-on-photo" gets picked correctly and "logo-rgb-alt-2" does not. Email and CMS blocks that only accept the fields the system supports.

The pattern generalises well beyond design software. A profile site assembled from structured widgets, as Nichevio does, is a brand rule expressed as a component: the person publishing chooses the content and the system supplies the treatment. Same move as a locked slide master, applied to a page. Wherever guidance can be converted into a default, convert it, then delete the paragraph that used to describe it.

Product surfaces need this most and get it least. Interface strings are brand output as surely as an advertisement is, and they are written by more people, under more pressure, with less review. Give them patterns rather than principles, which is exactly what a microcopy pass produces: real strings, rewritten, with the reasoning attached.

Who decides, and how a rule changes

Guidance that cannot change gets abandoned rather than amended. People hit a case it does not cover, improvise, and quietly stop treating the document as authoritative. The improvisation is not the problem. The absence of a route from improvisation back into the document is.

A loop that works, and costs almost nothing to run:

1. Somebody hits a case the guidance does not answer. This is normal and should be expected, rather than treated as evidence that the document was inadequate.
2. They make a call and ship. Deadlines win, always. Pretending otherwise is how guidance loses its credibility in the first month.
3. They log it in one line. What the case was, what they did. One line, one place, no form. If logging takes longer than deciding, nobody logs.
4. One named owner reviews the log on a fixed cadence. Monthly is usually enough. A committee is not required, and tends to slow the loop until it stops entirely.
5. Recurring cases become rules; single ones stay exceptions. And any new rule ships into the template as well as the document, or it will be ignored exactly like its predecessor.

Periodically, look at what actually went out rather than what was approved. A brand audit is useful here for an unglamorous reason: it measures drift against reality instead of intent, and drift is invisible from inside the team that caused it.

What we would write first

If you are starting over, write ten entries rather than a hundred pages. Take the ten questions your team has genuinely asked in the last quarter, answer each one in the four-part form above, and publish them where the work happens. Then stop, and wait to be asked something else. The visual identity and verbal identity work still has to be done properly. What changes is the shape in which it gets handed over.

The honest concession: this approach is worse in one situation, and it is a real one. If your work is executed largely by agencies, printers, franchisees or partners you cannot train and will never meet, a thorough document is the only instrument you have, and it needs to be exhaustive, unambiguous and slightly pedantic. Regulated categories are similar. There, length is the point. For an in-house team of any size it is overhead pretending to be rigour, and the sensible starting scope is closer to how much brand an early-stage company actually needs than to a two-hundred-page manual.

The test to apply to anything you write is a plain one. Hand it to somebody who was not in the project, give them a real task, and time them. If they cannot reach the answer in under a minute, the problem is the document, and no amount of reminding people to read it will change that.

If your existing guidelines are thorough and still ignored, that is a specific and fixable situation rather than a cultural one. Send us what you have and the last few things that shipped despite it.