How many people touch the brand require a operating system?
The question is not how many people your company has, but how many people are actively creating brand assets without anyone maintaining consistency.
There is no hard number of personnel to set a threshold. The real signal is when many people create brand assets without anyone maintaining consistency, leading to repeated questions about which logo, color, or template to use. Until that threshold is reached, a static set of standards and a few original templates are sufficient, without needing to create an operating system.
- Many people create assets together, and the brand begins to drift off course.
- Onboarding new users takes weeks due to the lack of a single source of truth.
- Dozens of agents and freelancers are self-producing assets.
- One to two people who can hold and remember the entire standard.
Many business owners ask this question incorrectly: "How many people does my company need to have an operating system?" The better question is: how many people are creating brand assets together, and how dispersed are they? The total number of employees does not say anything. The number of people touching the brand is what matters.
The real threshold is not a number
There is no hard personnel threshold recognized by the design operations industry (DesignOps, which studies how to organize design teams for effective operation) that states "from here, we must implement an operating system." The real signals come from three dimensions: the number of people creating and releasing assets, their level of dispersion across departments or locations, and the frequency of questions about preparation for repetition. When these three dimensions exceed the ability of one or two people to maintain consistency by memory, the operating system has a reason to exist.
Factors that need to be counted correctly
You need to list everyone who interacts with the brand, not just the internal team:
- The number of people creating, reviewing, and releasing brand assets within the company, including marketing, sales, and design.
- The number of external partners working in parallel: agency (outsourced creative unit), freelancer, printing house, distribution agents producing content at the point of sale.
- The number of branches or regions producing content independently without central approval.
- The number of channels currently running and the frequency of content production each week.
- The time it takes for a newcomer to understand and correctly use the brand standards without asking anyone.
A company with fifteen internal employees but thirty agents creating banners may need a more robust operating system than a fifty-person company with centralized operations.
When is it needed, when is it not needed yet
Need to build an operating system when: The question "which logo, which color, which template" is frequently repeated. Onboarding new employees takes weeks due to the lack of a single source of standard assets. Assets created by different teams do not look consistent. There are external partners or branches creating assets without oversight.
No need when: One or two people can handle everything and remember all the standards. The production volume is low, with few channels and partners. There is no budget for annual maintenance after completion.
The breaking point of a brand rarely lies in the quality of the initial identity. It lies in daily operations when many people work together without a single source of truth.
Sinh Vũ, service O2 Brand operating system.
Common errors
- Counting the wrong audience: Only counting internal personnel while overlooking agencies, freelancers, and distributors who are producing assets daily.
- Confusing scale with complexity: Thinking that a small company does not need it yet, while the external partner network is already complex enough to create risks.
- Wait until things are heavily off track: Many businesses only start thinking about operations after their brand has lost consistency everywhere. Fixing is more costly than preventing at the right time.
- Build a system before reaching the threshold: Creating a complex operational system for a team of one or two people is wasteful, and that system is often neglected because it is too cumbersome for actual needs.
Sinh Vũ's viewpoint
Most Vietnamese businesses are at a stage where the marketing team is still small, with one brand, and do not have the budget to maintain an annual system. For most of them, a static, clear set of brand guidelines and a few pre-locked design templates are enough to maintain consistency. A complete brand operating system is the next step, not the first.
Sinh Vũ observes that brand signals are drifting: assets created by different points of contact start to look different, raising questions about consistency, and onboarding is prolonged. This is when questions about the operating system arise, not when counting a certain number of personnel.
Decision checklist
Topic: How many people touch the brand before needing an operating system. Sinh Vũ guide, sinhvu.com
Select each item you find appropriate, then print or save as PDF to take with you.
If you have marked most of the signs above, this is the time to discuss in more detail. Sinh Vũ can help you review and propose a direction.
References
Nielsen Norman Group, DesignOps 101. Sinh Vũ, O2 service page.
Frequently asked questions
My company has only fifteen people but twenty sales agents creating their own banners. Do I need an operating system?
There is a likelihood of need, as sales agents also interact with the brand. When twenty agents create assets without a single source of truth, the brand will drift at the point of sale before you realize it. The minimum step is to create a set of locked assets and a clear release process for agents, then assess whether a more comprehensive operating system is needed.
I only have one person doing marketing but want to build an operating system to scale later. Should I do it now?
You shouldn't. When one person can handle everything and remembers all the standards, the cost of building an operational system outweighs the benefits it brings. Sinh Vũ recommends using a static standard set and a few core templates first. When the team expands and questions about standards begin to recur, that's when to consider an operational system.