Why does the identity system still sit in the cupboard?

Many Vietnamese businesses have spent significant budgets to create a comprehensive brand identity: a clear logo, consistent color palette, carefully chosen fonts, and guidelines spanning dozens of pages. Then six months later, each department uses a different color, each employee exports files in their own way, and that identity system lies dormant in a hard drive folder that no one opens. The issue is not poor design. The issue is a lack of an operating system.

Why is the identity system not being used?

Most identity systems are delivered as a complete product: beautiful, neatly packaged, with user instructions. However, an organization does not operate like an end user reading a manual and doing it correctly. Organizations operate through habits, deadline pressures, and established ways of working. If the identity system is not integrated into those flows, it will be overlooked, not because anyone intends to, but because no one has a mechanism to use it correctly.

This is not an issue specific to one company. It is a widespread condition that can be measured.

The gap between "having" and "being usable" is the part that is not designed: the operating system.

Static guidelines self-eroding

The delivered identity system often comes with a PDF document or Figma file. This is a good starting point, but it is not enough to maintain consistency over time. As the organization hires more people, opens new channels, and launches new products, that static document begins to drift. New employees do not know where that document is located. Marketers adjust colors because they "look better on screen." External agencies use old logos because that is the file they received from the previous collaboration.

Wally Olins, one of the pioneers of modern branding theory, defines a brand through four vectors: product, environment, communication, and behavior. An identity system only touches on the communication aspect. The other three parts need to be actively and continuously managed, with someone responsible.

Consistency is not a design problem. It is an organizational problem.

Marty Neumeier, The Brand Gap

What happens when identity is inconsistent

Inconsistency not only makes the identity system look chaotic. It undermines something more important: the ability to build recognition in the minds of customers. According to research from the Ehrenberg-Bass Institute (University of Adelaide, specializing in consumer behavior and branding), distinctive identity assets only create "mental availability" (presence in the buyer's mind at the moment they make a decision) when they are consistently repeated across enough touchpoints and over sufficient time. Continuous changes, even small ones, disrupt that accumulation process.

The root cause: identity can be designed but not organized.

The real problem does not lie in the quality of the design. It lies in how the identity system is delivered and integrated into the organization. Most branding processes end at the point of file delivery. From that point on, the organization has to fend for itself. No one clearly defines: who is allowed to make edits, what the approval flow for a new asset looks like, where identity assets are stored and accessed from, and what happens when a department needs to use the identity.

Without a structure to answer those questions, each person will come up with their own answers. New employees will search for the logo on Google. Marketing will adjust colors to fit the existing template. Sales will design their own deck according to personal taste. The result is a fragmented identity system, not because anyone intends to break it, but because there is no system to keep it intact.

The brand operating system is the missing piece.

The Brand Operating System does not replace the brand identity. It is the organizational layer that wraps around the identity, transforming design assets into something the organization can use daily without needing to start from scratch each time.

The operating system consists of at least three layers. The first layer is where assets are stored and distributed: who has access to what, which version is the official one, how to onboard new people and external agencies. The second layer is governance: who approves the creation of new assets, what are the boundaries for adaptation, and what are the boundaries that must not be crossed. The third layer is the update loop: when the identity needs to adjust according to business realities, how that change spreads through the system, not through mass emails but through a pre-designed structure.

McKinsey, in its study on the business value of design (2018, over 300 companies over 5 years), found that organizations that integrate design across departments rather than keeping it in a separate design center have significantly stronger financial correlations compared to those that do not. In other words: effective identity operation is not because the design is better, but because it is organized better.

Signs that the organization needs an operating system

Not every organization needs to build a complex operating system immediately. However, there are signs that the identity is stuck due to a lack of operational structure, not because of poor design quality.

• Each department has a different version of the logo or color palette being used simultaneously.
• New employees don't know where to find the identity assets and download them from random sources.
• Agencies or outsourced partners often use the identity incorrectly without anyone catching it in time.
• Each time a new asset is needed, the approval process is unclear and unnecessarily prolonged.
• Guidelines exist, but no one reads them, or they read them and still do not know how to apply them to specific situations.

If more than two of those describe the current situation, the issue lies not with the identity but with the organizational layer beneath it. Redesigning without addressing that layer will yield similar results after 6 to 12 months.