When your logo appears on partner apps, websites, and stores, there are no employees present to correct mistakes if they occur.
When the brand appears on a partner's channel, the identity system must operate correctly without supervision. This is only feasible if design tokens and brand rules are clearly established from the beginning, before handing over to any partners.
When the brand appears on a partner's app, website, or store, no one is there to correct it if the color is wrong, the logo is distorted, or the font is replaced with something convenient. The identity system must operate on its own at that moment, or it will not operate at all.
This is not an issue for large brands. Any business distributing through external channels, partnering with logistics providers, or placing products on e-commerce platforms is putting its identity in the hands of others. The question is not whether it should be done, but whether you are adequately prepared to ensure that it does not cause harm.
Partners do not intend to undermine your brand. They are simply doing their job with what they have at hand. When there are no clear guidelines, they make their own decisions. They download the logo from the website and stretch it to fit the banner. They choose a similar color. They use a system font because they cannot install the primary font.
Each small decision does not cause disaster on its own. But when added up across ten channels, twenty partners, and hundreds of customer touchpoints: the brand starts to resemble a parody of itself.
Having guidelines is a necessary condition, but not a sufficient one. The issue is not a lack of identity. The problem is that the system is not robust enough for that identity to operate autonomously without oversight.
Design tokens (foundational values of the identity stored centrally) are the solution to this problem at the technical level. Instead of sending a partner a PDF file stating that the primary color is #1A2B3C, you provide tokens that are updated in one place and automatically propagate across all platforms: iOS app, Android app, website, and print tools.
When the brand color changes, or when a darker variant is needed for dark mode, the technical team only needs to make one adjustment. Everywhere that token is used updates accordingly. No file is overlooked. No partner continues to use the old color because they haven't received an email notification.
A brand is not a logo. A brand is the customer's perception of that product, service, or company.
Marty Neumeier, The Brand Gap
That perception is created by hundreds of small touchpoints, every day. Tokens are the mechanism that keeps those touchpoints consistent, regardless of who is operating them.
Tokens address the technical aspect. However, not all partners have a technical team capable of integrating tokens. Small shops, regional distributors, or local agents often work with manual design files. In these cases, written rules are what keep the identity from drifting.
An effective rule is not a two-hundred-page guideline that no one reads. It is a set of answers to the decisions partners will have to make themselves:
These questions are simple. But without ready answers, partners will answer them themselves, and their answers often differ among various partners.
Even when tokens and rules are clear, there are still times when partners need to do something different. They may need a banner in the size required by the e-commerce platform that is not in the library. They may need to coordinate colors according to the decoration regulations of the shopping mall. They may need to act quickly for a promotional campaign and not have time to ask.
Governance (management of the identity system) is the mechanism for handling those exceptions. It is not about reviewing each file, but rather a clear process: who can make decisions within what scope, who needs to ask for permission when, and who is the point of contact when issues arise.
Without governance, even the internal team deviates after a few months. With external partners, the rate of deviation is even faster because they are not trained and there is no one to remind them regularly.
The conventional view: a brand is a set of identities, and an identity set is a logo and colors. This perspective leads to allocating most of the budget to initial design, with almost nothing for subsequent operations.
A more suitable perspective for multi-channel distribution businesses: identity is infrastructure. Like electricity or internet in a building: no one sees it, but everything depends on it functioning correctly. Investing in that infrastructure, specifically tokens, rules, and governance, is an investment to ensure the brand operates correctly when you are not present.
This is why Sinh Vũ builds a Brand Operating System for each client instead of just delivering a brand identity. A beautiful identity without an operational mechanism will drift off course within six months, according to observations from actual implementation projects. The operating system ensures that the identity remains consistent wherever it appears, even in places where no one from your team is present.
Marty Neumeier, The Brand Gap. Byron Sharp, How Brands Grow (Ehrenberg-Bass Institute). Marq / Demand Metric, Brand Consistency Report, 2021. Adobe, Content Authenticity and Brand Consistency Survey. W3C Design Token Community Group, stable spec 10/2025. Nathan Curtis, Modular Web Design and the EightShapes series on design system governance.
Design tokens are a set of foundational values for the identity, such as color codes, font sizes, and spacing, stored in a single location and automatically applied across all platforms. When partners use tokens instead of manually entering each parameter, errors due to confusion are almost eliminated. This is why large systems like Google's Material 3 and Salesforce's Lightning are built on a token foundation.
It doesn't need to be complicated, but it needs to be sufficient. Even with just one partner, you still need documentation that clearly states which colors can be used, which fonts to substitute when the primary font cannot be installed, and what the minimum logo should look like. Without this part, partners will make their own decisions, and the results often do not meet expectations. The level of detail correlates with the number of partners and their design autonomy.
Control through the system, not by reviewing each file. Provide tokens, a component library, and a set of written rules, along with examples of correct and incorrect usage. The partner's design team can be creative within those limits while still maintaining the identity. If necessary, set up a quick review round for important applications like campaign banners or payment interfaces.