A useful brand system gives teams enough structure to be recognisable and enough flexibility to communicate in different contexts. It turns strategy into repeatable choices rather than a static collection of assets.
The commercial argument for that structure is often made badly, so it is worth stating precisely. Research by Professor John Dawes of the Ehrenberg-Bass Institute, published with the LinkedIn B2B Institute, found that organisations typically change providers of services like banking, legal advice, software or telecoms around once every five years. That implies roughly 20% of potential buyers are in-market in a given year and about 5% in a given quarter — leaving around 95% who are not currently buying but will be later (Ehrenberg-Bass Institute / LinkedIn B2B Institute).
Marketing aimed only at the 5% competes for a small, expensive pool. The purpose of a brand system is to make you memorable to the other 95% long before they start looking — and Ehrenberg-Bass's related work on distinctive brand assets stresses that this depends on consistent, recognisable use of assets over time rather than frequent reinvention. That is the premise of our branding work.
Clarify the idea people should remember
Positioning should define who the brand is for, the value it creates and the perspective that makes it distinct. A memorable central idea helps verbal and visual expression pull in the same direction.
The bar is lower and harder than it sounds. It is not a mission statement. It is a claim specific enough that a competitor could not credibly make it, and simple enough that a customer could repeat it after hearing it once.
A working test: ask five colleagues from different teams to describe what the organisation does and who it is for. If you get five materially different answers, no visual system will fix the incoherence — it will only make it consistent-looking.
Dawes's related finding is worth noting here: in B2B, lack of awareness is a far more common problem than negative perception. Most of the buyers you are not winning have not rejected you. They have never registered you at all.
Design relationships, not isolated assets
A logo cannot carry the whole identity. Typography, colour, image direction, layout and motion should work as a coordinated set with clear roles and hierarchy.
In practice, the logo is rarely the asset doing the recognition work in digital contexts. A distinctive typographic voice, a consistent colour relationship or a recognisable photographic treatment is more likely to be doing the identifying — because those elements are present across an entire page, while the logo occupies a corner.
Useful things to define explicitly:
- Roles, not just values. Which colour signals a primary action, which signals a warning, which is decorative. A palette without roles becomes a free-for-all.
- Hierarchy in type. A scale with defined purposes, rather than a list of approved typefaces.
- What the imagery is about. "Authentic and human" is not direction. "Real staff, real premises, natural light, no stock" is.
- Motion and interaction character. Timing and easing are part of brand expression, and are almost always left undefined.
Build for real channels
Test the system in product interfaces, sales material, social content, campaigns and long-form pages. Real applications reveal whether the identity is expressive, accessible and practical.
Accessibility deserves specific mention because brand palettes are one of the most common sources of failure. WebAIM's 2026 scan of the top one million home pages found low contrast text on 83.9% of them — the single most common accessibility failure, and one that has topped the list every year since 2019 (WebAIM Million, 2026).
Those failures usually originate in a brand guideline, not a developer's mistake. A palette signed off on a printed board in good light becomes an unreadable caption on a phone in sunlight. The fix is straightforward if done early: test contrast ratios at the point the palette is chosen, and define accessible pairings — which colours may sit on which backgrounds, at which sizes — as part of the system rather than as a later exception.
The same logic applies to type. A display face that looks distinctive at 96px may be genuinely hard to read at 16px, which is where most of your words will actually live.
Give teams useful guidance
Good guidelines explain intent and show decisions in context. Templates and examples reduce reinvention while leaving room for judgement.
The difference between guidelines that get used and guidelines that sit in a folder is usually whether they answer the questions people actually have. Teams rarely need to be told the hex code. They need to know what to do when they have a long product name and a short space, or a photograph that clashes with the palette, or a channel the system was never designed for.
Practical structure:
- Show the reasoning, so people can extend the system rather than only copy it.
- Include the awkward cases, not just the flattering examples.
- Provide working templates in the tools people actually use.
- Say what is fixed and what is flexible. Ambiguity here produces either paralysis or drift, and usually both in different teams.
Where a brand system meets a live product, the boundary between brand and interface work effectively disappears. Component libraries, design tokens and interface patterns are where a digital identity is enforced in practice — which is why brand and UI/UX design tend to be more effective handled together than sequentially.
Evolve from evidence
Brands grow through use. Review where the system is creating consistency, where teams struggle and which new situations need patterns. Governance should support learning rather than freeze the identity.
There is a real tension here worth naming. The evidence on distinctive assets argues strongly for consistency over time — recognition is built by repetition, and frequent identity changes discard the memory you have accumulated. But a system that cannot accommodate new channels or new propositions gets ignored, which produces inconsistency by a different route.
The resolution is to distinguish between the assets that carry recognition and the applications that carry them. Change the applications freely. Change the recognition assets rarely, deliberately, and with an understanding of what you are giving up.
Signals worth reviewing quarterly:
- Which templates get used, and which get worked around
- Where teams commission assets outside the system, and why
- Whether contrast and legibility standards are holding in live pages
- Which new situations have appeared that the system does not cover
What this looks like in practice
For Software Imaging, a global enterprise imaging and healthcare workflow specialist, the engagement combined branding, content strategy, case studies and sales collateral with the platform itself — because market positioning is carried as much by how proof is presented as by the identity around it. For The Salutation Kent, the system had to express a historic property's character consistently across accommodation, dining and location content without flattening the differences between them.
Where to go next
- For positioning, identity systems and guidelines, see branding.
- For turning a brand system into interface patterns and components, see UI/UX design.
- For implementing it as a maintainable, accessible site, see web development.
- For the design discipline underneath it, read designing digital experiences people understand.
- See more examples in our portfolio.
Sources
- John Dawes / Ehrenberg-Bass Institute with the LinkedIn B2B Institute, How B2B Brands Grow (the 95-5 rule, distinctive assets, brand rejection) — https://business.linkedin.com/marketing-solutions/b2b-institute/how-b2b-brands-grow
- Ehrenberg-Bass Institute commentary on the 95-5 rule — https://marketingscience.info/news-and-insights/ehrenberg-bass-95-of-b2b-buyers-are-not-in-the-market-for-your-products
- WebAIM, The WebAIM Million (2026) — https://webaim.org/projects/million/
Useful digital work is a continuous loop: understand, design, build, learn and improve.