Growth scatters a brand. A company at twenty people, where everyone roughly knows what the brand looks like, becomes a company at a hundred and twenty people, where everyone is making their own decisions about the brand without quite realising it. Five people produce five versions of the deck. Three people produce three versions of the one-pager. The website looks one way, the social posts look another, the internal documents look like something else again. None of the individual instances is bad. Together they are a brand that has stopped holding its shape.
This is one of the more predictable problems of company growth, and one of the harder ones to solve well. The instinctive response — heavier brand policing, more elaborate guidelines, more approval steps — usually produces resistance rather than consistency. The better response is to make consistency easier to achieve than inconsistency, by providing the tools and templates people will reach for instead of building their own.
Why the problem appears when the company grows
At small scale, brand consistency happens by osmosis. The team is small enough that everyone has seen the website, the existing decks, the few collateral pieces that exist. When someone needs to produce something new, they can ask the founder or the marketing lead, look at the most recent example, and produce something that fits. The inconsistencies are small and self-correcting, because the people involved are seeing each other’s work constantly.
This breaks at scale. The team is too large for everyone to see everything. A salesperson in one region needs a deck for a client meeting and produces one in an afternoon, using whatever template happens to be on their machine. A new hire in another region produces a one-pager from scratch, because the existing templates do not seem to exist in any findable location. A regional office begins customising the brand in ways that no one at headquarters has been asked to approve, because they need to ship something this week.
None of these is anyone’s fault. Each individual decision is reasonable in the moment. The cumulative effect is brand fragmentation, which is visible to anyone looking at the company’s output across regions, channels, and functions — and especially visible to customers, who experience the company as inconsistent rather than coherent.
The natural but ineffective response
The instinctive response to fragmentation is to tighten control. Stronger brand guidelines. Mandatory approvals. A central team that signs off on every external piece of work. This is the response of a company that has noticed the problem and decided to solve it through governance.
It does not usually work, for predictable reasons.
Heavier guidelines tend to be longer documents that nobody reads. The fifty-page brand bible, when it arrives, gets bookmarked and ignored. The brand team congratulates itself on having produced the document. The rest of the company continues to make decisions without consulting it.
Mandatory approval queues create friction that slows the company down. A salesperson who needs a deck for tomorrow cannot wait three days for brand sign-off. They either ignore the approval process and produce something themselves, or they get the deck approved by skipping the rules everyone else is supposed to follow.
Centralised brand teams become bottlenecks. Every piece of work routed through a small team is delayed by the team’s capacity. The team is asked to review work for functions and regions they do not understand well. Goodwill erodes on both sides.
The deeper problem is that brand governance, in its policing mode, treats consistency as a compliance issue. Compliance requires people to do extra work to follow the rules. People do not, in general, do extra work unless they have to.
The better response: make consistency easier than inconsistency
The approach that works at scale is different. Instead of asking people to comply with brand standards, you make the on-brand version of any deliverable the easiest version to produce. The salesperson who needs a deck for tomorrow opens the template that has been waiting for them and fills in the content. The new hire who needs a one-pager finds a working one-pager template and edits it. The regional office that needs collateral does not have to build their own, because the central library already contains what they need.
This is the work of a small design system, in the lightweight sense — a coordinated set of templates, components, and conventions that meet the actual needs of the company’s working teams. It is not the elaborate design system of a large software product, with hundreds of components and a dedicated maintenance team. It is the slimmest possible version that covers the deliverables the company actually produces, in formats the company actually uses.
What a working small design system contains
For a typical growing company, the system covers a handful of categories.
Slide deck templates. Not one master template, but two or three — a sales pitch deck, an internal deck for team meetings, and a more formal deck for executive communications. Each one has working layouts, brand-consistent typography, the right colours, and example slides showing what good looks like. Anyone who needs to make a deck starts from one of these rather than from scratch.
Document templates. A one-pager template. A short report template. A memo template. Each one in the company’s typography and colour palette, with placeholders that prompt the writer toward the right structure.
Social media assets. Templates for the common social formats the company uses, with the right dimensions, brand elements, and example layouts. A team member who needs to produce a social post can adapt one of these rather than designing from scratch.
Email signatures. Standardised, with a simple format that everyone can copy.
Letterhead and basic stationery. Templates for letters, proposals, and other formal documents. Used rarely but visible when they are used.
A simple brand reference. Not a fifty-page document, but a short, scannable summary of the colours, the typography, the logo usage, the tone of voice. A few pages that can be skimmed in five minutes and referred back to when needed.
What the system does not contain, at this scale, is exhaustive coverage of every possible deliverable. It covers the things that actually get produced often, and leaves the edge cases to be handled with judgement.
What makes the system actually get used
Having the templates is necessary but not sufficient. The other half is making sure people find them and use them.
The templates have to be findable. A shared drive folder with clear labels, linked from the company wiki, mentioned in onboarding. A new hire should be able to find the templates within their first week, without having to ask anyone.
The templates have to be current. A template last updated three years ago, that uses an old logo or an old colour palette, undermines its own purpose. The templates need to be maintained alongside the brand they represent.
The templates have to be good. A template that produces an obviously inferior result to what someone could build themselves is a template nobody uses. The templates should be high quality — better than what a non-designer would produce from scratch — so that using them is the obvious choice.
The templates have to evolve with the company. The deck template that worked when the company had twenty people may not serve a company of a hundred and twenty. Periodic review of the templates, against what people are actually producing, catches the drift and updates the system accordingly.
The role of central design
The central design team, in this model, is not the brand police. It is the team that maintains the system, supports the people using it, and handles the work that does not fit into a template — pitches, campaigns, websites, major announcements. The team’s leverage comes from producing tools that the rest of the company uses, not from gating access to design work.
This is a different kind of role from the policing model, and it requires different people. The designers who thrive in it are the ones who enjoy systems work, take pride in templates that produce good outcomes for non-designers, and are comfortable with their work being adapted by people who are not designers. Building a brand that holds at scale requires this kind of designer.
The short version
Growth scatters a brand. Five people produce five versions of the deck. The instinctive response — tighter rules, more approvals, a heavier brand bible — usually produces resistance rather than consistency. The response that works is to make the on-brand version of every deliverable the easiest version to produce, through a small, current, well-maintained set of templates and references that cover the things the company actually makes. The central design team’s job becomes maintaining that system, not policing its use. Consistency, at scale, is achieved by making the right thing the easy thing.
