Most brand projects are judged on a single image: the logo, enlarged on a slide, approved or rejected in a meeting. Then the work actually begins — a sales deck, a job advert, an app icon, an invoice, a trade-show banner, a WhatsApp message from the support team — and none of those things were in the presentation. Whether they look like the same company is decided by something that was never on the slide.
That something is the identity system. It is the difference between a company that looks designed and one that merely once hired a designer.
The short version
- A logo is one asset. An identity system is the set of decisions that lets other people make new things correctly.
- Judge a system by what a stranger can build with it, not by how the presentation looked.
- Five properties: distinctive, coherent, flexible, accessible, governable.
- Design the hardest applications first. A system proven on the easy ones breaks on contact with reality.
- Rules people can follow beat rules that are theoretically correct. Written for a non-designer, or it will be ignored.
A logo is an asset. An identity is a system.
The logo gets the attention because it is the only part that fits on one slide and can be approved in one meeting. But a logo answers exactly one question — what mark goes in the corner — and the company has hundreds of other questions. What size is a heading on a phone. Which green, of the four greens now circulating. How much space goes around the mark on a vehicle. What a table looks like in a sales proposal. Whether the recruiter’s job advert is allowed to use the display typeface.
An identity system answers those questions in advance, so that people who are not designers, working without you, produce things that belong together. That is the actual deliverable. The logo is a by-product.
A system is not judged by what you made with it. It is judged by what a stranger can make with it.
Five properties of a great identity system
1. Distinctive — recognisable with the name removed
The system should be identifiable from a cropped fragment: a colour, a type setting, a shape, a photographic treatment. Most brands in a category converge on the same visual language, which is comfortable and useless. Distinctiveness is a commercial asset, not a matter of taste.
Test: cover the logo on three of your assets. Can someone in your market still name you?2. Coherent — the parts clearly come from one decision
Coherence comes from shared underlying logic, not from repetition. A single geometric principle in the mark, the shapes, the grid and the corner radii will hold a system together far better than stamping the logo on everything.
Test: put six unrelated pieces side by side. Do they look like siblings or like cousins?3. Flexible — it survives contact with the real world
The system must work at 16 pixels and on a six-metre banner, in colour and in one ink, on a dense data table and on a silent video. Flexibility is designed in by testing the extremes early, not by adding exceptions later.
Test: does it hold as a 16px favicon, as an embroidered shirt, and in a black-and-white invoice?4. Accessible — legible to everyone who has to read it
Text and background pairs that clear WCAG AA, type sizes that work for older eyes, meaning never carried by colour alone, and a motion policy that respects reduced-motion settings. An identity that excludes people is not elegant, it is unfinished.
Test: does every approved colour pairing clear 4.5:1 for body text?5. Governable — someone owns it and it can evolve
Files where people will look for them, in formats they can actually use. A named owner for questions. A way to request an exception. A system nobody maintains decays into four versions of the blue within eighteen months.
Test: can a new employee find the correct logo file in under two minutes, without asking anyone?Build one, and watch the rules appear
Every choice below changes dozens of downstream artefacts at once. That cascade — one decision propagating consistently — is what a system is.
Identity system builder
Three decisions. Watch the mark, the page and the applications move together.
Colour direction
Typographic voice
Shape language
Freight that arrives when we said it would
The same system has to work on this page, on an invoice, on a driver’s app and on the side of a truck. If any one of them needs an exception, the system is not finished.
What is actually inside a system
A complete system has four layers. Most projects deliver the second one and stop.
| Layer | What it contains | What breaks without it |
|---|---|---|
| Verbal | Positioning, naming conventions, tone of voice, a short word list of terms you do and do not use | The company looks consistent and sounds like four different organisations. |
| Visual core | Mark and lockups, clear space, typography and type scale, colour roles, grid, shape language, photography and illustration direction | Nothing — this is the layer everyone does. |
| Digital | Design tokens, component styling, states and interaction, motion rules, icon set, accessibility pairings, dark mode | The website drifts from the brand within one redesign cycle, because the brand was never expressed in the things the product is built from. |
| Governance | Named owner, asset library, templates, exception process, review cadence, onboarding for new staff and agencies | Four versions of the blue, three logo files in circulation, and a designer re-explaining the rules every quarter. |
The highest-leverage deliverable in most identity projects is not the guidelines document. It is the templates — a proposal deck, a social post, a job advert, an invoice — because they let people do the right thing without reading anything.
How to create one
1. Find the strategic fact first. Before any visual work, settle one sentence: what this company is for, who it is for, and what makes it genuinely different. Not a mission statement — a usable fact. “We are the only one in this market that delivers on a fixed date” gives a designer something to work from. “We value excellence and innovation” does not.
2. Audit what already exists, including the unofficial. Collect everything the company actually puts in front of people — including what the sales team made themselves in PowerPoint. That folder tells you what the system must solve for, and it is never what the brief says.
3. Design directions, not logos. Present two or three complete worlds: type, colour, shape, imagery, shown on real applications. Never present a mark on a white slide. A direction that only looks good in the presentation is a direction that will fail in week three.
4. Build the core, then immediately break it. Once a direction is approved, take it to the hardest applications first — the favicon, the single-colour print, the dense data table, the regulatory document, the embroidery. The system earns its rules by surviving the extremes.
5. Document as rules a non-designer can follow. “Use the primary colour for one call to action per screen” is a rule. “The palette should be applied with restraint and balance” is a wish. Write for the recruiter making a job advert at 6pm, because that is who will use it most.
6. Roll it out with templates and a named owner. Launch is not publishing a PDF. It is a session walking people through the system, templates in the tools they actually use, files where they will look, and one person who answers questions for the first six months.
How identity systems fail
| Failure | Looks like | Prevention |
|---|---|---|
| Designed for the pitch | Beautiful on the hero image, unusable on a form | Test on the boring applications before approval. |
| Rules without reasons | Everyone breaks them, nobody knows why they existed | One line of rationale beside every rule. |
| No exception route | Teams quietly go off-system rather than ask | A named owner and a two-day turnaround on requests. |
| Too rigid | Every new need requires a new approval | Define principles, not just permitted artefacts. |
| Too loose | “Use any of these twelve colours” | Assign colour roles, not a palette. |
| Delivered as a PDF only | Nobody can get the real files | A live asset library with templates in working formats. |
| Nobody owns it | Drift within a year | A named custodian and a scheduled annual review. |
Knowing whether it worked
Identity work resists measurement, but not completely. Three signals tell you most of what you need. Unprompted recognition — can people in your market identify your material with the name removed? Off-system output — count the pieces produced in a quarter that did not follow the rules; if that number is rising, the system is too hard, not the people too careless. Time to produce — how long it takes a non-designer to make an acceptable asset. A good system makes that faster every month.
If the rules are being broken constantly, the rules are the problem.
How we build identity systems at Adi Design. Strategy first, directions tested on the hardest applications before approval, tokens and templates delivered alongside the guidelines, and a named owner handed the system at the end rather than a PDF. If you are planning an identity project, get in touch.
