Start with the why
I begin by understanding the business goals, users, context, and existing experience. I use research, interviews, observation, data, and existing insights to uncover what people actually need.
How I turn problems into products
I don't follow a rigid process. I adapt my approach to the problem, the people, and the product — combining research, thoughtful design, collaboration, and continuous iteration.
Design process stages
Find what matters
I turn what I learn into clear problems, user journeys, priorities, and opportunities — making sure we're solving the right problem before designing the solution.
Think before I polish
I sketch, wireframe, and explore multiple directions before moving into detailed UI. This helps me test ideas early and avoid solving the wrong problem beautifully.
Make it simple and useful
I translate the chosen direction into intuitive interfaces, clear interactions, and scalable design systems while keeping accessibility, consistency, and visual hierarchy in mind.
Learn, improve, repeat
I test ideas with users and stakeholders, gather feedback, identify friction, and iterate. The goal isn't to get everything right the first time — it's to keep making the experience better.
Design doesn't happen alone
I work closely with developers, product teams, and stakeholders throughout the process, refining designs as we learn and making sure the final experience stays true to the problem we're solving.
An iterative, Agile approach
I work in short, collaborative cycles — designing, sharing, testing, learning, and refining as the product evolves.
Explore → Test → Learn → Refine → RepeatGood design isn't a straight line. It's a conversation between people, problems, ideas, and technology.