I design products
and the systems
behind them
I help product organisations ship consistent, scalable, multi-brand experiences faster, without losing quality or autonomy, by building the systems and working models teams actually adopt.
Now making those systems readable by AI agents as well as people.
Selected work
Each piece opens into a full case study: the decisions, the trade-offs, and what I’d do differently.
FanDuel / 2024–25 / Systems, leadership
Design system alignment program
5
verticals aligned
20+
CONSUMER designers
3
embedded specialists
1
DESIGN SYSTEM
Scaling trust, not just components. Three embedded specialists, twenty-plus designers, and one adoption goal.
Read case studyFanDuel / 2026 / Systems, AI
The system becomes shared AI infrastructure
FanDuel / 2022 / Systems
Token-powered colour system
News UK / 2021–22 / Product
One account,
multiple brands
Settings, subscriptions and notifications designed once, served across every masthead on NewsKit.
Nutmeg / 2019–20 / Product
Mobile onboarding and native investing
New investment journeys from concept to launch, and dark mode foundations across iOS and Android.
Systems work is people work in disguise
I’ve managed a team, and I still do my best work in the weeds, next to the people I’m building with.
About Me- 01
I’m the first to step in, and stay until it’s done
I captained American football teams for years and the habit stuck. I’d rather be in the files with you than drawing arrows in the air from above.
- 02
I learn by making things
I’m curious and restless. I build a rough answer, put it in front of people, and keep going until it’s actually better, not just new. I’m happy to be told when it isn’t.
- 03
I’ll do the dishes
Making things simple is complicated. I take on the complexity so the people using the work don’t have to.
- 04
I own the miss, and keep my head up
When something doesn’t land, I say so and learn what to do differently next time. When the miss is my team’s, I take my part and own that too.
Thinking forwards
Design systems for people and machines
Component libraries that only serve humans are a dead end. The next generation needs structured metadata, MCP infrastructure and documentation written for LLMs as much as for people.
- 01
Systems as infrastructure
A design system isn’t a component library. It’s load-bearing infrastructure: tokens, semantics, and governance matter more than pixel pushing.
- 02
AI-native documentation
The new player is already in the room. Components carry structured metadata, so the system speaks to both humans and agents.
- 03
Token-first design ops
Tokens as the single source of truth across tools, brands, and platforms, with MCP as the routing layer between design intent and engineering output.
Let's
talk
Open to conversations about design systems, product craft, and what good design infrastructure looks like in practice. If you're building something great and thinking about how it scales, let's talk about it.