How I work 🧠 📐 Over the years, I’ve learned that strong product design rarely comes from a single big idea. It usually comes from understanding the problem well, relying on familiar and proven patterns, and shaping experiences that stay clear for users while supporting business goals and technical reality.

1. What I optimize for

When I work on a product, I look beyond the happy path. I pay attention to how flows connect, where users might lose context, and how the experience holds up in empty states, errors, and moments of ambiguity. My goal is to make sure users always understand where they are, what is happening, and what they can do next.

2. How I make decisions

My process is practical and rooted in discovery. I start by using existing patterns, product context, and user behavior to frame the problem clearly, then map the core flows and test the weak points across the journey. I focus on solutions that feel intuitive, realistic to build, and resilient once they reach production.

3. How I work with teams

I work closely with product and engineering from the start, because the best decisions usually come from shared understanding early on. That includes not only the main journey, but also fallback paths, system messages, transitions, and the small product details that make an experience feel coherent and reliable.

4. How I use AI

I use AI as a thinking and testing partner throughout the design process. It helps me explore alternative flows, surface overlooked edge cases, pressure-test unlikely scenarios, and create faster prototype variations in Figma before the team invests too much in one direction. I see it as a way to expand reflection and speed, while keeping judgment, prioritisation, and product quality firmly human.