What color of blue is it, really?
A new campaign is being created and someone asks if there are any graphic elements to use as a starting point. At the same time, the website is being updated, but which blue color really applies – the one from the latest presentation, the one on the site, or the one the brand manual from 2019 says?
Someone is frantically searching for the component library. Someone else is trying to understand why the same button looks different on two pages. A third person is building an ad from scratch – again – even though similar material was produced just three weeks ago.
Nobody makes mistakes. Everyone tries. But everyone starts from different versions of the "truth".
Do you recognize yourself? Then you are definitely not alone. And what is missing has a name: design system.
What is a design system – and what is it not?
Let's start with what it's not : it's not a PDF of logo rules that no one can find. Nor is it just a collection of color codes that some designer saved in a document three years ago.
A design system is a living, shared framework that brings together all the building blocks you need to express your brand consistently across digital environments. Think of it like a perfectly curated wardrobe – everything has a place, everything matches, and anyone on the team can put together something that looks thoughtful, without having to ask what goes together.
What is typically included?
The visual basics: Color palette with precise color codes, typography with clear rules for hierarchy, logo with usage rules and free zones, and guidelines for image style.
Components: Buttons, forms, menus, cards, and other pre-built parts that can be reused – defined in different states and responsive variants.
Principles and guidelines: Design principles that guide decisions, accessibility guidelines, and sometimes even tonality and copy guidelines.
Code (in more advanced systems): Ready-made code components that developers can use directly, with documentation that connects design to implementation.
The important thing to understand? A design system is not a project with a start and an end. It is a living product that grows with your organization.
Why you as a marketing manager should care
"Design sounds like the designer's job" – and yes, the designer is central to building the system. But the impact is felt far beyond the design department. It's felt in your everyday life.
Without a design system
Monday: Market needs a landing page for an upcoming campaign. The designer starts from scratch – looking up color codes, fonts and image styles from the previous project. Finds three versions. Chooses the one that looks most current.
Tuesday: The developer gets the design. Some of the components look like the ones already on the site – but not quite. The developer builds new variants. This takes extra time.
Wednesday: At the same time, a colleague in marketing is creating advertising material in Canva. The person is using the colors in Canva's branding kit, but they don't quite match what the designer used. No one notices it right now.
Thursday: The CEO sees the landing page and wonders why the buttons look different compared to the rest of the site. The designer explains. A retake is done.
Friday: The campaign launches. It looks okay, but it took three times as long as it should. And if you look closely, the ad, landing page, and website look like they come from three different companies.
No individual did anything wrong. The system failed them.
With a design system
The designer opens the design system, selects existing components, and puts the page together in a morning. The developer assembles – not builds – because the components are already in code. Marketing creates creative with the right colors, templates, and guidelines. Everything is connected. The campaign launches in half the time and looks like part of the same brand regardless of channel.
Five reasons to care – from a business perspective
1. Time is money – and you save plenty of both
With a design system, the building blocks are already in place. The designer designs faster. The developer builds faster. The market produces faster. That may not sound dramatic in a single project, but multiply it by all projects over a year and it becomes very noticeable.
2. Consistent experience builds trust
Think about the brands you trust the most. Regardless of the channel, it feels like the same company. It doesn't happen by itself, it happens because they have a system. When your expression varies depending on who produced the material, recognition disappears. And recognition is a prerequisite for trust.
3. Onboarding and collaboration become easier
Without a design system: long onboarding, lots of questions, lots of "this is how we usually do it" that is never documented. With a design system: "Here's the system. This is how we work. Go ahead." Especially valuable if you work with external partners such as agencies, freelancers or other teams.
4. You can scale without losing control
The more channels, campaigns and teams you add, the harder it becomes to keep the whole thing together. A design system gives you the opportunity to grow without the expression spreading. More hands can work in parallel without the quality dropping.
5. It protects the investment in your brand
You've invested time, energy and money into your visual identity. Without a system that ensures it's managed consistently, it slowly erodes. Not through one big disaster, but through a thousand small deviations that together cause the brand to lose focus.
"Do we really need it?" – Three levels to choose from
Not everyone needs a full-scale design system. The level of ambition should match where you are.
Level 1: Visual guidelines (basic level)
Documented colors, fonts, logo rules and image style. No coded components – but a clear visual reference that everyone can use.
Suitable for you if you are a smaller team, lack documented guidelines and want to create order without making it a large project. In practice: a well-structured document or a shared Figma file. Takes days to set up, not months.
Level 2: Component Library (Intermediate Level)
In addition to the visual guidelines, there are pre-built design components that designers can use directly – defined in different states and responsive variants.
Suitable for you if you regularly produce digital material, multiple people create design or content, you work with external partners or you have experienced inconsistency between pages and channels.
Level 3: Full-scale design system (advanced level)
Design and code live together. Each design component is also available as a ready-made code component. The system includes documentation, principles, accessibility guidelines and often even tone.
Suitable for you if you have a complex digital presence with multiple sites or platforms, design and development teams work in parallel, or you scale quickly and need the single source of truth for all digital expressions.
Recognize your situation
Most companies we meet are somewhere between level 1 and 2. They have something – but it’s not really connected, it’s not up to date, and it’s not being used consistently. That’s perfectly normal. And the most important step is not to build a perfect system – but to start.
How do you create a design system?
Here is the practical process – adapted to reality, not the textbook.
1. Take inventory of what is available. Go through the site and collect all the unique variations of buttons, forms, colors, and other elements. You'll probably find five variations of the "primary button" and three shades of "our blue." That's not a failure—it's the starting point.
2. Choose what should be common. Not everything needs to be there from day one. Start with what is used most and creates the most friction: color palette, typography, buttons, form fields, and spacing. That's the core. The rest is added gradually.
3. Design, document and anchor. Each component is designed in its variants and documented with clear rules: when to use it, where to place it and why it looks the way it does. But just as important – involve designers, developers and the market already during creation. Appoint an owner. Make it easy to find. Otherwise it will collect dust.
4. Maintenance as a product. The design system is never "finished." New components are added, old ones are phased out, guidelines are adjusted. Treat it like a product with its own roadmap—not a one-time project.
Common objections and honest answers
- "We are too small for a design system."
Maybe – but you are never too young for visual guidelines (level 1). It is easier and cheaper to start early than to clean up afterwards. - "That sounds expensive."
The initial work costs money – but think of all the hours spent on rework, duplication and “which variant should I use?” questions. Those hours cost money too – they just don’t show up on an invoice. - "Our team won't use it anyway."
Justified concern. But it all depends on how it is introduced. A system that is thrown over the wall without involvement – no, it will not be used. A system that is built with the teams and solves their problems – it becomes a natural part of everyday life. - "We have a brand manual."
Good – that’s a start. But a brand manual describes what the brand is. The design system provides the tools to build it consistently in digital environments. One tells the story. The other enables.
Do you want to get started?
At Mild, we live in the intersection of design, technology, and strategy, every day. We build design systems that don't just look good in a Figma file, but actually work in the real world. From visual guidelines to full-scale systems with code libraries, we always start with your needs in mind.
Whether you want to build from scratch, structure what you already have, or just brainstorm – get in touch.
