About
Turns out I've been organizing systems since I was young. Categorizing, structuring, finding patterns. Design systems turned out to be the professional version of that same instinct.
Questions people ask me
What this site is
This site holds my thinking and the work behind it: case studies with their numbers and sources, essays, talks, and the templates I use with clients. Client engagements run through my consultancy, Digitaltableteur (opens in a new tab)My founder-led consultancy for complex digital products: product design, design systems, AI workflows, brand and engineering. I lead every engagement and bring in specialists from a trusted network when the work needs them. The full project archive, brand and illustration included, lives there., which also keeps the full project archive, brand and illustration work included. I also build VertaaUX (opens in a new tab)VertaaUX scans your live product for automatically detectable WCAG 2.2 issues, generates fix-ready reports and tracks them over time, so manual testing can focus on what tools cannot judge., an automated accessibility audit service.
What I do
Design systems
Align design + engineering, define component contracts, ship governance that doesn't kill velocity.
Enterprise UX shipping
Reduce drift, reduce friction, increase consistency across teams and platforms.
AI and design work
How agents change the way products get designed and built. I write and speak about it here; hands-on AI workflow projects run through Digitaltableteur.
Advisory
I take a small number of design system engagements alongside talks and workshops. Every engagement ends with something your team can use: tokens, specs, components. I don't deliver slide decks. Engagements are contracted through Digitaltableteur, which is also where AI workflow projects and larger builds are scoped.
Design system foundations
Tokens, component contracts and documentation that design and engineering both build on.
Governance and adoption
How the system is decided, released, retired and taken up by product teams.
Design and code alignment
One set of names, contracts and handoff rules across Figma, code and Storybook.
Advisory
Ongoing decisions, reviews and coaching for the people who run the system.
The stack I ship
The tools I use today. I switch when something better turns up.
Design Systems
- Figma
- Tokens Studio
- Style Dictionary
- Storybook
Frontend
- React
- Next.js
- TypeScript
- Tailwind CSS
AI Tooling
- Cursor
- Claude
- GitHub Copilot
- v0
Testing & QA
- Playwright
- Chromatic
- axe-core
- Lighthouse
How design systems flow
From brand guidelines to adopted components. The loop that makes systems compound over time.
How I work
Outcome-first
Define what changes (and how you'll know).
Decision records
Big choices are documented, testable, reversible when possible.
Artifacts over opinions
I hand over tokens, specs, examples and working components.
Adoption as a product
Docs, contribution model and feedback loops are part of the system.
What I don't do
Design system theater
A library without governance isn't a system.
Static handoff workflows
Figma frames don't ship. Code does.
Late-stage accessibility
Fixes found late cost more than fixes built in.
If you only read one thing
Ready to talk?
Thirty minutes on your situation. You describe the problem; I tell you whether I can help and what it would take.