About me

I was trained as an architect before becoming a product designer, and I still approach design the same way today. Whether I'm designing a product, a workflow, or an AI interaction pattern, I start by understanding how the whole system works before designing individual pieces.

I believe good design happens where business goals, user needs, and engineering constraints meet. The best products aren't just intuitive to use. They're practical to build, accessible by default, and designed to evolve without losing quality.

Architecture taught me that the hardest design problems are rarely about individual elements; they're about understanding how everything fits together. That's the mindset I bring to product design today. I enjoy bringing clarity to messy, ambiguous problems by uncovering the relationships between people, technology, and business goals before designing solutions.

The image on the left is from my master's thesis in architecture. Although I design software today, the way I think hasn't changed. The medium has changed from buildings to digital products, but the mindset is the same.