Brand guidelines or brand system: why a PDF is no longer enough

Almost every company has a file called something like “Brand_Guidelines_V3_final.pdf”. It is polished, thorough and rarely opened. That isn’t negligence: the questions people ask while making an asset are almost never the ones it answers.

The problem isn’t the guidelines. It’s the format. To see why, you have to ask who the document was invented for.

What are brand guidelines, and who were they written for?

Brand guidelines were born when a brand produced a finite number of things: letterhead, business cards, a brochure, a sign, a few press ads. They were made by designers and printers who knew how to read a specification. The guidelines were a hand-over document between professionals, and a fixed document was the right tool: you opened it at the start of a job, applied it, and checked it on the proof.

Classic guidelines still contain much the same today:

• the logo, its versions and its clear space;
• the colour palette, with its print and screen equivalents;
• the typefaces and their weights;
• a few layout principles;
• examples of use and a list of don’ts.

None of this is useless, and none of it disappears in a brand system. The problem lies elsewhere: the reader has changed, and the document hasn’t.

Why is a PDF no longer enough?

Three things have changed, and none of them is about how the brand is drawn.

Volume. A brand no longer produces a few dozen assets a year but a continuous stream: posts, stories, vertical videos, banners, sales decks, web pages, emails, interfaces. Many of these formats didn’t exist when the guidelines were written.

People. The reader is no longer a designer. It’s whoever runs social media in a template tool, the developer building a page, the salesperson reworking a deck the night before a meeting, the editor finishing a video, and increasingly an automated tool. None of them was trained to read a graphic specification.

Tools. Each of these people works in different software, and none of that software reads a PDF. A colour given as a hex code has to be copied by hand into a presentation theme, a stylesheet, a design library, an editing preset. Every time it is copied, someone interprets a little.

So between the document and the tool there is a translation step that nobody is responsible for. The guidelines stay correct, the assets drift anyway, and everyone can honestly say they followed the rules.

What can brand guidelines not say?

Even read carefully, guidelines have blind spots that come from their form: they show still images, while much of what makes a brand recognisable doesn’t stand still.

Behaviour. Guidelines don’t say how an element appears, how fast it moves, or what it becomes when the screen gets narrower. Writing “dynamic, fluid transitions” achieves nothing: everyone fills those words with their software’s default settings.

States. A button doesn’t have one look, it has five: resting, hovered, pressed, disabled, in error. An interface has to exist in light and dark mode. These aren’t build details, they are brand decisions. If the guidelines don’t make them, the developer makes them instead.

Real content. The examples in guidelines are set with headlines of just the right length and photos chosen to look good. Reality brings endless product names, images sent by a partner, translations that stretch every line. A sample page doesn’t say what should give way when the content doesn’t fit.

These blind spots have one thing in common: they only show up at the moment of production. Yet guidelines are written when you know the least, on the day the identity project ends, before a single real asset has been made with them. Guidelines have a date. A system has a version number.

What does a brand system add?

A brand system keeps everything the guidelines contain but changes the form in which the rules are delivered. Instead of being described in a document, they are built into the places where people work.

• Components rather than examples. A header, a card, a caption, a block of figures: elements built once, properly, then reused. Nobody has to recompose; they assemble.
• Templates in the team’s real tools. The presentation theme, social media templates, sales documents, prepared in the software the teams actually use, not the studio’s.
• Motion references. Durations, curves, ways of entering and leaving, delivered as files and presets, not adjectives.
• Code. Colours, type sizes, spacing and corner radii become shared variables, often called design tokens. The website, the design library and the templates all draw from the same source.

That last point changes more than it seems. With guidelines, changing a colour means publishing version 4 of the PDF and hoping the existing files will follow, which they never do. With a system, the value changes in one place and spreads. Guidelines freeze the brand at the moment they are written. A system lets it evolve without leaving contradictory versions of itself behind.

Brand guidelines, style guide, design system: what’s the difference?

The terms overlap, and the confusion isn’t harmless.

Brand guidelines, sometimes called a style guide, are the document that sets the visual rules, often extended to tone of voice and sometimes positioning. A design system comes from another world, that of product teams: a library of interface components, with their code and documentation, built to make screens. What we call a brand system is where the two meet: the brand’s rules, delivered in a usable form, across every medium and not only the interface.

For a long time these worlds ignored each other, guidelines on the marketing side, the design system on the product side. In many companies there are two competing definitions of the same brand: the PDF’s and the code’s. When they diverge, the code almost always wins, because it is what customers see every day.

You can go further: today, the most complete and precise description of a brand is often its website. Its stylesheet holds the exact sizes, the spacing, the states, the behaviours, everything the PDF leaves out. That is why we don’t treat web design as a step that comes after the identity, but as one of the places where it gets written.

What does rolling out a system look like on a real project?

Trace designs sensors that measure athletes’ performance. The identity starts from the idea of a trace, the path an athlete leaves behind. The symbol, the typography and a signal green express both the precision of the data and the energy of movement.

On paper, this identity would fit on three pages. In practice, it has to stretch from the product to sales materials, from the website to campaign visuals, assets that share neither format, nor authors, nor tools. A PDF could have fixed the green and the typeface. It couldn’t have said how a trace is drawn from real data, or how an animated format stays recognisable when the team produces it alone. That is why part of the system we delivered isn’t a document at all: visuals generated by code from the sensors’ data, and animated social templates with the rules already applied.

GUD, a platform promoting blockchain in the video game industry, goes further. The heart of the identity is a behaviour: the logo is drawn in pixels, the pixels become cubes, and the cubes evolve into entities that change with the user’s interactions. No page of guidelines can hold that. A screenshot would show one state, never the rule. This identity only fully exists in the interface, which is why the studio designed the web interfaces, icons and ads in the same movement.

How do you know whether you need guidelines or a system?

Not every brand needs a system, and selling one to everyone would be dishonest. Company size isn’t the right test either. A few questions are better ones:

• How many people produce assets for the brand, and how many of them are designers?
• In how many different pieces of software is the brand made?
• Does the brand live mostly on screen, in motion, in video?
• Do you have a website or digital product that changes regularly?
• How many outside suppliers work on your assets?
• If you changed a colour tomorrow, how many files would need reworking?

If one or two people produce most of the work, mostly in print, and the brand rarely changes, good brand guidelines are enough. They should then be short: fifteen pages people read beat eighty pages people admire.

If several non-designers produce in several tools, if video and the website are central, or if the last question makes you smile, you need a system. In between, there is a sensible route: tightened guidelines with the three or four templates that cover most uses, then expanded as real needs appear.

How do you move from guidelines to a system without redoing your identity?

Most of the time there is nothing to redraw: the identity is fine, it’s the way it is delivered that isn’t. The work follows a fairly steady order.

First, look at what has actually been produced over recent months, not what the guidelines imagined: where the brand is made, by whom, in which tools.

Next, spot the decisions people keep making on their own, such as headline size on a story or where the logo goes on a busy photo. Every repeated decision is a missing component or variable.

Then build those rules into the places where people work, starting with the website and the team’s most-used tool, where the drift is strongest.

Finally, shrink the PDF. It doesn’t disappear: it becomes the system’s index, short and versioned, explaining the intentions and pointing to the sources.

The takeaway

Brand guidelines say what the brand should look like. A brand system makes sure it does, even when nobody from the studio is in the room. The difference isn’t in the drawing, but in where the rules live.

That is how we approach every brand identity project at Initial: the mark, the system and the tools that make it usable, website included. For brands that want the system kept up and extended over time, the studio also offers monthly art direction. If your guidelines are asleep in a shared folder while your assets drift, let’s talk.