The Real User of Your Brand Guidelines Isn’t a Designer

Massimo Vignelli designed the New York City Subway map in 1972.¹ He designed the Unigrid system for the United States National Park Service in 1977.² Both systems were built with one explicit goal: to function without him. The grid, the type, the hierarchy, the rules, all of it documented with a precision that assumed the designer would be absent. Not retired. Not on holiday. Gone. Permanently replaced by people who had never met him and would never ask him a question.

This is not how most visual identity systems are built today.

Most visual identity systems are built to impress a client at a presentation. They are delivered in a folder, signed off, invoiced, and handed over to an organization that has no institutional memory of the decisions that produced them. Six months later, the designer is gone. Twelve months later, the brand is unrecognizable. Nobody knows why the secondary typeface was chosen. Nobody knows what the color ratio means or why it matters.

The brand has not been broken. It has been abandoned. And the design industry built the conditions for that abandonment and called it a deliverable.

Boost Your Skills and Build Brands Faster. Proven Systems for Business Owners, Marketers, and Agencies
→ Our mini-course helps you audit and refine an existing brand in 15 days, just 15 minutes a day.
→ The Ultimate Brand Building System is your step-by-step blueprint to building and scaling powerful brands from scratch.

What Wally Olins understood that most brand designers do not

Wally Olins spent most of his career arguing that brand identity is organizational behavior, not visual style.³ His work at Wolff Olins was built on the premise that a visual identity system only works if the people inside an organization understand why it exists. Not what it looks like. Why it exists.

The distinction matters more than the industry typically acknowledges. In 1978, Wolff Olins rebranded Bovis, the British construction company, with an orange hummingbird mark that had nothing visually to do with construction. The mark was deliberately chosen to be distinctive rather than descriptive. But the work Olins considered more important than the mark was the internal program: the workshops, the documentation, the sustained effort to make every person in the organization understand what the brand was trying to communicate and why. The visual identity was the last thing. The internal alignment was the work.

Typical brand engagement ends with visual identity. Olins argued it should begin there. The logo, the typeface, and the color are the visible surface of something that has to operate at every level of an organization, from the CEO’s investor presentation to the sales coordinator’s LinkedIn post. If the people making those touchpoints do not understand what the brand is trying to do, the visual system becomes decorative. It looks like a brand. It does not function as one.

Most brand guidelines documents are written as if the people reading them already understand this. They do not.

The gap Neumeier described that the industry has been slow to close

Marty Neumeier in The Brand Gap describes the distance between a company’s strategic intent and its customers’ actual experience as the gap.⁴ Every inconsistency, every off-brand decision made by someone who did not understand the system widens it.

What Neumeier does not say, but what anyone who has worked in brand identity knows, is that the gap is often widest inside the organization. In the office. In the shared drive. In the deck, the sales team made without asking anyone.

The brand guidelines document was supposed to prevent this. It has largely struggled to do so, not because the documents are badly designed, but because they are designed for the wrong person. They are designed for a designer to review and approve. They are not designed for a marketing coordinator to use under time pressure on a Thursday afternoon, with no design background, while a generative tool is open in another tab.

Michael Bierut has observed that an identity program is a living thing whose ongoing success depends only in part on what the designer brings to the process. What really makes a difference, he notes, is how the program is used day after day.⁵ This is not carelessness. It is what happens when the logic of a system is held in one person’s head instead of being built into the infrastructure around it.

The gap widens not because people are negligent but because the system was never designed to be used by them.

Brand guidelines are a product. The industry has not always designed them like one.

Here is the idea the profession has not fully reckoned with: a brand guidelines document is not documentation. It is a product. And, like every product that struggles, it often does so because it was designed without understanding the people who actually use it.

The users of a visual identity system are not designers. They are the people who will produce touchpoints after the designer has left. The marketing coordinator. The regional sales manager. The partner agency was hired eighteen months later, with no access to the original brief, no understanding of why certain decisions were made, and a deadline that does not allow for careful deliberation.

