Every brand book has a launch party. There are canapés. Someone from the agency clicks through 120 beautiful pages while the leadership team nods at the logo’s “breathing room”. A PDF is emailed to all staff and then, like a gym membership bought in January, never touched again.

Six months later the sales team is using a logo screenshotted from the website, the Jakarta distributor has invented a fourth shade of blue, and HR has discovered Papyrus. Nobody broke the rules on purpose. Nobody knew where the rules were.

I have written several of these documents and watched most of them die. So, first, what they are for.

Brand guidelines are the documented rules and ready-made resources that show anyone, inside or outside an organisation, how to present the brand correctly: logo, colour, type, imagery, voice and behaviour, explained with examples, reasons and files they can actually use.

Note the last bit. Files they can use. That is where most guidelines fail.

Why does nobody read brand guidelines?

Not because people are lazy. Because most guidelines are written for the wrong reader.

The typical brand book is designed to impress the client who paid for it. It opens with twelve pages of manifesto, spends another eight on the logo’s origin story and buries the hex codes on page 87, if it includes them at all.

Talk to any web developer and you will hear the same grievance: a book born in print, with colours only in CMYK, type sizes in points, no web fonts and no thought for screens. The web team never brought it to a meeting. Why would they? It had nothing to say to them.

The other killers are familiar. Rules without reasons, which invite quiet mutiny. Files stored on a shared drive four folders deep, in a document called Brand_Guidelines_v3_FINAL_revised. And the guide that was accurate on its launch day and has been drifting out of date ever since.

Length is not the core problem. Uselessness is. A long document full of answers gets used. A short one full of adjectives does not.

The most beautiful manual nobody was allowed to follow

Designers have a favourite brand manual, and it has a strange history.

In 1974 the studio Danne & Blackburn designed NASA’s “worm” logotype, and the Graphics Standards Manual that went with it laid down, in meticulous detail, how the new identity should be applied across the agency. It is a gorgeous piece of work. In 1992 NASA rescinded it, brought back the old “meatball” insignia, and the manual went out of print.

Then, in 2015, two designers at Pentagram ran a Kickstarter campaign to reissue it as a book. They asked for US$158,000. They raised US$941,966 from 8,798 backers. In April 2020 the worm returned on the SpaceX rocket carrying NASA astronauts for the Demo-2 flight, though NASA was careful to say the meatball remained its primary symbol.

NASA’s own film on the return of the worm.

The lesson for the rest of us is double-edged. A brand manual can become so admired that people pay to own it decades after its owner stopped using it. It can also become a monument, sitting on coffee tables instead of desks.

Admiration is lovely. It does not get your logo printed correctly on a forklift.

What should brand guidelines include?

Less than you think, and more precisely than you think.

A one-page why. What the brand stands for and who it serves, in plain language. One page. If you need twelve, the strategy is not finished.

The logo, with numbers. Vague advice like “give the logo room to breathe” is decoration. Spotify’s guidelines for partners tell you the full logo must be at least 70 pixels on screen or 20 millimetres in print, that the clear space around it is half the height of the icon, and that the green version belongs only on black or white. You can argue with those rules. You cannot misunderstand them.

Colour in every format. Hex, RGB, CMYK and a print reference, side by side, plus which combinations pass accessibility contrast. Digital teams will thank you. Loudly.

Type that works everywhere. The licensed brand fonts, and also the fallbacks for email, slide decks and the laptop of a freelancer who does not own them.

Imagery, with examples. Show three photographs that are right and three that are wrong. A picture of a bad picture explains more than a paragraph about “authentic moments”.

Voice and tone. More on this below, because it is where guidelines get interesting.

Templates. Letterhead, slides, social posts, email signatures, the proposal cover. Every template is a rule nobody has to remember.

A named human. Who to ask, and how fast they reply.

Voice is the hard part

Anyone can specify a colour. Writing down how a brand sounds is harder, and the best public guides show how.

Mailchimp published its content style guide openly, under a Creative Commons licence, and invited other organisations to adapt it. Its central idea is that voice stays constant while tone shifts with the reader’s mood: you are the same person with your best friend and with your boss, but you choose different words. It also tells writers that humour is optional, and that a forced joke is worse than none.

Monzo’s tone of voice guide goes further and puts the advice in a table. Its three principles (straightforward kindness, everyday magic and warm wit) are dialled up or down by channel. Warm wit is switched off for operational messages and customer service, and turned all the way up for organic social.

The guide also bans the kind of seasonal pun that makes readers groan, with “eggcellent” singled out for Easter. That is a rule a writer can apply at 4.55 on a Friday.

