About

I lead product design for transportation and logistics software, working at the intersection of dispatch, carrier management, and exception handling — the parts of the supply chain where a bad interface costs someone real time, real money, or a missed pickup. My focus over the last few years has been turning operationally dense, alert-heavy workflows into interfaces a dispatcher can trust at a glance, even when the underlying data is messy.

Lately most of my work sits at the edge of AI-augmented product design: figuring out where a model’s suggestion belongs in a human’s workflow, how much control to hand over, and how to design for the moments a system is wrong. I care less about AI as a feature and more about AI as an interaction pattern — how confidence, uncertainty, and override paths get surfaced in the interface so operators stay in control instead of getting steamrolled by automation.

My process leans on systems thinking — mapping the full workflow before touching a single screen, then designing components that hold up across edge cases instead of just the happy path. I prototype in code almost as often as in Figma, partly because transportation software rewards fast iteration and partly because real interactions surface real problems faster than static comps do.

Outside of shipped work, I spend time building small experiments — the kind you can click around in this playground — as a way of testing new interaction ideas before they show up in production. If you’re working on similarly gnarly operational problems, I’d like to hear about it.