A logo is not a brand identity

A logo answers one question. A business has several hundred more. What a brand identity system actually contains, and the one test that tells you whether you have one.

The most expensive misunderstanding in branding is that a brand identity is a logo with some extras attached. It leads to a predictable sequence: the logo is approved, everyone is pleased, and then six months later nothing the business produces looks like it came from the same company.

The logo was never the problem. The problem is that a logo answers one question — what is the mark? — and the business has to answer several hundred more.

The questions a logo cannot answer

Every one of these comes up within weeks of launch:

  • What does a headline look like, and what does body copy look like next to it?
  • How much space goes between a heading and the text under it, and is that the same everywhere?
  • Which of the brand colours can carry text, and which are decoration only?
  • What does a button look like, and what does it look like when you hover over it?
  • What happens to the mark at 16 pixels, on a dark background, on a photograph?
  • When somebody in the business needs a slide, an ad and a label in the same week, how do they all end up looking related?

If the answer to any of these is “ask the designer”, the brand is not a system. It is a dependency.

What a system actually contains

A type scale, not a font choice

Picking a typeface takes an afternoon. Building a scale — a fixed set of sizes with fixed line heights and fixed weights, each with a stated job — is what makes two people produce consistent work without talking to each other. Without a scale, everyone sets headings at whatever looks right on the day, and nothing lines up.

A colour system with roles

Not a row of swatches. A structure: which colour is the surface, which is the text on that surface, which is the accent, and what the accessible pairings are. A palette without roles gets used decoratively, and decorative use is what makes a brand look scattered.

A spacing rhythm

One base unit, and every gap in the system a multiple of it. This is the single least visible and most load-bearing part of an identity. It is why professional layouts feel calm and amateur ones feel restless, and it survives being applied by somebody with no design training.

A defined graphic device

Something other than the logo that says who this is — a shape, a cut, a rule, a grid behaviour, a photographic treatment. It is what lets a piece be recognisable when the logo is small or absent. Without one, every piece has to shout the logo to be identifiable.

Rules for the mark

Clear space, minimum size, the approved lockups, the backgrounds it may sit on, and — more useful than any of those — a short list of the things people will try to do to it that they must not.

Applied examples

The system proven on real artefacts: a business card, a social post, a document, a page. Examples are what make the abstract rules obeyable. Nobody reads a specification. Everybody copies a template.

How you know you have a system and not a logo

One test: hand the files to somebody who is not a designer and ask them to make something you did not brief. An invoice, a job ad, a delivery note.

If what comes back is recognisably yours, the system works. If they had to guess at sizes and picked colours because they liked them, you have a logo and a folder.

Why this is cheaper, not more expensive

A system looks like the more expensive option because it is more work at the start. It is the cheaper option over any period longer than a few months, for a reason that has nothing to do with design.

Without a system, every piece of collateral is a small design project. Somebody has to decide, somebody has to approve, and often somebody external has to be paid. With a system, most pieces are assembly. The decisions were made once and they stay made.

The business that gets the most out of an identity is not the one with the best logo. It is the one whose team can produce work without asking permission and still have it look like the company.

The identity work I do is built as a system by default, and every project hands over the rules alongside the files. If the system needs to reach a shelf, packaging is where those rules get their hardest test.