How I Design

1. Understand the problem

I ask the sometimes annoying questions first: who is struggling, what the business needs, and what the existing product or technology can support.

2. Find the opportunity

I turn conversations, research, and product data into patterns, journeys, and a focused set of problems worth solving.

3. Define the path

I map task flows and information architecture, then align with PMs and engineers on scope, feasibility, and the smallest useful first release.

4. Explore and prototype

I use wireframes to make structure visible, then build realistic Figma or Adobe XD prototypes from the team’s design system. Feedback comes early, while change is still cheap.

5. Deliver the final design

I deliver the final design with annotated specs, tokens, and component guidance, then work directly with engineering to resolve gaps and make sure the built product matches the intent.

6. Learn after launch

“The launch is a starting point. I watch how the product performs in the hands of real people, bring testing and feedback back to the team, and help rework the experience as new needs, edge cases, and opportunities appear.”