Why most businesses are not yet ready to implement a brand operating system
The brand operating system is a powerful tool, but implementing it before there is a real need will create a machine that no one operates and waste the budget.
Most Vietnamese businesses currently do not need a brand operating system because their challenge is finding customers and increasing visibility, not coordinating many people to produce consistently. The real threshold appears when the team expands to the point where multiple departments touch the brand and no one knows what anyone else is doing. Until that threshold is reached, a good set of standards along with a template is sufficient and significantly cheaper.
- Many touchpoints, many people involved in production.
- Prepare to scale or manage multiple brands.
- Preparing for an IPO, M&A, or regional expansion
- A small team, one brand, without an annual maintenance budget.
- The commitment scope is under 18 months.
Sinh Vũ is straightforward from the beginning: a brand operating system is not the natural next step after creating a logo and guidelines. It is a tool for a different problem that arises at a different stage. Most businesses questioning the operating system are not actually at that stage.
What is the real challenge ?
There are two completely different problems that businesses often confuse as one.
The first challenge is finding customers and increasing visibility: the market does not know who you are, does not trust you, and does not remember you. This is the challenge for most startups and businesses in the early or mid-stages. The right solution is a clear identity foundation, sharp messaging, and appropriate channels, not a complex operating system.
The second challenge is consistent coordination: many people, many departments, many touchpoints producing brand content and images every day, with no one knowing what others are doing, resulting in chaotic outcomes. This is the challenge that a brand operating system is designed to solve.
If you do not have a second problem yet, purchasing a solution for a second problem is unnecessary.
The real threshold is coordination, not scale
The question is not "how many people are on my team" but rather "how many people are touching the brand every day and how are they coordinating?"
According to practical consulting observations from Sinh Vũ, the threshold to consider often appears when multiple departments are producing the brand in different directions, when preparing for franchising or opening branches, or when preparing for significant events such as M&A or IPO. McKinsey, when analyzing marketing operational models, also pointed out that the transition from the exploratory phase to coordination is a pivotal point, not a fixed headcount threshold.
Qualitatively speaking: if everyone involved with the brand can still sit in the same room and talk directly to each other, then a large coordination system is not yet necessary.
Signs of not yet reaching the threshold.
- Only one or two people actually handle the design and brand content.
- A single brand, with no plans for multi-branding or franchising.
- The commitment scope is short, under 18 months, with unclear long-term direction.
- There is no annual maintenance budget for the system after it is built.
- The current priority is still to increase visibility and find new customers.
Missing one of the above conditions is not a reason to stop indefinitely, but missing multiple conditions at once clearly indicates it is not the right time.
Common mistakes when starting too early
The most common mistake is buying an operating system out of trend, after seeing a larger business do it and thinking they should have it too. The result is a beautiful set of documents, a complete set of processes, and no one actually runs it because the team is not complex enough to need it.
Nielsen Norman Group, when researching DesignOps, also clearly states: the operational machinery should follow real needs, not lead. A small team only needs to think lightly about operations, without needing a full machinery.
The second mistake is ignoring annual maintenance costs when making decisions. An operating system is not a one-time purchase. It requires maintenance, updates, and training for new users. If this cost has not been accounted for, it is better not to start.
Create standards and BOS Lite (lightweight package): Suitable when the team is still small, with one brand, and the main challenge is basic identity and consistency. Lower cost, faster implementation, no unnecessary purchases.
The viewpoint of Sinh Vũ
Sinh Vũ proactively defines this boundary because O2 (brand operating system) is a flagship service but not for the masses. Proposing a service larger than the actual need is not good consulting; it is selling.
If you have not reached the threshold, Sinh Vũ will state that directly and suggest starting from the identity foundation or a more suitable standard package. When the business grows and the coordination problem truly arises, the operating system will then have room to thrive.
The operational system should follow real needs, not lead. Small teams only need a light operational mindset, without a full-fledged structure.
Nielsen Norman Group, DesignOps 101
Decision checklist
Topic: Why most businesses shouldn't implement a brand operating system just yet. 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
McKinsey, Connecting for growth: A makeover for your marketing operating model. Nielsen Norman Group, DesignOps 101. Consulting perspective and qualitative estimates: Sinh Vũ, based on practical experience consulting for Vietnamese businesses.
Frequently asked questions
My team has several dozen people, so do we need a brand operating system?
It's not the size of the entire team that matters, but the number of people actually involved in brand production every day. If only one or two people are handling design and content, it's not yet a coordination issue. When multiple departments are publishing, ordering designs, and communicating with partners in various directions, that's when the coordination system truly adds value.
After establishing brand identity guidelines, is the next step an operating system?
Not necessarily. The identity standards address the question of appearance, while the operating system addresses who does what, in which process, measured by what metrics. If the team is still small and the issue is still increasing recognition, the next step is to effectively use the existing standards, not to purchase an additional layer of a new system.