← All work

Case study · Cerved · 2022–now

Cerved Design System

Cerved's products had grown apart, each solving the same problems in its own way. I created the design system that brings them back together, from the tokens behind a single colour to the structure of a data-heavy page.

Role
Design system lead: created it, and its sole owner today
Worked with
A designer colleague early on; IT on feasibility
Deliverables
Tokens, Figma library, component specs, layout guidelines, contribution process
Scope
40 components, 6 page layouts; dark by default, plus light and white-label themes for banking clients
A portfolio dashboard in the default dark theme, built with the design system: summary cards, a revenue-by-sector table and a risk distribution card.

The problem

Each product had its own interface. Designers kept re-solving the same layouts and interactions, and users met a different experience in every tool.

What I did

Audited existing patterns, defined the token architecture, designed the component library, documented page layouts and set up how changes get proposed and released.

The result

The whole design team, about 10 designers, starts from one library instead of rebuilding or copy-pasting from old projects. The system became the base for the accessibility work and the AI kit.

01 · Context

Many products, many answers to the same question

Cerved builds data-intensive B2B products: company archives, risk assessments, dashboards full of tables and filters. Over time each product had developed its own interface conventions.

The result was duplicated effort for designers, who either rebuilt search, selection and table patterns from scratch or copy-pasted them from other projects, and inconsistency for users, who often work across several of these tools.

02 · Approach

From recurring patterns to shared rules

1. Audit what already existed

I compared how each product handled recurring tasks (searching, selecting, triggering actions) to decide what belonged in the shared library and which real differences the components had to support.

2. Build a token architecture first

I defined a token taxonomy that separates what a value means from what it looks like. Components only reference semantic tokens, so a theme is just a different set of values: light, dark and the white-label themes for banking clients run on the exact same components.

Cerved's products are dark by default, with light as a complete alternative. Dark is the harder theme to get right, especially for contrast and elevation, so both themes are checked pair by pair.

PrimitiveHSL palettes. Colours in the same family share hue and saturation and differ only in lightness.
SemanticMeaning, not appearance: color-on-surface-high-emphasis is #263873 in light and #e1e3ea in dark.
ComponentButton, Card, DataTable… reference semantic tokens only, so every theme reuses the same components.
Token architecture. A theme is a different set of values, never a different set of components.
The same card, buttons and search field in three themes: dark (default), light and a violet white-label client theme.
One set of components, three themes: dark (default), light and a white-label client theme.

3. Specify components and how to choose them

For each component I defined anatomy, variants and states and, just as important, when to use which variant. That guidance is what stops a library from turning into a menu of options.

Button specimen in the dark theme: contained, outlined and text buttons, each shown default, with an icon and disabled.
Button variants by emphasis, with icon and disabled states.

4. Define how components form a page

Components alone don't make consistent products. I documented page layouts: where navigation, headers and content go, and how they scroll. In an archive, the table is the workspace. In a dashboard (above), the same table sits inside a card next to summary metrics. On an entity page, cards and data blocks organise everything about one company.

A company archive in the light theme: navigation, header and a data table.
Archive: the table is the workspace.
A company page in the light theme: header with status and actions, sub-page navigation, key figures, registry data and risk.
Entity: one company, organised in cards.

5. Make it sustainable

I validated feasibility with IT while building the system, published the Figma library and guidelines, and defined contribution standards for how changes are proposed, reviewed and released.

03 · Key decisions

Where I drew the lines

Extend the tokens, keep the components

Client and product themes change token values only, never component structure.

WhyOne set of components to maintain, test and make accessible, no matter how many brands it serves.

Layouts are part of the system

I documented page patterns (archive, dashboard, entity detail, wizard) alongside components.

WhyMost inconsistency between products came from how pieces were assembled, not from the pieces themselves.

Usage rules over visual specs

Every component guide starts with when to use it, not how it looks.

WhyVisual specs tell you how to draw a button. Usage rules tell you which button. That's where products diverge.

04 · Outcome

A foundation other work builds on

  • Faster screens: designers start from established layouts instead of a blank canvas or an old file.
  • Consistent behaviour: recurring interactions work the same across products.
  • Theming without forks: dark (the default), light and white-label client themes share one library.
  • A platform for what came next: the system made the accessibility work and the AI prototyping kit possible.

What I learned

A design system succeeds on adoption, not on the size of its library. The time spent on documentation and on a clear contribution process paid back more than any single component.

Building or scaling a design system?

I'd be glad to talk about how this one was built and rolled out.

hello@mauriziocarlini.com