If you designed a digital product for those users, you would start with research. You would map their tasks, constraints, and most common failure points. You would prototype the system and watch them use it. You would iterate until the system produced correct outputs reliably, not just when used carefully by someone who understood it, but when used quickly by someone who did not.

This approach is rarely applied to brand guidelines. The document is written by the designer who created the system for an imagined reader who shares the designer’s visual literacy and cares about the brand as the designer does. That reader almost never exists in the real organization. The actual reader is under pressure, making judgment calls the document did not anticipate, reaching for whatever tool is fastest.

The Vignelli Unigrid did not survive because it was beautiful. It survived because it was designed for the people who would use it after Vignelli was gone. Every variable that could introduce inconsistency was either locked or documented with enough specificity that deviation required active effort. That is not thoroughness. That is user-centered thinking applied to a different kind of product.

What a survivable visual identity system actually requires

There is a version of this conversation that stays theoretical. Here is what it looks like in practice.

When building out the identity system for a technology client, the first question after the visual system was approved was not what the guidelines should look like. It was who would use them and what they would need to do without asking anyone. The answer identified three distinct user types: in-house marketing staff who needed to move fast and did not always have time to reference documentation, external agencies who needed to understand the logic of decisions, not just the decisions themselves, and the client’s own leadership team who needed to be able to describe the brand verbally to investors and partners.

A single guidelines document serves none of those people equally well. What served them were three different outputs from the same system: a quick-reference card for everyday decisions, a rationale document explaining why each element existed, and a verbal identity guide for non-visual contexts. The visual system was the same. Its packaging changed depending on who was doing what with it.

This is more work. It takes longer. It costs more. And it is the version of brand guidelines most likely to survive contact with the real organization.

What the industry has been slow to admit

The design industry has spent years making the case for user-centered design. It has been argued, correctly, that products fail when they are built for an imagined user rather than a real one. It has convinced clients, stakeholders, and boardrooms that understanding the person you are designing for is not a luxury but a prerequisite.

And then it has gone home and written brand guidelines for an imagined reader.

This is not a critique of individual designers. Most are working within briefs and budgets that do not account for the time it takes to build a truly survivable system. The gap between what is possible and what gets delivered is often as much a resourcing problem as a thinking problem. The critique is of the professional standard: the industry’s definition of done, the frameworks used to scope brand work, the measures used to evaluate its success. A visual identity system is not finished when the guidelines document is approved. It is finished when the people who will use it can use it correctly without the designer in the room.

Holding that standard consistently would change what brand work costs, what it takes, and how long it lasts.

Practical recommendations

For designers and brand strategists who want to build systems that survive them, these shifts matter.

Identify the real users before writing a single guideline. Not the client who commissioned the work. The people inside the organization who will produce brand touchpoints after you are gone. Map their tasks, their skill levels, and the conditions under which they will be working. Design the guidelines for those people specifically.

Separate rationale from rules. Most guidelines documents tell people what to do. Very few explain why. When someone understands why a decision was made, they can make better judgment calls in situations the guidelines did not anticipate. When they only know what to do, every edge case becomes a failure point.

Build in the decision the guidelines cannot make. Every visual identity system will encounter situations the designer did not predict. Instead of trying to document every scenario, identify the two or three principles that should govern any decision not covered by the guidelines. Write those principles in plain language and put them at the front of the document.

Test the guidelines before you deliver them. Give the document to someone who did not work on the brand and ask them to produce a real touchpoint using only the guidelines. Watch where they hesitate. Watch where they guess. Every moment of uncertainty is a gap in the documentation. Fix it before you invoice.

Define done differently. A visual identity system is not finished at delivery. Build into the scope a six-month check-in to audit how the system is actually being used and what has drifted. That audit is not quality control. It is the most useful brief you will ever receive for the next version of the work.

Vignelli understood this. Olins understood this. The design industry has understood it in theory for decades.

The question is a simpler one than it appears. Do you want to make something beautiful that impresses a client at a presentation and becomes unrecognizable in the hands of the people who inherit it? Or do you want to make something that still works correctly two years after you cashed the invoice?

Both are possible. Only one of them is finished.