Your brand is an archaeological artifact
Why brand and design systems evolved apart - and why AI makes a fix even more urgent.
Where does a brand team’s work live?
Brand guidelines, brand standards. Decks sent to agencies. A Confluence page. Almost certainly a PDF or two.
Where does a design system team’s work live?
The component library. Tokens. The design system website. A Storybook instance. An npm package.
Two expressions of what a company is. Consistent and coherent in themselves. Often almost zero shared conversation.
It’s a strange structural failure in modern product organizations. I’m surprised it’s not talked about more often.
Brand sits in the marketing organization. Design systems sit somewhere in product, design, engineering organizations. They share a fundamental subject matter, but operate in organizational separation.
The results are predictable.
Design systems encode visual consistency without brand meaning. Brand guidelines describe how a company should feel...and nobody in product has read them.
The digital expression of the brand gets determined by whoever’s in the room.
Whose job actually is it to ensure that a product expresses the brand?
In most enterprises I’ve seen, the honest answer is nobody. Brand says what a company should feel like. Design systems say what the products should look like. And there’s a gap between the two where digital brand value can quietly disappear.
It’s an archaeological artifact.
Brand as an organizational function predates digital product as a discipline, by decades. And those structures have calcified. Brand in marketing, product in...product. And that’s held even after the product has become the primary brand experience for most companies.
Your brand is not the ad. Not the packaging. It’s the thing you use every day. But the org charts are already set.
I’ve seen the alternative. I built one of the few examples I see of how it can exist at scale. IBM Carbon doesn’t derive from component logic. It derives from a broader IBM design philosophy - that predates the system, runs deeper than any product services. But which defined a design language with awareness of, and collaboration with, the digital design system team.
The result is that I see Carbon in an IBM television ad or on a billboard. Or, more accurately, IBM products that use Carbon represent a coherent design language. Something that exists across mediums because it’s grounded in something universal.
That’s not the norm.
Brand guidelines evolved from print and campaign logic. Design systems evolved from digital product delivery logic. They haven’t evolved toward each other. Customers are the ones who absorb the incoherence.
This might have been manageable when product moved relatively slowly. Misalignment can be addressed (...or ignored!). Brand drift was visible enough for someone to notice before it compounds too much.
The faster delivery accelerates, the more difficult it is to manage. And we’re at the point of AI driving acceleration so that delivery might become almost incomprehensibly fast.
The models that let us ship in days instead of months will be generating interfaces, copy, and variations at a scale no brand team has ever accounted for. AI will drift because it has no context for what that brand is.
Design systems that carry genuine brand meaning - not just coherent visual rules, but the reasoning behind them - will compound in the right direction. Design systems that are sophisticated token libraries and nothing more will produce brand-incoherent experiences. Faster, and at greater volume, than before.
The AI case makes the structural fix urgent. But it was already necessary.
The product has been the brand for years.
The org chart just hasn’t caught up.
Further reading:
Weidemann, V (PhD). The Unspoken Tension: Product vs. Marketing — Why We Still Don’t Speak the Same Language. Medium, May 2025.
Why do product and brand need to be developed together? GreyGekko, Apr 2026.
Article photo by naeim jafari on Unsplash.