Design System
A design system and UI that hold your product together
As a product grows, screens, components, and the people working on it multiply. Without clear rules, the interface becomes inconsistent, design and development drift apart, and every new change costs more time than it should.
I help design and grow UI and design systems that unify the product, speed up design and development work, and give the team a shared foundation to keep growing on.
Who it's for
When a design system makes sense
Your product is becoming inconsistent
The same elements look or behave differently in different places. Components get rebuilt from scratch, and the team gradually loses track of what's actually correct.
Design and development are drifting apart
One version of a component exists in Figma, another in production — and every change re-litigates the same details.
Your product is growing fast
New features, screens, or teams keep appearing, and you need a system that lets the product grow without design and technical debt growing with every change.
What we can work on
A design system isn't just a button library. I set up rules that make sense for designers, developers, and the product itself.
wireframes and prototypes for key UI screens
conversion landing pages and new product screens
an audit of the current UI and components
unifying visual and interaction patterns
a UI component library in Figma
variants, properties and component states
design tokens and Figma Variables
colours, typography, spacing and other foundations
responsive component behaviour
documentation and usage guidelines
connecting design with Storybook
visual review through Chromatic
handoff and collaboration with the dev team
Design QA during implementation
Tools I work with
FigmaFigma Variables
Storybook
Chromatic
React
GitLabHow does the collaboration work?
Four steps from the first call to handoff-ready documentation for development.
.01
We clarify the problem
We define what the product needs to change, who we're building it for, and how we'll measure success.
.02
I map the path to a solution
I analyse the current state and real scenarios. I design a logical structure and the first prototypes.
.03
I finish the interface
I build the final, functional UI, including components, responsiveness and all the states that matter.
.04
From production to DesignOps
I prepare a clean handoff for development and personally check the implementation matches the design.
Frequently asked questions
It depends on the product's scope and what already exists — after an initial call you'll get a concrete estimate.
Need to unify your UI or move your design system forward?
Whether your design system is just getting started, or you have a component library that can no longer keep up with your product, we can start by looking at the current state and figuring out what's worth tackling first.
Talk about your design system