Carlsberg Group's digital products were being built brand by brand and market by market, each team rebuilding the same dropdown, the same table, the same nav pattern from scratch. Malty was the fix: a single design system meant to give every team a shared language instead of duplicated work, so product delivery could scale without design and engineering re-solving the same problems every time.

I led the definition of the system's structure, component logic and governance model, working closely with designers and developers across markets. That meant thinking beyond a component library: tokens, documentation, and contribution workflows all had to work together so teams could actually adopt the system and evolve it themselves, not just borrow assets from it once. The real test of a design system isn't whether it looks complete, it's whether other teams choose to build on top of it instead of around it.

- Malty is live and in production, not a reference system sitting unused, teams are shipping real product on it.

- Carl's Shop runs on Malty across four markets, Denmark, Norway, Laos and Russia, proving the system holds up across genuinely different market contexts, not just one flagship team.

- Skillable, a separate Carlsberg product, also adopted Malty, the clearest signal a design system can get: teams outside the one that built it chose to use it instead of building their own.

- Malty documents 42 components across forms, navigation, cards, overlays and more, with the majority already production-released and the rest openly tracked, not hidden, as known issues. It's a live, governed system, not a one-time deliverable.