Available for Work
Going from 0-1:
My Design Process
A good design process is ever evolving and highly adaptive to the given challenge, but here are some general activities that I always find useful when working with new teams.
1 - Problem Discovery
Every project begins with understanding the problem. But in my experience, problem discovery is not a one-time event—it's an ongoing, iterative process. I start by defining the problem space and setting initial objectives, but I remain flexible, knowing that new insights may emerge as the project evolves. Understanding business goals and user pain points is crucial, but so is revisiting these elements as I gather more information. Here are the main activities I like conducting at the earliest stages when working with startups:
UX Research Activities
User Interviews:
I prioritize user interviews because they allow me to connect directly with the people who will be using the product. These conversations provide invaluable qualitative insights into users' pain points, motivations, and behaviors. By conducting interviews at various stages, I ensure that my understanding evolves alongside the project, keeping the design aligned with actual user needs.
User Journeys:
Mapping user journeys helps me visualize the entire experience from the user’s perspective. This is crucial for identifying pain points and opportunities throughout the product’s lifecycle. I revisit and refine these maps as new information comes to light, ensuring that every design decision supports a seamless user experience.
Mind Maps:
Mind maps are a creative tool that I use to explore and organize ideas. They help me think broadly about potential solutions and make connections between different aspects of the project. I find that revisiting these maps throughout the process ensures that no valuable insights or opportunities are overlooked.
Surveys and Quantitative Research:
Surveys and other quantitative research methods complement the qualitative insights I gain from interviews and other activities. I like using these tools because they help validate my hypotheses at scale, providing a broader understanding of user preferences and priorities. This data-driven approach helps me prioritize features and make informed design decisions.
Contextual Inquiries:
Contextual inquiry is one of my favorite research methods because it allows me to observe users in their natural environment. This real-world context often reveals insights that interviews or surveys might miss, such as environmental factors that influence how users interact with the product. I find that this method adds depth to my understanding of user needs, which translates into more intuitive and effective designs.
Affinity Diagrams:
I use affinity diagrams to make sense of large amounts of qualitative data, like user feedback or interview notes. This process helps me identify patterns and themes that might not be immediately obvious. As the project evolves, I reorganize this data to refine my understanding, making sure that the design continues to address the most pressing user needs.
JTBD Sprints:
Jobs-To-Be-Done (JTBD) Sprints allow me to focus on what users are trying to accomplish with the product. By understanding these jobs, I can design features that directly address their needs, leading to more targeted and effective solutions. I revisit these sprints as the project evolves, ensuring that the product remains aligned with what users truly want to achieve.
Competitive Research:
Staying aware of the competition is vital in any market, but especially in a startup. I engage in continuous competitive analysis to keep track of market trends and competitor offerings. This ongoing process informs both the design and overall strategy, ensuring our product is differentiated and positioned for success.
2 - Iterative Design & Prototyping
Every project begins with understanding the problem. But in my experience, problem discovery is not a one-time event—it's an ongoing, iterative process. I start by defining the problem space and setting initial objectives, but I remain flexible, knowing that new insights may emerge as the project evolves. Understanding business goals and user pain points is crucial, but so is revisiting these elements as I gather more information. Here are the main activities I like conducting at the earliest stages when working with startups:
UX Research Activities
User Interviews:
I prioritize user interviews because they allow me to connect directly with the people who will be using the product. These conversations provide invaluable qualitative insights into users' pain points, motivations, and behaviors. By conducting interviews at various stages, I ensure that my understanding evolves alongside the project, keeping the design aligned with actual user needs.
User Journeys:
Mapping user journeys helps me visualize the entire experience from the user’s perspective. This is crucial for identifying pain points and opportunities throughout the product’s lifecycle. I revisit and refine these maps as new information comes to light, ensuring that every design decision supports a seamless user experience.
Mind Maps:
Mind maps are a creative tool that I use to explore and organize ideas. They help me think broadly about potential solutions and make connections between different aspects of the project. I find that revisiting these maps throughout the process ensures that no valuable insights or opportunities are overlooked.
Surveys and Quantitative Research:
Surveys and other quantitative research methods complement the qualitative insights I gain from interviews and other activities. I like using these tools because they help validate my hypotheses at scale, providing a broader understanding of user preferences and priorities. This data-driven approach helps me prioritize features and make informed design decisions.
Contextual Inquiries:
Contextual inquiry is one of my favorite research methods because it allows me to observe users in their natural environment. This real-world context often reveals insights that interviews or surveys might miss, such as environmental factors that influence how users interact with the product. I find that this method adds depth to my understanding of user needs, which translates into more intuitive and effective designs.
Affinity Diagrams:
I use affinity diagrams to make sense of large amounts of qualitative data, like user feedback or interview notes. This process helps me identify patterns and themes that might not be immediately obvious. As the project evolves, I reorganize this data to refine my understanding, making sure that the design continues to address the most pressing user needs.
JTBD Sprints:
Jobs-To-Be-Done (JTBD) Sprints allow me to focus on what users are trying to accomplish with the product. By understanding these jobs, I can design features that directly address their needs, leading to more targeted and effective solutions. I revisit these sprints as the project evolves, ensuring that the product remains aligned with what users truly want to achieve.
Competitive Research:
Staying aware of the competition is vital in any market, but especially in a startup. I engage in continuous competitive analysis to keep track of market trends and competitor offerings. This ongoing process informs both the design and overall strategy, ensuring our product is differentiated and positioned for success.
