The Brand Guide vs. The Building

THE PDF

Someone sends you a brand guidelines PDF. Sixty-two pages. Pantone swatches, typeface specimens, clear space rules, a whole section on "tone of voice" that has nothing to do with anything you're about to build. Page 14, little box with a ruler icon: "Primary typeface: Gotham Light. Use at all times. Do not substitute."

Honestly that's a perfectly reasonable instruction if you're designing a website or a brochure. But Gotham Light on a 4-inch deep channel letter readable at 200 feet is a different animal entirely, and there's no reason the person who wrote that guide would know that. Why would they? They're not sign people. They're brand people, and they're good at what they do. The problem isn't the guide. The problem is that nobody's built a reliable bridge between what the guide says and what the building needs.

That's kind of what this whole post is about... Not "brand guides are wrong." More like "brand guides are incomplete, and that gap is where our job actually starts."

THE GAP

Brand guidelines are written by graphic designers and brand strategists working in controlled environments. Consistent lighting, predictable screens, precise color reproduction. That's their world, and they're excellent at it. Our world is sun, rain, distance, speed, building materials, code restrictions, and time. Those two worlds don't automatically translate, and honestly, nobody should expect them to. It's two completely different disciplines that happen to share a logo.

So when the guide says "Gotham at all times," it's not a bad spec. It's just an incomplete one. Gotham Light at 18 inches? Rough at distance. Strokes are thin enough to wash out in direct sun and bleed into the background at night. Gotham Bold? Much better. Gotham Ultra? Now the counters start closing up at distance, especially on 'e', 'a', and 's', and word shapes go muddy. The guide can't reasonably cover all of that. It wasn't written for this medium. That's not a failure of the guide. That's just the reality of translation.

Same thing with scripts and serifs. A delicate modern serif can be stunning on a business card and genuinely unbuildable as a channel letter under 36 inches. Thin serifs either can't be made at the needed scale or they create fragile returns that won't hold up structurally. Not the brand team's fault for choosing a beautiful typeface. Just a physical constraint that needs to be navigated.

Letter spacing too. Brand guides often spec tight tracking because it looks clean in print. Totally valid in that context. On dimensional letters it gets tricky. Channel letters need physical separation for mounting hardware, electrical connections, and enough visual breathing room that letterforms don't merge at distance. I've had files come through where the tracking was so tight that "LOUNGE" read as "LOUAGE" from the parking lot because the N ate the G. Nobody's fault, really. Just two different sets of rules colliding.

GLARE

This one bites everyone at least once, not because anyone made a mistake, but because it's genuinely counterintuitive if you haven't dealt with it.

PMS 186 Red. Deep, punchy, looks fantastic on print collateral. As a high-gloss finish on a south-facing panel? Between 11 AM and 3 PM that sign is just a white rectangle of reflected sunlight. The brand's signature color, gone, during peak traffic. There's no way to know that from looking at a swatch book.

Fix is usually satin or matte finish. Diffuses the reflection, holds color across viewing angles. But if the guide specs gloss, there's a good reason for it. It probably looks amazing on packaging, on the website, in the showroom. The disconnect is just that glossy surfaces behave completely differently outdoors at scale. Once you explain it and show the comparison, most people get it immediately. It's not a hard sell. It's just information that hasn't been shared yet.

I could go on a whole tangent about how red and orange acrylic faces absorb so much LED light they look dim at night next to white letters on the same sign. Or how certain red pigments fade under UV and drift toward a washed-out brick by year three. Or how high-gloss finishes yellow over time. Point is, the brand guide gives you a color target. The physical world introduces variables the guide was never designed to address. Our job is to close that gap, not complain about it.

CONTEXT

Brand guides show logos on white backgrounds or clean renderings with neutral buildings and empty streets, which makes sense for demonstrating the visual system. But no sign lives in that vacuum. Real signs sit next to other tenants, against building materials with their own color and texture, behind landscaping that'll double in height in five years, in code environments with their own restrictions. The brand team can't anticipate all of that, nor should they have to, that's literally what we're here for.

We had a project years back where the guidelines specified a horizontal logo lockup with generous clear space on all sides. Perfect on paper. The building's sign band was tall and narrow, maybe 3 by 8 feet, between two columns. Horizontal lockup scaled to fit the width disappeared. Scaled to fill the height, it overshot both edges... Obviously neither version worked. We mocked a stacked version, icon over wordmark, that wasn't in the guide. We showed the client on-site photos with both options overlaid so they could see the difference themselves, and got approved in about a week. No drama. The result actually did what the brand needed it to do, while the horizontal version would've been compliant and invisible. Sometimes the best way to serve the brand is to adapt the playbook.

BRIDGING IT

The process, when it goes well, is pretty straightforward. Study the guide to understand intent (not just the specs, but the why behind them). What's the personality of this typeface? What's the hierarchy between icon and wordmark? What feeling is the color palette going for? The better you understand the intent, the smarter your adaptations are when the specs hit a physical wall.

Survey the site. Every approach angle, different times of day. Building materials, adjacent signage, code restrictions. I've shown up to installs and found problems that a single site visit would've caught. Shadows across the sign band, sightlines blocked by a neighbor's awning, a fascia channel too shallow for the returns. None of these are catastrophic if you catch them early, but all of them are expensive if you don't.

Then build the bridge. I keep a spreadsheet (because of course I do) of the most common translation issues and their fixes. Thin weights, bump up or add letter height. Tight tracking, open to optical spacing. Horizontal lockup on narrow fascia, go stacked. Gloss panel in direct sun, switch to satin. About forty items now, and it grows every time something new comes up.

The best tool we've found for getting alignment with brand teams: side-by-side mockups. Render the sign exactly per the guide in actual site conditions, right next to the adapted version. "Here's what the spec produces on this building, and here's what we're recommending instead." Most of the time, the visual does all the talking. People aren't unreasonable, they just need help visualizing things sometimes.

THE BRAND IS BIGGER

Took me a long time to really internalize this, but a brand isn't its guidelines. Guidelines are a snapshot. A description of the visual system at a moment in time. The brand itself is the recognition, the trust, and the feeling when someone sees your name on a building. Sometimes the best (or only) way to protect that feeling is to deviate from the document.

The best working relationships we've had with brand teams started when we stopped treating the guide as a rulebook and started treating it as a shared starting point. They know the brand better than we ever will, and we know the physical environment better than they ever will. When you put those together honestly the work gets better for everyone involved.

That's kind of the whole gig, right? Not fighting the brand guide, not ignoring it... Translating it. Taking something built for one medium and making it work in another, and doing it with enough care that both sides of the equation feel respected.