Skip to content

About

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.

20+

Years in the field

50+

Design systems shipped

10+

Teams coached

4

Enterprise products

Questions people ask me

What this site is

This site is a practical hub for high-signal AI and design systems work. It is built to make the best ideas easy to access and to show what it looks like in practice.

  • Share top-tier AI and design systems content.
  • Promote services and make booking simple.
  • Collect creative and business endeavors in one place — including Digitaltableteur and VertaaUX.

What I do

Design systems leadership

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 workflow acceleration

Automate repetitive work without sacrificing craft, accessibility, or maintainability.

The stack I ship

Practical tools that get results. No tool religion — whatever ships quality fastest.

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 actually flow

From brand guidelines to adopted components. The loop that makes systems compound over time.

The workflow shows how brand guidelines connect to design tokens. Design tokens split into Figma variables and code tokens. Both feed into the component library, which produces documentation and Storybook. Documentation and Storybook drive adoption. Adoption feeds back into governance, completing the loop.

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

Tokens, specs, examples and working components beat slide decks.

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

Baked in from the start or you'll pay 10x later.

If you only read one thing

Ready to talk?

30-minute discovery call. No pitch. Just friendly banter and problem-solving.

Get in touch