Senior Product Designer. Can’t leave the code alone.
Nine years across fintech, banking, and B2B SaaS — now mostly designing and building AI products at Enable. For me, building means prototyping in real code to get an idea closer to the real thing, and shipping the occasional production fix — engineers take it the rest of the way. Built this site (and native apps for Mac and iOS) the same way.
Recent projects designing decision tools, AI surfaces, and analytics for commercial teams.
A few principles that shape how I design and build.
Reducing complexity is the complexity.
The hardest part of designing for technical products isn't the interface — it's making the underlying system legible. Most ‘simple’ designs hide complexity that has to surface eventually.
I build what I design.
I take ideas to working products with AI tools like Claude Code — real prototypes in real code, pushed to GitHub and deployed. Engineers implement from something they can click, not guess at, and the design gets pressure-tested as a product, not screens.
You can't design trust — you earn it.
Especially with AI. Users don't reject AI — they reject AI they can't verify. So I make the system checkable: show the math, the source, the lifecycle, the confidence.
Research closes the loop.
Customer sessions, prototype testing, observed behaviour — the work product isn't the artifact, it's a closer reading of the problem. Ship the design that earned that reading.
Let's build the real thing.
If you're building products people need to trust — or want a designer who can take an idea all the way to a working product — let's talk.