I became a designer because I wanted to understand things.
I didn't plan to work in design. I got curious about how systems touched people's lives and how small changes could remove friction. That curiosity turned into a career.
Today, I design products for complex, real-world operations—helping teams make sense of the messy so they can do their best work.
User Manual
TODO: one line on how to work with you.
- ▸I'm brought in early enough to shape the problem.
- ▸The problem is complex and the stakes are real.
- ▸There's trust, candor, and room to think.
- ▸We talk to users. A lot.
- ▸Decisions are made without evidence.
- ▸Speed is prioritized over learning.
- ▸Design is treated like decoration.
- ▸"What problem are we actually solving?"
- ▸"How do users do this today?"
- ▸"What happens when this fails?"
- ▸"How will we know if this worked?"
- ▸Cognitive load
- ▸Broken workflows
- ▸Naming inconsistencies
- ▸Missing feedback loops
- ▸Edge cases
- ▸Turning chaos into clarity
- ▸Building systems that scale
- ▸Collaborating with sharp, kind humans
- ▸Shipping work I'm proud of
Great work happens when we combine empathy, curiosity, and a bias for action.
Questions I'm often asked
Thoughts on design, leadership, and everything in between.
A good design leader creates clarity and trust. They help teams align on the right problems, make space for great thinking, and remove blockers so the team can do their best work. They invest in people, set a high bar, and lead with humility. They know when to zoom out, when to get into the details, and when to shut up and listen. And ultimately, they design the conditions for the team—not just the product.
Leadership isn't about having all the answers. It's about creating the environment where the right answers can emerge.
Writing on design & beyond
I write when I'm thinking out loud. About systems, product design, motivation, and the messy in between.
Read on SubstackAway from my desk
A few of the things that inspire, reset, and fuel me.