Atlassian makes a similar point about timing. Its voice is described as bold, optimistic and practical with a wink, and the wink is reserved for moments when the user is likely to be in a good mood. Nobody wants a joke inside an error message about lost work.

Notice what these guides have in common. They describe behaviour in situations, not personality in adjectives. “We are friendly” is a horoscope. “No jokes in outage notices” is a guideline.

What to cut

Brutal editing is a kindness to your readers. Here is my usual hit list.

The founder’s poetry. The page explaining that the logo’s curve represents “the gentle arc of possibility”. Mood boards that were useful during the project and mean nothing afterwards.

Rules for situations that have never happened. Rules nobody can check. And every sentence that begins with “Our brand is”, unless it ends with something a person could actually do.

Picture a Singapore logistics firm with a 96-page brand book. Strip it back to what a driver, a salesperson, a recruiter and an external agency each need to do their jobs, and it becomes about twenty pages and a folder of templates. The other seventy-six pages were for the board meeting. They can live in an appendix, where they will be equally unread but less in the way.

Stop sending PDFs

The best guidelines have stopped being documents. They have become systems.

The GOV.UK Design System, maintained by a team at the Government Digital Service, gives anyone building a British government service ready-made styles, coded components and tested patterns for tasks such as asking for a name or an address. Teams do not interpret the rules. They install them.

The team behind the GOV.UK Design System on running it as a service.

Anyone working on government services can propose a new component, and content changes are suggested through GitHub, so the system improves as it is used. GOV.UK’s brand guidelines, published in June 2025, were updated again in March 2026. Living documents get updated. Monuments get dusted.

Singapore has taken the same road. The Singapore Government Design System offers shared foundations for colour, type and design tokens, plus components that drop into React, Vue, Angular and other frameworks, so a new government service starts from the brand instead of approximating it.

You do not need a civil service to do this. A shared Canva or Figma library, a set of locked templates, a brand portal with download buttons and a page of copy examples will beat a gorgeous PDF every time. Software engineers worked this out long ago: if nobody will read the style guide, make the tools enforce it.

Why can’t the brand police fix this?

Because nobody ever achieved consistency by decree. In the 1990s, design firms were happy to boast about dodging Hewlett-Packard’s “design police”. The more a brand team behaves like a traffic warden, the more creative people become at parking illegally.

Teaching works better. Caterpillar ran workshops for everyone who bought design services, explaining how its identity system worked and why. People who understand why a rule exists tend to keep it. People who are merely told tend to find the loophole.

There is a further catch. The measures organisations rely on most, such as emailing the manual to everyone, are the easiest to count and not necessarily the ones that work. What matters more is managers setting an example. If the chief executive’s slides ignore the template, so will everyone else’s.

And sometimes the cleverest guideline is permission. Kumamoto Prefecture created its bear mascot Kumamon in 2010 to attract visitors after the Kyushu Shinkansen opened, then let any individual or group use the character free of charge, provided the product promoted the prefecture’s goods or services. Within two years, sales of Kumamon goods ran to tens of billions of yen. A rule that says yes, under clear conditions, travels further than ten that say no.

Kumamon at Kumamoto Castle: a mascot anyone may use, on clear conditions.

Your newest reader is a machine

Here is a twist the 120-page PDF never anticipated. Brand guidelines are now being fed into AI design tools, which produce slides, social posts and web pages on brand, or nearly. Designers comparing results disagree on the best input: some find a guidelines PDF works well, others swear a handful of screenshots teaches the machine faster.

Either way, the machine has the same needs as your sales team, only more literally. It cannot infer a hex code from a mood. It does not understand “breathing room”.

It follows explicit values, labelled examples and stated reasons. Write guidelines a careful robot could follow, and a busy human will follow them too.

Then keep them alive. Give the guidelines an owner with a name, not a department, and a short change log so people know what moved. Review them at least once a year, and every time you launch something the rules did not foresee. Add a feedback link, and treat each “how do I…?” question as a missing page.

Finally, do the most radical thing of all. Use them yourself, in public, every day. Nothing persuades an organisation that guidelines matter quite like watching the brand team follow them.

Questions from the back row

How long should brand guidelines be?
As long as the answers people need and no longer. For most small and mid-sized organisations that means roughly 15 to 30 pages plus templates, with strategy and background kept to an appendix.

What is the difference between brand guidelines and a style guide?
Brand guidelines cover the whole brand: strategy, visual identity, voice and behaviour. A style guide usually covers one part in detail, such as editorial writing rules or a digital design system.

How often should brand guidelines be updated?
Review them at least once a year and whenever the brand meets a new channel, market or product the rules did not anticipate. Record each change so users can see what is current.

If your brand book is gathering dust, we can help you turn it into guidelines people actually use.