Back
Halden
B2B SaaS, Design system
One design system for five teams
Halden’s analytics platform had five teams and five ways to build a table. I led the system that unified them.
Role
Design System Lead
Team
3 designers, 2 front-end engineers
Timeline
9 months
Tools
Figma, Storybook, Zeroheight

(The problem)
Halden grew through two acquisitions and ended up with three component libraries and no shared rules. The same filter looked different on every screen, and engineers rebuilt basic UI for each feature.
Design reviews were spent debating spacing instead of solving customer problems.
(The solution)
The system now covers 64 components and powers every new screen at Halden. Contribution is open, with a weekly review where any team can propose changes.


(Process)
I audited 240 screens and grouped every pattern by job, not by look. We agreed on foundations first: tokens for color, type, and spacing that both design and code could read.
Each component shipped with usage guidance, a Figma version, and a coded version in Storybook. Teams adopted it one surface at a time instead of in one big migration.
Results
64
Components in one shared library
3x
Faster delivery for new features
92%
Of product screens on the system
(Client testimonial)
“Working with Elias changed how our engineers think about design. The system he led saved us months, and he was in every code review asking how to make things easier to build.”

Jonas Weber
Engineering Lead,
Halden

Let’s talk

