Projects

I care about process. Every project I work on has one, and I lean on it to keep things clear, for me and for the team. What changes is its shape. Some projects needed weeks of research before a single screen existed, while others needed a working prototype by Friday. So instead of running the same playbook every time, I adapt to the context, the constraints, and what the team actually needs.

What doesn't change is how I start: with a lot of questions, long before opening Figma. For me, everything in product design depends on making sure we're solving the right problem, and that often means listening for what people don't say. While the answer isn't there yet, I go looking for it by talking to people, digging through data, or testing a rough prototype, whatever gets me closer to clarity.

Curiosity keeps that search moving. I'm always poking at something new, whether it's a tool, a framework, or a rabbit hole, and I'm quick to figure out which of those is actually useful right now. AI has been part of my daily work for the last two years, but as an assistant. The thinking still happens with pen and paper.

In the end, every version of my process shares the same core: communication. Product design is a wide umbrella that covers interaction, visual craft, and systems thinking, but most of the job is translating between business, engineering, and the people who'll actually use the product. That's why my process works best in a team that builds close together, where design is part of the conversation from the start, not brought in at the end.