SMB brands often run on the founder's memory and aesthetic judgment, not on a system. When the founder steps back, the team has nowhere to look things up, so they improvise, and the brand identity gradually drifts. A minimum documentation set has three layers: design origins, operating guidelines, and an approval process. Each layer answers a different kind of question the team faces every day.
In this article · 6 sections
Many SMB (small and medium-sized business) brands run on the founder's memory, not on a system.
The founder remembers which color that is. The founder knows which font is used for headlines. The founder decides which photo feels “right” and which does not.
The team doesn't know. They only know to ask.
While the founder is still present every day, this is not a big problem. But when the founder opens another location, hands off some operations, or simply travels for a week, the team starts to improvise.
And when people handle it on their own, everyone handles it differently.
The biggest enemy of the brand is not competitors. It is the thousands of small decisions made by people who have not been taught the logic of that brand.
Marty Neumeier, The Brand Gap
Neumeier calls this “brand drift”: the identity slowly slides off course, not because of one big event but because of the accumulation of many small, improvised decisions.
Why this situation is so common
According to a 2021 survey by Marq and Demand Metric, 85% of organizations have brand guidelines. But only about 30% apply them consistently in practice.
This gap is not because the team is lazy. In most cases, the existing documents simply do not answer the real questions people are facing.
Traditional guidelines usually say “use this color” but not “when to use the secondary color instead of the primary one”. They say “this is the logo” but not “which version to use on a dark background”.
When documentation isn't detailed enough to answer real questions, people ignore it and decide on their own.
Three minimum layers of documentation
For a brand to run on its own without the founder reviewing every detail, you need three layers of documentation, each answering a different kind of question.
Layer one: Origins and reasoning. This document records why the brand looks the way it does, not just what it looks like. Why this color was chosen.
The logo has that shape because of what it communicates. Handwritten or capital letters, because of what the brand wants customers to feel when they look at it.
Without this layer, the team has no basis for judgment when a new situation comes up. They rely on personal feeling instead of brand logic.
Layer two: Operating documents. These are specific guides for real situations: posting on social media, printing packaging, designing an event banner, sending a quote to a client.
Every situation needs an answer: which color, which typeface, what kind of image, what logo proportions.
Good operating documentation is documentation that a new team member can read and follow correctly the first time, without asking anyone else.
Layer three: Approval process. State clearly who can decide what on their own, what needs approval, and who approves when the founder is not around.
Without this layer, either everyone waits for the founder or everyone does their own thing. Both extremes are bad.
Static documents drift within six months
A 2019 Adobe survey found that 81% of content creators and designers struggle with inconsistent brand assets.
And 71% need at least seven people to review an asset before it is released.
The problem is not that the documents are missing. The problem is that they are not updated when the brand changes, and no one is responsible for keeping them “alive.”
A set of guidelines that is written, filed away in a shared folder, and six months later no one remembers the path to, is a dead document. A dead document does nothing to protect the brand.
What teams really need to ask
When Sinh Vũ works with businesses building a documentation system, the team's questions usually fall into four groups:
- I don't have the original files. What do I use to make a new design?
- A client asks for something that isn't in the brand identity. Do I do it or decline?
- Two people on the team work in two different ways. Which one is right?
- My brand feels inconsistent, but I don't know where to start fixing it.
These questions are not answered by a logo file. They need a structured documentation system.
A starting point for small businesses
You do not need to start with a complete hundred-page document. A more practical starting point is to build the part the team asks about most, first.
Usually that means: the standard color file, the font files, three to five rules for using the logo, and one page that states clearly what “this brand does not do,” so people know what to say no to.
The “this brand does not do” section is often skipped, yet it is the part that helps the team decide fastest when the founder is not there.
This figure comes from a self-reported survey, so read it with care.
But the direction matches the logic: when the team makes the right decisions without waiting for review, speed goes up and the cost of rework goes down.
When a brand truly runs itself
The clearest sign is not whether the document set is thick or thin. The sign is whether the team can answer brand questions without calling the founder.
Wally Olins once wrote that a brand is behavior, not image. Consistent behavior only happens when the people carrying it out understand the logic, not just see the templates.
Good guidelines are not a set of rules for control. They are a tool that lets the team act correctly with confidence, without asking permission at every step.
And when the team feels confident acting correctly, the brand builds up something no one else can do for it: consistency over time.
References
Marty Neumeier, The Brand Gap (2003). Wally Olins, On Brand (2003). Marq / Demand Metric, Brand Consistency Report (2021). Adobe, State of Creative and Marketing Collaboration (2019). McKinsey & Company, The Business Value of Design (2018).