SolisReach
← Journal
Brand & UI/UX6 min read

Brand guidelines that are actually usable, not just a PDF nobody opens

Written by the SolisReach team

We inherited a client's existing brand guidelines last month, a beautifully designed forty-page PDF full of mood boards and color theory, and within ten minutes of trying to actually use it for a real design decision, we understood exactly why nobody on the client's team had opened it in over a year. It looked impressive. It didn't answer a single practical question we needed answered.

That's the pattern we see constantly: brand guidelines built to win approval in a single polished presentation, not to be used by an actual team making dozens of small decisions a week. The two goals produce very different documents, and most agencies optimize for the wrong one because it's the one the client sees before signing off.

What a usable guide actually needs to answer

Not "what does our brand feel like," but "what button color do I use here, what happens when this headline wraps to two lines, is this specific shade of blue our primary or our secondary." A usable guide is a reference document for people making fast decisions under deadline pressure, not an art piece meant to be read once from cover to cover.

We test every guideline we produce against a real scenario before calling it done: hand it to someone on the client's team who wasn't involved in creating it, give them an actual task, like building a simple flyer or a social post, and watch whether the guide actually answers their questions as they go, without needing to ask us directly.

Why mood boards alone don't survive contact with real work

A mood board communicates a feeling effectively to the people in the room when it's presented. It communicates almost nothing to a freelance designer working from it eight months later with no context, which is the situation most brand guidelines actually need to serve. Feeling is important, but it has to get translated into specific, checkable rules to be useful later.

We still build mood boards, because they're genuinely useful for aligning stakeholders early in a project. We just don't stop there. Every mood board we produce gets translated into specific hex codes, specific type scales, and specific usage rules before the guideline is considered finished, so the feeling survives past the room it was first agreed on in.

The sections that actually get referenced

Color usage with exact values and explicit pairing rules, not just a palette. Typography with a defined scale for headings and body text across contexts, not just "use this font." Logo clear space and minimum sizing, spelled out in pixels or a defined unit, not left to judgment. Do-and-don't examples showing actual mistakes we've seen made with similar brands, because a wrong example teaches faster than a description of a rule ever does.

We've watched teams reference these four sections constantly and almost never touch the brand story or the tone-of-voice essay that took the longest to write. That's not a criticism of the writing. It's a fact about what a guideline is actually for once the launch excitement fades and the daily grind of production work sets in.

Building it as a living reference, not a static file

A PDF gets outdated the first time a color shifts slightly or a new product line needs its own sub-brand treatment, and updating a forty-page PDF is enough friction that most teams just stop bothering, leaving an increasingly wrong document as the only reference anyone has. We push clients toward a simple, linkable web page instead wherever possible, something a designer can bookmark and actually check before starting new work.

A living reference also lets us track what's actually being used, informally, just by noticing which sections questions keep coming back to. That feedback loop has quietly improved every guideline we've built since we started paying attention to it, because it tells us where the document is still unclear even after a team has been using it for months.

A PDF gets outdated the first time a color shifts slightly or a new product line needs its own sub-brand treatment, and updating a forty-page PDF is enough friction that most teams just stop bothering, leaving an increasingly wrong document as the only reference anyone has.

What we cut from the traditional brand guide

Long philosophical brand narratives that read beautifully once and get referenced never. Overly rigid rules that don't account for real-world edge cases, like what actually happens when a partner logo has to sit next to yours on a co-branded page nobody planned for. Anything written primarily to sound impressive to the person approving the document rather than useful to the person applying it later.

Cutting these isn't about making the guide less thorough. It's about spending the effort on the parts that get used a hundred times instead of the parts that get read once, in the meeting where the guide is first presented, and then never opened again.

How we roll this out with a new client

We deliver the guide in a working session, not an email attachment, and we walk through three or four realistic scenarios live: designing a social ad, laying out a one-page flyer, adapting the logo for a small favicon. Watching someone actually try to use the rules in real time surfaces gaps faster than any amount of internal review ever does.

Feedback from that session goes straight back into the document before we call it finished. This adds a day to the timeline. It also means the guide that finally ships has already survived contact with real work, instead of discovering its gaps for the first time months later on a project we're not even involved in anymore.

A brand guide's real test isn't how it looks in the presentation where it gets approved. It's whether a designer six months from now, working under deadline pressure, with no memory of that meeting, can open it and get a clear, confident answer.

Most brand guides fail that test quietly, because nobody ever actually checks. We check, on purpose, before calling any guideline done, and it's changed how we scope every brand project since.

It's also changed what clients expect from us upfront. More than a few have specifically asked, after seeing this process once, for the working session to happen earlier in future projects, not just at the handoff, because it surfaces real decisions faster than a document review ever could on its own.

We keep a short internal log of every question a client's team asks us after handoff, and we treat repeated questions as a signal that the guide itself is missing something, not that the team failed to read it closely enough. That habit alone has quietly improved every guideline we've shipped since we started it.

Start a project

Want this applied to your site?

We run a Core Web Vitals and SEO audit before quoting any performance marketing engagement, and we're happy to share what we'd find on yours.