top of page

Design Process

This is how I approach problem solving through design. I follow a general process that I tailor to fit each project's unique needs.

01

Understand the problem

I gain clarity on the user's needs, business goals, and the context of the problem. This step sets the foundation for meaningful solutions.

Questions to ask:

  1. What problem are we trying to solve, and for whom?

  2. What are the user's pain points or unmet needs?

  3. What constraints (technical, business, timeline) should I be aware of?

02

Brainstorm

I explore a wide range of ideas without judgment. This encourages creativity and invites multiple perspectives.

Questions to ask:

  1. What are all the possible ways we could approach this?

  2. Are we considering both conventional and unconventional ideas?

  3. Who should be involved to bring fresh perspectives?

03

Ideate & test

Select promising ideas and quickly build and test them to explore feasibility and user relevance.

Questions to ask:

  1. Which ideas have the most potential to solve the problem?

  2. How can we test these concepts quickly and inexpensively?

  3. What assumptions are we making, and how can we validate them?

04

Define

Refine and structure the chosen solution into a cohesive and functional design.

05

Prototype & Test

Build interactive or visual representations of the design and test usability, flow, and experience.

06

Validate

Confirm that the solution works as intended by gathering feedback from real users and stakeholders.

Questions to ask:

  1. How can we turn our best ideas into a clear design direction?

  2. Does the design meet user needs and business goals?

  3. Are there gaps in the user journey or interface that need solving?

Questions to ask:

  1. What level of fidelity does the prototype need for useful feedback?

  2. Where might users get confused or stuck in this version?

  3. What are we hoping to learn from this round of testing?

Questions to ask:

  1. Does the solution solve the user’s problem effectively?

  2. What feedback patterns are emerging from users and stakeholders?

  3. What should we improve before moving forward or launching?

bottom of page