Brand and Creative
Brand identity and design systems
The job here is specific: make the brand reproducible by people who were not in the room when it was designed.
What happens in a brand identity and design systems?
Make the brand reproducible by people who were not in the room when it was designed. In practice that means a visual system with rules rather than examples, so new work stays consistent, and then the harder half: components and templates for the formats produced weekly.
Why this work exists
Put bluntly: the alternative is making decisions on numbers nobody has checked.
This is one part of Brand and Creative, described separately because it is usually the first thing anybody needs.
The nearest piece of work to it is deciding what the brand will not say, which is half of positioning. Where that is already handled, this moves faster than the estimate; where it is not, the two get done together or neither of them holds.
What good looks like
When this is working, the answer to a question about it is a document rather than a conversation, and the document is current.
The gap between that and where most accounts start is why this is scoped as brand identity and design systems rather than as a line inside something larger. Getting the sales deck and the website to tell one story is the usual second step once it is in place.
When this is the right work
The tells:
- Every new asset looks slightly different
- The brand guidelines are a PDF nobody can find
- Agency and in-house work are visibly from different brands
If none of those is true, something else is probably the constraint, and the Brand and Creative overview maps the alternatives. The usual neighbours are finding where the visual identity falls apart in practice and building a system a non-designer can use without breaking it.
What the work covers
What the work actually involves:
- A visual system with rules rather than examples, so new work stays consistent, revisited rather than finished, because the inputs keep moving.
- Components and templates for the formats produced weekly. Usually quick; occasionally the thing that reopens the whole scope.
- Accessibility checked at the system level, so contrast is not re-litigated per asset, which changes often enough that a single pass has a shelf life.
- Governance: who approves an exception and how it gets recorded. This is the piece a client can verify themselves, which matters more than it sounds.
How it runs
How this gets done without the usual two-month discovery phase.
The cheap wins
Anything that can be fixed in an afternoon gets fixed in the first week, partly because it is free progress and partly because it clears the view.
Setting the guardrails
Limits get agreed early: what will not be touched, what needs sign-off, what can be changed without asking. Arguments about scope mostly trace back to skipping this.
Testing on the awkward cases
Whatever gets built is checked against the messy real examples rather than the clean ones, because the clean ones were never going to be the problem.
What each part runs into
What gets in the way, part by part:
- A visual system with rules rather than examples, so new work stays consistent, and in Pune the constraint on it is an enquiry path that runs through a messaging app rather than a form
- Components and templates for the formats produced weekly, harder in Ahmedabad because of a catchment smaller than the ambition on the website
- Accessibility checked at the system level, so contrast is not re-litigated per asset – in Abu Dhabi, complicated by the fact that an incumbent whose position comes from presence rather than effort
- Governance: who approves an exception and how it gets recorded, which in Leeds runs into a buying pattern that resolves faster than the reporting cycle
The trap
Delivering a PDF and calling it a system. A system is components people use, not a document people are told to read.
This is the version most often delivered, which is why the discipline has a worse reputation than it deserves.
How it is measured
Share of assets produced from the system, and how often exceptions are requested. It is reported with the existing metrics rather than replacing them, because a new number nobody recognises persuades nobody.
Where the figure is estimated rather than counted, it says so on the report.
What you end up with
What gets handed over: a documented system with working components, plus the governance that keeps it from drifting.
Plain language throughout. Jargon gets defined where it is unavoidable.
How it differs by sector
Read across three sectors, the differences are clear:
- Manufacturing and industrial, constrained by the fact that low volume, high value, and a specification sheet that decides the deal.
- Automotive: Local inventory, model-level demand, and a buyer who arrives having already decided. so this work has to account for that before anything else.
- Ecommerce and retail, where margin per order decides everything, and the product feed is usually the weakest asset. which moves this work earlier in the plan.
The industry pages carry the rest of that detail. Manufacturing and industrial and Automotive are the two where this piece of work most often decides the outcome. Core Web Vitals remediation is the prerequisite. JavaScript rendering audit is what it makes possible.
Common questions
How detailed should guidelines be?
Detailed where mistakes are expensive, loose where they are not. Rules nobody can follow get ignored entirely.
Who maintains the system?
Somebody named. A system without an owner drifts within two quarters.
How do we know this is the right piece of work?
The signals above are the test. If none of them describes your situation, something else is the constraint, and saying so is more useful than selling this. The sequencing matters: Vancouver before Abu Dhabi, not the other way round.
What happens if it does not work?
We report that it did not, with the reason. Share of assets produced from the system, and how often exceptions are requested agreed before the work starts makes that an honest conversation rather than an argument. Where this gets detailed is Automotive; where it gets argued about is B2B services.
Who does the work on brand identity and design systems?
A practitioner rather than an account manager, and the same person throughout. Share of assets produced from the system, and how often exceptions are requested is their number, which is the only arrangement under which the reporting stays honest. Read Local SEO next if the problem is already defined, and Marketplace Marketing if it is not.
Ask about brand identity and design systems
Send what you know. We will come back with what we would check and roughly what it involves.
Start with an honest read on the gaps
Send us your site and your goals. You will get an honest read on the gaps worth fixing first, whether or not you work with us.