The work is complicated. The product shouldn't feel that way.

I've spent most of my career trying to understand how things work. That curiosity has sent me wandering through photography, consulting, fintech, enterprise software, developer tools, and lately AI-assisted products. Not all those who wander are lost, but they do come away with an odd, useful toolkit: photography taught me to look, consulting taught me to listen, and the rest taught me that the hardest problems are rarely where people expect them.

One question threads through all of it: when the work behind a product is genuinely complicated, how do you keep the product itself from feeling that way? I spend most of my time understanding systems before I design anything. How people decide, how teams collaborate, how products grow, and where complexity quietly gets in the way.

I think often about the bridge of a starship: an impossibly complex machine reduced to a handful of calm controls and a clear view of where you are going. That is the bar I hold for the products I work on, understandable even when the machinery underneath is anything but simple.

The other thing I love about that bridge is the crew. The work stays pointed at the problem. People keep their egos out of it and stay objective, they lean on each other's strengths rather than siloing what they know, and they treat every new situation as something to learn from. That collaborative, always-learning way of solving problems is how I try to work.

Today I'm a Staff Product Designer at Moderne, working on developer experiences, documentation systems, and AI-powered workflows for enterprise engineering teams. Before Moderne, I led platform strategy at BNY Pershing X and helped organizations navigate digital transformation at VMware Tanzu Labs.

The problems I'm drawn to rarely fit into a single discipline. They sit between product strategy, information architecture, systems thinking, and design. What I'm good at is making sense of the messy middle: getting a team pointed the same way and turning a complicated idea into something people can actually use.

Lately I've spent most of my time on how AI is changing the way software gets built, and what design's job is in guiding and governing those systems.