You Don't Need a New Logo.

Good design solves one problem. A system solves every problem that comes after.

Anne Wonner — Bureau Dimanche, Paris · Reading time ~10 minutes

The folder

A client once sent me a folder before our first call. Six versions of their logo, four blues, none of them quite the same. Two typefaces on the website, a third in the pitch deck, a fourth in the email signature. A photo library where half the images were warm and half were cold.

Not one of those files was badly made. Someone had done careful work on every single one of them, probably at a different moment, for a different reason, with a different brief. The client's request was simple: "We think we need a new logo."

They didn't need a new logo. They needed a system. What they were experiencing wasn't a design problem — it was the absence of a structure that could hold their decisions together over time. This is the most common brief I receive, and it almost never arrives named correctly.

A logo is a decision. A system is what lets you keep making decisions without contradicting yourself.

At Bureau Dimanche I work under a single principle: le dessein avant le dessin — the intent before the image. A system is what turns intent into something repeatable. Without one, you're not building a brand; you're accumulating artefacts.

Part One — What a design system actually is

It's a shared language, not a folder of assets

A design system is not a UI kit. It's not a Figma library. It's not a 60-page PDF that lives in a Drive folder nobody opens after launch week. It's the shared language your designers, developers, marketers and founders use to make consistent decisions without consulting each other every time.

I find it useful to think of a system in four layers, from the most abstract to the most concrete. Most systems fail because someone started at layer three.

Layer 1 — Foundations (the invariants). The things that don't move, and that everything else is built on: the colour palette with defined roles — not just "our blue," but which blue does what, and where; the typographic scale, with families, weights, sizes, line heights and the ratios between them; the spacing system, a single unit and its multiples, so every gap is a deliberate choice; and the grid.

Layer 2 — Components (the vocabulary). Buttons in every state, form elements, cards, modals, navigation, icons, and the illustration and photographic direction that sits behind them.

Layer 3 — Behaviour (the grammar). Motion principles — what moves, how fast, and why. Interaction patterns. Accessibility standards, built into the components rather than checked afterwards.

Layer 4 — Voice (the tone). Verbal identity, naming conventions, and microcopy rules: how you word an error, a confirmation, an empty state.

Almost everyone stops at layer two. The systems that actually hold are the ones where someone has decided how an error message should be worded, not merely what the error box looks like. That's the difference between a component library and a real system.

And what it isn't

Three misunderstandings I correct in almost every kick-off. It isn't a style guide — a style guide describes what has been done, a system prescribes what to do next; one is documentation, the other is infrastructure. It isn't finished — a system that isn't maintained becomes archaeology within eighteen months; it's a living object with an owner. It isn't a constraint on creativity, which is the objection I hear most, and which I'll come back to below.

Part Two — How I build one: la Méthode Archipel

Every studio has a process. Mine has a name and three movements, because I got tired of watching identity projects collapse into taste debates. An archipelago is a set of islands that share a geology: from the surface they look separate, underneath they're one formation. That's exactly what a brand system is.

1. Noyau — the core. Before a single colour is chosen, we establish what the brand actually is: its position, its promise, its non-negotiables, the two or three ideas it will defend for the next five years. This phase produces no visuals — it produces decisions. It's also the phase clients are most tempted to skip, which is precisely why so many identities feel arbitrary: they were built on a mood board instead of a conviction. If you can't finish the sentence "We are the only ones who…", you're not ready to open Illustrator.

