How many people does the brand start to drift

There is a question that many brand managers only ask when it is too late: "When did our identity become so chaotic?" The answer is rarely due to a lack of guidelines. Most often, it is because the organization's scale has exceeded a certain threshold. Yet the level of systematization has remained the same since the team was just 5 people.

Under 10 people: seed is enough

At this scale, the brand often runs through one or two people. The founder or the person in charge directly controls most outputs. Consistency comes naturally because the number of design decision-makers is small, and everything passes through the same pair of eyes.

What is needed at this stage is not a complete system. A seed set is required: basic color tokens (primary and secondary color palette), a deliberately chosen typeface, a standardized logo version for common formats. Add a few minimal application rules. No more than that.

The trap at this stage is building too much too early. An 80-page guideline document for a team of 6 is a dead document: no one reads it, no one uses it, and it will be outdated before it is applied a second time. It is better to build less, build right, and build in a structure that can scale later.

From 10 to 20 people: the blind stage

This is the quietest danger zone. The team is large enough for many people to create media assets, but not large enough for anyone to feel the need to formalize things. The founder still thinks they are in control. In reality, that is no longer entirely the case.

At this point, design decisions begin to decentralize. Marketing managers choose background colors for advertising banners. Sales staff adjust presentation decks to their personal taste. Printing partners use old logo versions still saved in old emails. Each of these small decisions does not cause immediate problems. But they accumulate.

Marty Neumeier calls this "brand drift": the greatest enemy of identity is not competitors, but the thousands of small decisions made by those who have not been taught brand logic. At the stage of 10 to 20 people, drift has begun. But the pace is slow, so it is often overlooked.

From 20 people and above: divergence begins

This is the threshold where identity divergence becomes a measurable phenomenon. The number of brand touchpoints increases: website, social media, sales documents, emails, packaging, events, recruitment content. And each of these touchpoints has a different person making design decisions every day.

At this threshold, the static guideline documents begin to lose their effectiveness. Not because they are wrong, but because they are not close enough to actual workflows to be used. Executors need to know not just "what the color is" but also "in this specific situation, which color do I use, what font size, and who do I ask if I'm unsure."

Guidelines are not walls to block mistakes. They are GPS: they only work when the driver actually opens the map.

Operational principles, Sinh Vũ Studio

What is needed at the stage of 20 to 50 people is a real operating system layer, not just documents. Specifically, this includes: design tokens (shared design variables embedded into tools like Figma or code), a real-time accessible asset library, and a clear approval process for new assets. And at least one person responsible for consistency.

Over 50 people: the governance challenge

From 50 people onwards, the brand can no longer rely on personal control. This scale requires governance, meaning decision-making and consistency maintenance mechanisms that are institutionalized, independent of whether someone "remembers" or "pays attention".

According to data from Adobe (2021), in larger organizations, an average of 71% of brand assets require at least 7 approvals before release. This is a sign of a system lacking a single source of truth. People must cross-check each other because they do not trust the original documents.

Design tokens (shared design variables) partially solve this issue at the technical layer: change once, propagate to all touchpoints. But tokens are just tools. Governance is the human mechanism: who has the authority to decide what, what the change process looks like, and how the system updates as the brand evolves.

Three layers of the system by scale

The most practical way to view this issue is through three progressively increasing layers:

• Level 1: Seed (under 10 people). Core tokens, standardized logo, a few basic application rules. Goal: enough consistency to be recognizable, flexible enough not to hinder speed.
• Level 2: Operational system (10 to 50 people). Design tokens embedded in tools, a real-time asset library, clear approval processes, and a person responsible for consistency. Goal: consistency that does not rely on personal memory.
• Level 3: Governance (over 50 people). Brand decision-making mechanisms are institutionalized, with regular update processes and clear delegation between departments. Goal: a self-sustaining system that remains consistent even without someone "overseeing" it.

Questions for self positioning

Instead of counting heads, there are three questions to help determine where you are and what you need:

• How many people in the organization are creating media assets each week, including those who do not identify as designers?
• If the brand manager takes a month off, will the identity remain consistent?
• When a primary color or font needs to be changed, how long does it take for that change to propagate across all used assets?

If the answer to the second question is "not sure" and the answer to the third question is "very long or never fully", then the current level of systematization is below the required scale. This is no one's fault. The organization has grown beyond the system that holds it together.

Consistency is the mechanism that accumulates identity in customers' memories, not just an aesthetic issue. According to the Ehrenberg-Bass Institute, distinctive brand assets only create mental availability (the ability to be recalled when purchasing) when repeated consistently for a long enough time. A team of 30 creating 30 different versions of "consistency" is a team that is depleting rather than accumulating.