The tools I use most for systems and product work.
Hey, I'm Simon
I build design systems that product teams and AI tools build with.
Staff product designer in Seattle. Design systems at Thinkific and Anywhere Real Estate, payments at Amazon Prime, and Android at Samsung.
I design for the next ten use cases, not just the first. I ask who else will need it and what will change, because a pattern that holds up across teams, brands, and platforms is worth more than a one-off screen.
Scalability
I communicate early, so people know what’s happening before they have to ask. I give them clear choices and just enough information to decide, so they never have to wonder whether they can trust the product. I put extra care into failure states and edge cases, because that’s where trust is won or lost.
Clarity builds trust
Consistency gets harder with every team that ships. I protect it through process as much as design: shared tokens, clear contribution rules, and review before release. When patterns behave the same everywhere, people only learn a product once.
Consistency
When a team is stuck on opinions, I bring in research. A small test often settles what a week of debate can’t, and I’m clear about what the data doesn’t show.
Data drives decisions
Design principles
When I'm not working
Where I've been
My toolkit
Four principles shape how I work, whether I'm building a component or a checkout flow.
Click or scroll while hovering over the component :)