The identity system that nobody reads

Brand guidelines are one of the most reliably useless deliverables in the industry. Not because they’re badly made — often they’re beautifully made — but because they’re solving the wrong problem. The studio thinks it’s creating a system. The client thinks it’s receiving a manual. Both are wrong about what it takes for a brand to stay coherent over time.

The studio thinks it’s creating a system. The client thinks it’s receiving a manual.

Why guidelines fail

The fundamental problem with most brand guidelines is that they’re written for a hypothetical person who has read everything, understands the rationale, and has time to consult a document before making every design decision. This person does not exist. The people who actually use brand assets are in a hurry, working in tools that don’t match the guidelines, and making judgement calls the document never anticipated.

Guidelines that don’t account for this aren’t guidelines. They’re aspirations. And aspirations that live in a PDF nobody opens are indistinguishable from not having guidelines at all.

The failure compounds at handoff. The studio presents the guidelines in a meeting, walks through the logic, answers questions. Then the PDF gets uploaded to a shared drive. Three months later, the marketing team is using the wrong font weight because nobody remembered which one was primary, and the new hire on the social team is working from a colour palette they found in an old Instagram post.

What actually makes a system stick

The identity systems that hold up over time have a few things in common, and none of them are about the quality of the PDF.

First, they’re built with constraints, not options. A brand that offers three headline typefaces and two colour palettes and four approved layouts will be used inconsistently, because every decision becomes a choice and most people making those choices haven’t internalised the logic behind them. The systems that work give people one answer, not a range of acceptable ones.

Second, they’re embedded, not delivered. The studios that produce the most durable identity work aren’t handing over a document at the end of a project — they’re building the brand directly into the tools the client team uses every day. Figma libraries, template files, pre-built Framer components. The brand isn’t something you refer to; it’s something you’re already using.

Third, they account for drift. Every identity drifts over time. The question isn’t whether it will, but whether you’ve built anything that makes the drift visible and correctable. An annual review. A single person who owns it. A set of canonical examples that get updated rather than archived. The studios that get this right treat the handoff as the beginning of a maintenance relationship, not the end of a project.

The question to ask at the start

Before the first brand presentation, before the moodboard, before any of it — ask the client who will be responsible for the brand in two years’ time. Not who’s in the room now. Who’ll own it when the agency relationship ends and the marketing team turns over and the CEO gets replaced.

If they can’t answer that question, the guidelines won’t help them. What they need isn’t a more thorough document. They need a simpler system, built for people who didn’t choose it and won’t read the rationale behind it. That’s a harder thing to design. It’s also the only thing worth designing.