a few words

I started in mathematics and computer science. That's probably why I'm drawn to the products most designers route around: dense data, several user roles, and people who understand their work far better than any tool does. My job isn't to simplify what they know. It's to make the software keep up with it.

Design came later, and I'd spent years in it before co-founding an agency. It grew to fifteen people and it worked — the kind of business you're supposed to want. A few years in, I left it anyway, for something harder to measure. Agency work hands the design off and moves on; you almost never see what a decision does six months later. I wanted to stay long enough to be wrong about something and fix it. So for the last six years I've been the only designer on one live B2B product, owning it end to end.

Across all of it, the domain varies far more than the work. Clinicians ordering diagnostics, credit analysts weighing risk, sales teams running outreach, research teams sharing data, fleet managers tracking vehicles, people filing government reports — each has its own language and constraints, but the way I approach it barely changes: understand how an expert actually decides, then build software that carries that judgment without getting in the way of it or pretending to replace it.

What I want next is another problem worth staying on — something complex enough that getting it right matters, with people who'd rather solve it together than pass it down the line. If that's what you're building, I'd be glad to talk.

Request CV↗