I design software for people whose job depends on it.
That's the through-line of my work. Not the apps people open twice a month, but the platforms dispatchers, drivers and analysts live inside for eight hours a day. The apps where a badly placed field costs real money and a confusing state costs somebody their whole afternoon. I find that kind of problem genuinely fun (which I realize says something about me).
I came to product design from graphic design and web programming, made it official through DesignLab's UX Academy, and have been practicing professionally since 2019; first at Mathison and breathing.ai, then AT&T's consumer mobile apps, and then for four and a half years owning WM's internal tools suite. These days I design for client AI products at Koi Studios.
The technical background still earns its keep. I'm comfortable in the constraints engineers actually live with, and I'd rather hear "that's too expensive" early than defend a beautiful spec that quietly dies in sprint planning.
Start at the business consequence
Before I even open Figma I want to know what this costs the company today and which number moves later if we fix it. It makes prioritization arguments short, and it means the case study writes itself later.
Design for the exception
In operational software, the happy path is the easy 20%. The real value is in the truck that broke down, the route that overran, or the model that guessed wrong, so that's where I spend my time.
Treat adoption as part of the design
A tool nobody trusts is a tool nobody opens. Let's see some test rollouts, pilot markets, override rates, and office hours. The rollout plan is a design artifact, and I'm happy to be the one who writes it.
Be the easiest person on the project
Ego has left the chat. I'd rather bring engineering in early and lose a round on the whiteboard than win it and watch the build fall apart later. Being pleasant to work with isn't just some soft skill, it's how good work survives.
Keep a little levity in the room
Enterprise software IS serious, but every meeting about enterprise software doesn't have to be. A well-timed dad joke has gotten me more honest feedback than a perfectly structured critique ever has.
Leave the team better than I found it
Whether it's mentoring designers, documenting decisions, or building contribution models. I've been the only designer on a huge suite of products, and the only way that works is by making the system carry the load.
Figma · Claude Design · FigJam · Sketch · ProtoPie · Maze · LogRocket · Photoshop · Illustrator
I studied music production before I found design, and I still write and record. It’s often the same instinct in a different medium: a lot of meticulous structure underneath something that ends up feeling effortless.