Tiered BOS: globally consistent, locally relevant

When a business opens its first branch in a new market, the first question is often about products, personnel, and logistics. Questions about branding usually come later, often in the form of: "Can they adjust a bit to fit in over there?" This question sounds practical. But it is precisely the starting point of drift.

Why allowing branches to self-adjust is a systemic risk

When there are no clear boundaries, "self-adjustment" does not mean controlled refinement. It means each person makes decisions based on personal judgment. The local marketing team changes colors because they feel the original color does not suit local tastes. The outsourced media company uses a different font because they cannot find the original file. The branch manager rewrites the tagline to sound more relatable to local customers.

Marty Neumeier calls this phenomenon "internal drift." He argues that the biggest enemy of a brand is the thousands of small decisions made by people who are not equipped with brand logic. Each individual decision may seem reasonable. Cumulatively, they break the identity.

The issue is not a lack of identity. The issue is the absence of a structure to operate that identity when the organization is dispersed across many points.

The two layers in BOS stratification

The tiered Brand Operating System (BOS) divides the entire brand system into two clearly defined areas.

The first layer is the global core, which refers to immutable elements. This is a collection of factors that create the core identity and must not change regardless of the market. Typically, the global core includes: logo and protection area, primary color palette, foundational typography, brand voice, and basic visual principles. These are the elements that Jenni Romaniuk refers to as distinctive assets: they hold value because they are repeated long enough to embed in customers' memories. Breaking them is not adaptation, but rather self-erasure of the brand value built over time.

The second layer is local adaptation, which refers to local adjustments. These are elements that are allowed to change within a predefined framework to align with local culture, language, and preferences. This layer typically includes: language and message expression, illustrative images and photography style, secondary color tones expanded from the core palette, and content organization on each local channel.

Consistency does not mean uniformity. It means that every variation recognizes each other as part of the same family.

The principles of the tiered BOS, based on Kapferer's framework for brand identity

Boundaries are intentionally designed, not default.

The point many businesses overlook is that the boundary between the two tiers does not naturally appear. It must be designed. And that design requires brand judgment, not just a list.

For example, the gold color is a core identity asset of the brand, belonging to the global core. But when that brand enters a market with negative cultural associations with the color yellow, can that color be adjusted? The answer is not an absolute "yes" or "no." The answer is that someone with authority must make that decision. This person needs to understand both sides deeply. That decision must be documented in the system.

This is why the tiered BOS is not just an Excel sheet with two columns of "allowed / not allowed." It is a governance structure: who can decide what, at which layer, and through what process.

Design token: a technical bridge between the two layers

At the practical implementation level, design tokens are technical tools that enable layered operations. Tokens are variables that contain design values, such as exact colors, font sizes, and spacing, stored in a single source and spread across all digital products.

In the layered structure, global core tokens are immutable values: brand color, foundational typography, basic ratios. Local tokens are values that can be overridden within the allowed area. For example, the background color token of a local page may point to a variant in the approved secondary color palette. Change it once at the source, and the change spreads throughout the system. No team needs to guess the value of the color.

Salesforce Lightning and Google Material 3 both operate under this architecture at the scale of hundreds of products. The principles remain unchanged even at a much smaller scale.

How to read signals when the structure is breaking down

Before the system completely breaks down, there are often early signs that you can recognize.

• Each branch has a different PowerPoint presentation, and no one is sure which one is the standard.
• When customers encounter the brand in two markets, they are unsure if it is the same company.
• The local team often asks, "Is this allowed?" because there are no clear answers in the documentation.
• Every time there is a new campaign, each place does it in its own way, and no one collects common results.

These signals are not a design team issue. They are structural issues. And a tiered structure is the structural answer, not just another approval round.

Where to start when there is nothing

Not every business needs to build an entire token and governance system from scratch. However, every expanding business must start with one thing: sitting down and listing what cannot be changed, regardless of location.

That list, even if just one page, is the first global core. From there, every local adjustment has a point of reference. Every team knows they are adjusting within the allowed range, not making guesses.

Sinh Vũ refers to this process as the "BOS seed": a minimal structure sufficient for operation and expansion, not necessarily a complete system from the start. As the organization grows, the system expands without needing to be rebuilt from scratch.