Process
This is my general process for approaching designs. This process is always iterative and non-linear.
Initial Analysis
Traditionally, you may see ‘Research’ or ‘Empathize’ as the first step in the design process. But when joining a company, there will typically be an existing product and I will seek to understand the users, the problem & pain point a product is trying to solve for.
I may look through existing user testing results, personas, user journeys, or conduct a heuristic evaluation as part of my initial analysis.
Research
Once I’m given a project to work on with a project definition, problem statement, and/or business goal, I will conduct research by talking to users and/or conduct a competitive/comparative analysis.
To prep for user research, I typically define the research goal and formulate a set of questions to gain an understand of the user's goals, current process, motivation, and pain point and answer the who, what, where, when, why, and how.
Research Synthesize
The research notes will then be synthesized to identify themes and insights.
Personas / User Journeys / Scenarios
Depending on the project, personas, user journeys, or user scenarios may need to be created or modified.
Ideation
This its the stage where multiple solutions as explored as ideas are allowed to diverge, typically in the form of sketches to start with. User flows are drafted as well.
Prototype
After a series of feedback from stakeholders and other team members, the designs go through a convergent phase and the hypothesized solution can be picked for user testing.
For an existing product, there's typically design patterns or a design systems in place, and it should be easy to pull assets from the components library to execute a high fidelity mockup for testing. I like to use Marvel or Invision as my prototyping tool.
Deploy & Learn
Once deployed, it’s important to learn from it, tracking key KPIs that's been defined as a measure of success.
Process
Every project is different, but this is my general process for designs. The process is always iterative and non-linear.
Initial Analysis
Traditionally, you may see ‘Research’ or ‘Empathize’ as the first step in the design process. But when joining a company, there will typically be an existing product and I will seek to understand the users, the problem & pain point a product is trying to solve for.
I may look through existing user testing results, personas, user journeys, or conduct a heuristic evaluation as part of my initial analysis.
Research
Once I’m given a project to work on with a project definition, problem statement, and/or business goal, I will conduct research by talking to users and/or conduct a competitive/comparative analysis.
To prep for user research, I typically define the research goal and formulate a set of questions to gain an understand of the user's goals, current process, motivation, and pain point and answer the who, what, where, when, why, and how.
Research Synthesize
The research notes will then be synthesized to identify themes and insights.
Personas / User Journeys / Scenarios
Depending on the project, personas, user journeys, or user scenarios may need to be created or modified.
Ideation
This its the stage where multiple solutions as explored as ideas are allowed to diverge, typically in the form of sketches to start with. User flows are drafted as well.
Prototype
After a series of feedback from stakeholders and other team members, the designs go through a convergent phase and the hypothesized solution can be picked for user testing.
For an existing product, there's typically design patterns or a design systems in place, and it should be easy to pull assets from the components library to execute a high fidelity mockup for testing. I like to use Marvel or Invision as my prototyping tool.
Deploy & Learn
Once deployed, it’s important to learn from it, tracking key KPIs that's been defined as a measure of success.