2. Système — the system. Here the core becomes form. Typography, colour, grid, iconography, image direction — each chosen because it argues for the core, not because it looked good on Pinterest. For Maestro of IT, an IT services company, the core idea was orchestration: a technical partner who conducts rather than executes. The system that came out of it was deliberately narrow — an electric blue (#0000DB) as the single loud voice, deep navies to hold it, a warm orange (#FF7A1A) as the only permitted accent, and Inter Light throughout. One family, one weight, one accent colour. Restriction is what made it recognisable.

For Kaizō Studio, the final pairing — Sfizia with Montserrat — arrived only after we abandoned an earlier typeface that read beautifully in isolation and collapsed at small sizes across their actual templates. Systems are tested in the ugly cases, not in the hero shots.

3. Mouvement — the movement. A system that can't extend is a cage. This phase defines how the brand moves into new territory: new products, new formats, sub-brands, campaigns. When Kaizō Studio launched a second activity, Kaizō Habitat, we didn't design a new identity — we applied the existing rules to a new case. The whole exercise took a fraction of the original project because the grammar already existed. That's the compound return of a system, and it only shows up on the second use.

Part Three — Why it matters: nine returns on the same investment

I've grouped these into what a system does for your audience, for your team, and for your business — three different conversations, and you'll need all three depending on who you're convincing.

For your audience

1. Consistency builds trust. Open an app where every page uses different button styles, different fonts, different spacing. Nothing feels connected. You may not consciously register the inconsistency, but your brain does: every unfamiliar element costs a small amount of attention, and that cost accumulates. Consistency reduces cognitive load — users don't relearn the interface with each click, they feel at ease, and ease reads as competence. Competence reads as trust. This is why Apple, Google, Airbnb and Spotify invest so heavily here; their products feel familiar because every detail obeys the same rules.

2. Stronger brand recognition. Most people think recognition begins with the logo. It doesn't — it comes from repetition. Think of the brands you identify instantly: remove their logo and you'd still recognise them by their typography, their spacing, their colour, their photographic treatment, their layouts. Over time people recognise the experience before they recognise the mark, which is fortunate, because the logo appears in maybe two percent of your touchpoints and the system appears in all of them.

3. Better user experience. Users don't want to learn your interface; they want to finish a task. A consistent system creates predictable experiences — buttons behave the same, navigation stays where it was, forms follow one pattern. Less time spent decoding, more time spent doing. That's the entire job.

4. Accessibility becomes structural, not remedial. Accessibility should never be a final-stage audit. A serious system carries it inside every component: accessible colour contrast, readable type sizes, keyboard navigation, visible focus states, touch-friendly spacing, screen-reader considerations. The distinction that matters is whether accessibility is a property of the component or a checklist applied to the finished page. When it's built in at component level, every new screen is inclusive by default, and you stop fixing problems in favour of preventing them.

For your team

5. It makes teams faster. Without a system, every project restarts from zero. What size should this button be? Which blue is the right blue? How much padding looks right here? Hundreds of micro-decisions, re-litigated weekly. A system answers them once, permanently: designers move on to real user problems, developers reuse components instead of rebuilding them. Faster projects, fewer errors, less friction.

6. Easier collaboration. Design isn't made by designers alone — developers build it, marketing distributes it, writers explain it, product decides what ships. Without a shared reference, each function interprets the brand slightly differently, and each interpretation is defensible, which is what makes the arguments endless. A system replaces opinion with precedent, and discussions get shorter because the answer already exists.

7. It scales. Designing five screens is easy; designing five hundred is a different discipline. As a product grows, inconsistency grows faster than the product does: one designer adds a card variant, another builds a nearly identical button, a third introduces a new font weight for one campaign, and within a year you're maintaining eleven versions of the same component. This is design debt, and like financial debt it compounds quietly until it's the only thing you can afford to work on. A system replaces the reflex of creating a new pattern with the reflex of improving an existing one.

For your business

8. It saves money. Many companies avoid building a system because it looks expensive, but the comparison is wrong: the alternative isn't free, it's just unbilled. Without a system, teams spend thousands of hours redesigning the same components, developers rebuild identical interfaces, QA re-tests known patterns, and design reviews never end because there's no agreed standard to review against. A system is an investment that compounds — the larger the product, the higher the return.

9. It future-proofs. Products evolve, features change, teams turn over, markets shift. A system gives you a flexible foundation instead of a set of finished artefacts: you update the rule once and everything downstream inherits it. That's why the world's largest digital products run on systems rather than one-off designs, and why the second, third and tenth project always cost less than the first.

"But I'm not Airbnb"

This is the objection I get most often, and the one I care about most, because it's usually raised by exactly the businesses that would benefit fastest. Large companies build systems because they have to; small ones benefit disproportionately because they have no margin for waste.

The smallest system I've ever built was for two founders. No design department, no marketing team, no budget for a rebrand every two years. One typeface, a deliberately tight palette, a single generative idea, and a set of rules for how it lands on signage, on Instagram, on printed matter and on the door. They now produce their own communication without calling me every week — that isn't a loss for my business, that's the deliverable.

If you're a team of two, a system isn't the luxury version of a brand. It's how two people produce the visual output of a team of six, and it's why small clients almost always see the return before large ones do.

The biggest misconception: that systems kill creativity

They do the opposite, and I'd argue this quite forcefully. Creativity is a finite daily resource, and every hour spent deciding whether this padding should be 12 or 16 pixels, whether this heading should be semibold or bold, whether this blue is the blue, is an hour not spent on the problem that actually matters.

A system doesn't remove creative decisions — it moves them upstream, to where they're worth making, and then protects them. The constraint is the point: restriction is what makes a brand recognisable, while unlimited freedom is what makes everything look like everything else. The most distinctive identities I've built are the ones with the fewest permitted elements.

A system isn't about making everything look the same. It's about making everything feel connected — the difference between a collection of individual screens and a product that feels intentional. The best systems are almost invisible: nobody notices them, people just notice that everything feels easy.

What a system will not fix

I'd be selling you something if I stopped there.

A system won't fix a weak position. If you don't know what you stand for, a beautifully consistent identity will simply broadcast that emptiness more efficiently, at higher resolution, across more channels. This is the entire reason my method starts with the core and not with colour.

A system won't survive without an owner. Somebody has to arbitrate, maintain, deprecate. If that person doesn't exist, you're commissioning a document, not a system.

A system won't replace judgement. It handles the recurring eighty percent so the exceptional twenty percent gets the attention it deserves. Rules exist to be broken deliberately — which is only possible when they exist in the first place.

Do you need one? Six honest questions

Answer these about your own organisation, and be strict.

1. Are your colours used consistently across every touchpoint — website, deck, invoice, social, packaging, signage?

2. Do your buttons, cards and forms follow the same rules, or the same approximate rules?

3. Could a new designer join on Monday and ship a correct screen on Wednesday without guessing?

4. If someone asks "which blue?", is there a single answer, and does it live somewhere findable?

5. When you launched your last campaign, did you apply your identity or reinterpret it?

6. If your product doubled in size tomorrow, would your current design hold?

Scoring is simple. Five or six yeses: you have a system, look after it. Three or four: you have conventions, and conventions decay. Two or fewer: you don't need better screens, you need a better foundation.

Where to start when you have nothing

You don't need a six-month programme. You need a first honest pass.

Step 1 — Inventory. Screenshot everything you've published in the last twelve months and put it on one wall. This is the most uncomfortable and most useful hour of the whole process. Count your blues.

Step 2 — Decide the core. Not the visuals: the position. What you defend, who for, against whom. Write it in one paragraph you'd be willing to sign.

Step 3 — Set the foundations. One spacing unit, one typographic scale, a palette with defined roles rather than a list of swatches. This alone eliminates the majority of your inconsistency.

Step 4 — Build only what you actually use. Take the ten components that appear on ninety percent of your surfaces and do those properly. Ignore the rest until they exist.

Step 5 — Write the rules down and name an owner. A system without documentation is a memory; a system without an owner is a fossil.

In short

Good design solves one problem. A system solves every problem that comes after — including the ones you haven't met yet, made by people you haven't hired yet.

If you're looking at your own brand and recognising the folder I described at the top of this piece, that's not a failure. It's just the moment when accumulation has outgrown intuition, and it happens to every organisation that's actually doing things. The fix isn't a new logo. It's a structure.

Work with me

For ten years, I sat on the other side of this table.

I was a CMO in Beauty & Luxury — an industry where a brand lives or dies in the details. A shade, a serif, a silence. I was the one writing the briefs, defending the budgets, and inheriting the folders. Which means I didn't learn the cost of a missing system from a case study. I signed the invoices: agency hours spent re-explaining rules that should have been written down once, campaigns that drifted a few degrees further from the last one each quarter, decks rebuilt from nothing because nothing had been made reusable.

Then I did the thing I'd quietly wanted to do for years — I crossed over, and became the person who designs the brand rather than the one who briefs it. That's how Bureau Dimanche started: a studio where strategy comes before the pretty. Le dessein avant le dessin — the intention before the drawing.

That crossing is what you're hiring. I build systems that have to answer to two people at once: the designer working inside them every day, and the executive justifying them every quarter. Most identity work only serves the first. A system that can't be defended in a budget meeting doesn't survive one — and I've been in the room where that decision gets made, on both sides of it.

Whether it's a full identity or a single interface, the test is the same. Not does this look good, but does this work, does it mean something, and does it make the decision effortless for the person on the other end.

→ My method — how a project actually runs, phase by phase → Selected work — Maestro of IT, Kaizō Studio, and others → Start a conversation — no brief required. A folder is enough.

Anne Wonner spent a decade as a CMO in Beauty & Luxury before founding Bureau Dimanche — the Sunday office, named for the day ideas get to stretch, wander and daydream a little before showing up sharp on Monday. Calm thinking, sharp design. Made in Paris, at home anywhere.