Visual Identity
An identity system that still works on the four hundredth asset
A logo is one artefact. An identity is the system that lets a hundred people produce consistent work without a designer in the room — type, colour, grid, photography and motion, with rules specific enough to survive a website, an ad account and a social calendar.
The distinction that decides the budget
A logo package and an identity system are different purchases
Both are legitimate. They cost different amounts, solve different problems, and fail in different ways, and confusing them is the most common reason a brand project disappoints.
| Dimension | Logo and asset package | Identity system |
|---|---|---|
| What you receive | A mark, colour values, a typeface choice, a short usage document | Type scale, colour roles, grid, spacing, imagery direction, iconography, motion, templates and task-based guidelines |
| Who can produce on brand | A designer, or anyone copying an existing piece closely | Anyone on the team, for the asset types the system covers |
| Right when | Output is low volume and largely produced by one person | Several people produce assets across several channels every week |
| Where it breaks | The first time someone needs something the document does not cover | When the system was built for flattering cases and not awkward ones |
| Cost profile | Lower upfront, recurring design cost on every new asset | Higher upfront, much lower marginal cost per asset afterwards |
| Digital readiness | Often untested — contrast and small sizes discovered later | Tested in a browser and at real sizes before it is delivered |
Where identities actually fail
The website is the test, and most identities are not designed for it
An identity presented as a set of large, carefully composed slides will always look convincing. The difficulty is that almost none of the assets a business actually produces resemble those slides. They are pages of dense text, forms, tables, small advertisements, email signatures and social posts made in a hurry.
This is why we design against real applications while the system is still being decided rather than afterwards. The palette is checked as body text on a real background at real sizes, because a colour that reads beautifully as a large heading frequently fails contrast requirements at fourteen pixels. The typeface is checked for the weights an interface needs, for how much it costs to license for web use, and for how much it weighs when it loads.
The mark gets the same treatment: at favicon size, in a single colour, on a photograph, and inside a space narrower than it wants to be. Marks with fine detail or tight interior counters disappear in exactly those places, and those are the places most people will encounter it.
The result is less dramatic to present and considerably cheaper to live with. Nothing has to be quietly re-specified during the website build, and the team does not end up maintaining an unofficial second palette that exists only because the official one was unusable.
Scope
What the system actually contains
Not every engagement needs all of this. Scope is set by what your team produces and how often, and we would rather build fewer parts properly than deliver a document with a section for everything and rules for nothing.
- Wordmark and logo variants with explicit rules for each — minimum sizes, single-colour use, clear space and what to do when the space is too narrow
- A typographic scale with defined roles, tested at interface sizes, with web licensing and file weight settled
- Colour with roles rather than a swatch row — text, surface, border, accent and state colours, contrast-checked in a browser
- A grid and spacing scale that maps directly onto how the website will be built
- Photography direction shown with real examples and, more usefully, counter-examples
- Iconography produced as files, not described as a style
- Motion principles covering interface behaviour and campaign use, with limits so nothing damages performance or accessibility
- Templates for the five or six assets your team makes most often
- Guidelines organised by task — "make a social post", "build a proposal" — rather than by design principle
- Production files, web fonts and a handover session with the people who will use them
Standards
What we hold an identity to before we hand it over
Every system we deliver
- Is tested as a live web page before delivery, not only as presentation slides
- Has text colour combinations that meet WCAG 2.2 contrast requirements as specified
- Names the typeface licensing and the loading cost, so nothing is a surprise during the build
- Includes the awkward applications — dense text, small ads, single colour, favicon size
- Ships with editable templates for the assets the team produces most often
What we will not do
- Present an identity only on flattering, large-format layouts
- Specify a display typeface with no usable weights for body text or interface use
- Deliver guidelines written for designers when the daily users are not designers
- Recommend motion that damages accessibility or page performance
- Sell a full system to a business whose output volume does not justify one
How it runs
From position to production files
Audit what you produce
A count of the assets your team actually makes, who makes them and how often. This decides how much system you need and which parts matter, and it is usually a surprise to everyone involved.
You get: Asset inventory and production reality
Establish the design direction
Two or three directions, each shown on real applications rather than as a mark on white. You judge them as a web page, a document and an advertisement, because that is where they will live.
You get: Directions shown in applied context
Build the system
Type scale, colour roles, grid, spacing, imagery, iconography and motion — developed together and tested against the awkward cases as they are built rather than at the end.
You get: Working system with contrast and size testing
Template and document
Templates for the highest-volume assets, then guidelines organised around the tasks people perform. Short, task-led and specific enough to settle a disagreement.
You get: Templates and task-based guidelines
Hand over properly
Production files, web fonts, a session with the people who will use it daily, and a named owner on your side who reviews output periodically so drift is caught early.
You get: Full asset handover and team session
Questions
What people ask about identity work
Do we need a full identity system or just a logo?
It depends on how much you produce and who produces it. A business with one website and a handful of documents can operate reasonably on a logo, a typeface and two colours.
The moment several people are producing assets across several channels every week, the absence of a system becomes expensive: everything needs review, output drifts, and the company starts to look inconsistent to anyone who encounters it more than once.
Will a system constrain our marketing team?
A good one removes decisions rather than options. Nobody should be deciding a heading size or a photography treatment from scratch each time, and the time that goes into those decisions is not producing anything.
Where systems do become constraining is when they cover only the safe cases. If the guidelines have nothing to say about a paid social ad or a conference stand, people improvise, and the improvisation becomes the real brand.
Do brand colours need to pass accessibility contrast checks?
Text does. Under WCAG 2.2, normal body text needs a contrast ratio of at least 4.5 to 1 against its background, and large text at least 3 to 1. Plenty of brand palettes were never checked against that, which is why so many websites quietly use a darker version of the brand colour for text.
The practical answer is to design the palette with defined roles from the start — which colours are for text, which for surfaces, which for accents — and to test them in a browser rather than on a presentation slide.
How do we stop the identity drifting within a year?
Three things do most of the work: templates for the assets produced most often, guidelines organised around tasks rather than principles, and a named owner who reviews output periodically.
The other factor is coverage. Drift usually starts in the situations the guidelines did not anticipate, so we build the system against the awkward cases — a dense data table, a small-space ad, a co-branded document — rather than only the flattering ones.
Can you work with our existing logo?
Frequently, yes. A lot of businesses have a serviceable mark and no system around it, and building the system is a smaller, cheaper project than starting again.
We would recommend replacing a mark when it is technically unusable — illegible at small sizes, dependent on effects that fail in a single colour, or with no usable digital source files — or when the strategy has changed what the business is claiming to be.
Show us the last ten things your team produced
That set will tell you more about your identity than any audit. If they look like one company, you may not need this work. If they look like four, we can show you exactly where the system is missing.
Related
Where to go next
- brand strategy and developmentIdentity expresses a position that should already be settled.
- the positioning decisions underneathDesign cannot resolve an unresolved strategy.
- website design and buildWhere an identity system is most severely tested.
- social channel productionHigh-volume production is what breaks weak systems.
- campaign asset production
- the standards we work to
Last updated · Reviewed by Zubair Afzal