Brands lose consistency after a software change usually because identity assets are scattered across individual tools instead of kept in one neutral place. The solution is not to pick better software, but to build a brand system that is independent of any platform. That system sets the principles, and the tools are only where they are put into practice.
In this article · 7 sections
Sinh Vũ has observed many businesses that have just completed a migration of their internal management software, from an old system to a newer, more modern tool.
A few weeks later, someone notices that the logo on the sales materials differs from the logo on social media. The colors in the slide deck are off compared with the website. No one sabotaged anything.
It's just that no one knows where to get it.
The most common reason: brand assets live inside the software
Many businesses store brand assets directly inside the tools they use: the logo in the design software's library, the color palette in the presentation tool's settings, fonts in the project management software's templates.
When a company moves to a new system, those assets don't move on their own. The new team uses whatever version they can find, often an old one downloaded from email or sitting on a personal laptop.
The result is not a lost brand. It is a brand that exists in several versions at once, with no one knowing which one is official.
Software is where the work happens, not where the rules are kept
This is the distinction to make clear: software is a tool for execution. It handles files, permissions, and edit history.
But it can't hold onto the reason why this logo is right and that one is wrong.
Brand principles, official colors, permitted typefaces, tone of voice, how to place the logo on dark or light backgrounds: all of this is knowledge.
Knowledge needs to be written down, not embedded in the settings of one specific piece of software.
A brand is not a logo. A brand is how customers feel about a product or a business.
Marty Neumeier, The Brand Gap
When brand knowledge lives only in the heads of a few people, or is stuck in the settings of one tool, a business depends on the two things that are easiest to lose: human memory and software continuity.
A brand system needs to be independent of the platform
The principle for designing a durable identity system is this: place assets and rules in a neutral layer, outside any internal management software.
That layer has three parts:
- Source assets (logos in original format, color palettes with exact codes, approved font files): store them where everyone in the organization can access them, not tied to the permissions of a specific tool.
- The guidelines document spells out how to use things: who uses them, where, which version is the latest, and who is allowed to edit.
- Update process: when something changes, who announces it, who updates it, and who confirms it's done.
These three parts don't need expensive software. But without them, no software can make up for it.
Design tokens: change one place, and it spreads across the whole system
For businesses with digital products or digital interfaces, there is a more technical approach: design tokens (named design values stored in one central place).
Instead of writing the primary color as #1A2B3C in ten different places, the business gives it a name, for example "primary-color", and uses that name everywhere.
When you need to change a color, you edit one place and the whole system updates with it.
This is how Google (Material Design 3) and Salesforce (Lightning Design System) build identity systems for their products. The principles stay the same when they upgrade or replace internal tools.
Before switching software: three questions to answer
When a business is about to change an internal system, whether it's project management software, a design platform, or a document system, Sinh Vũ usually asks three questions:
- Where are your brand assets right now, and who knows that location?
- If that person leaves tomorrow, can the rest of the team still find the right files?
- Once the new system is in use, who will put the brand assets in the right place, in the right version?
These three questions aren't on a typical software migration checklist. But if you can't answer them, the identity will start to drift right after the new system goes live.
Consistency is not about aesthetics
A common view is that brand consistency is a matter for designers and communications people. In reality, that is not the case.
Researcher Jenni Romaniuk of the Ehrenberg-Bass Institute points out that distinctive assets only build up in customers' memory when they are repeated consistently over time.
Repetition is how memory works, not an aesthetic choice.
Every time the identity appears off, even if it's just a color a few shades wrong or an old logo left on a document, the signal gets distorted. With enough distortion, customers stop recognizing you.
And according to a Lucidpress / Demand Metric survey, businesses that keep a consistent identity may see higher revenue than those that don't, based on self-reported surveys from participating businesses.
The size of the gap varies by industry and scale, but the direction is clear.
What to do today
If your business hasn't checked its brand assets since the most recent software migration, here are three things you can do right away:
- Gather every logo file, color palette, and typeface actually in use, from every department. Compare them with the originals to see how far they have drifted.
- Create a shared folder that isn't tied to anyone's personal account, and keep the official assets there.
- Write a short one-page guide: which logo to use when, which color has which code, which typeface is official. One A4 page is enough to get started.
None of this needs new software. It only needs a decision to do it.
References
Marty Neumeier, The Brand Gap. Marq / Demand Metric, Brand Consistency Report, 2021. Adobe, Digital Content Survey. Material Design 3 (Google), Salesforce Lightning Design System.