design system — Parma, Italia

Design system consulting in Parma: audits, governance and component libraries

If your product has grown, its interface has grown with it: buttons that differ from screen to screen, three shades of the same green, a component rebuilt for every new page. A design system fixes that once, at the root.

who this is for

what an audit covers

ranges

Ranges, not a quote: it depends on how many components, how many platforms and how much of the old interface has to be migrated. The audit comes first, and it is the part that tells us whether the rest is worth doing.

what is not included

how it works

  1. 1. Audit: Two weeks: inventory, token drift, the three places where the interface hurts most.
  2. 2. Decision: We agree what the system covers and what stays out. A system that tries to cover everything is adopted by nobody.
  3. 3. Library: Figma and code, built together, so the two cannot drift.
  4. 4. Governance: Naming, review and retirement rules, written down and short enough to be read.

measured, not promised

This site runs on its own design system: one token set drives every theme, and the build fails if any of the 50 contrast checks regresses. That is the standard I hold a client system to.

Why a design system and not a style guide

A style guide in a PDF is read by nobody. A design system lives where the work happens: in Figma and in the code, with the same names on both sides.

The cost is not building it, it is maintaining it. That is why governance comes before the library: who adds a component, how it is named, when it is retired. Without those rules the library drifts back to where you started.

A system nobody adopts is a folder. It is measured in components reused, not in components created — and that number is visible in the code, not in a slide.

questions

We already have a component library. Is that a design system?

Not yet. A library is the parts; a system is the parts plus the rules for adding, naming and retiring them. Without the rules, the library drifts back to where you started.

Do we need Figma and code?

If designers and developers both work on the product, yes. A Figma-only system is a picture of a system, and it diverges from the code the first week.

How long before we see something?

The audit takes two weeks. The first components land in the third. The full library depends on size: a small product is a month, a large one is a quarter.

What if the team does not adopt it?

That is the real risk, and it is why governance is part of the work, not an appendix. A system nobody uses is a folder.

How much does a design system cost?

The audit starts at EUR 1,200, a Figma library at EUR 2,500, the React library at EUR 3,500. The audit comes first because it tells you whether the rest is worth doing.

Where do we start?

With the inventory: what components exist, which ones duplicate each other, which ones nobody uses. Two weeks, and you have a list you can act on even without the rest of the project.

Start with the audit

The audit is the part that tells you whether a design system is worth it. If it is not, I will say so.

Request an audit