My Design Process: From Chaos to Clarity
I’ve built a design process that helps me move from messy ideas to meaningful user experiences, efficiently and strategically.
Insights
May 2, 2025
1. Research & Discovery
Before jumping into visuals, I invest time in understanding the problem space. I ask questions, study user behavior, review analytics, and run stakeholder interviews when possible. The goal? To uncover real needs, not just surface requests.
In a recent healthcare project, this step helped me identify that older users struggled with basic navigation — not due to complexity, but due to poor contrast, text sizing, and button feedback. That insight became the north star for every design decision afterward.
2. Concept & Ideation
Armed with insights, I explore different solutions — sketching, wireframing, and creating early flows. I typically use Figma for ideation and Notion or Miro for mapping journeys and systems.
This is where I collaborate most closely with PMs and developers to validate ideas early and avoid surprises later. My goal here is to solve the right problem, not over-design the wrong one.
3. Feedback & Iteration
Once there’s a working prototype (low or high fidelity), I test it — with users if possible, or internally with teams and stakeholders. I believe design should provoke discussion, and feedback is never a setback — it’s part of refinement.
One of my favorite parts here is revisiting assumptions. Did that feature actually help? Did that animation distract? Every iteration brings more clarity.
4. Handoff & Beyond
When we’re ready to ship, I focus on a smooth design-to-dev transition. I use design systems, annotate key interactions, and stay involved through QA to ensure that what goes live reflects the intention behind the design.
But my job doesn’t stop at handoff — I track impact, learn what worked (or didn’t), and use that knowledge in the next iteration.
Why This Matters
Too often, design is seen as a straight line: idea → screen → done. But real-world product design is messy, collaborative, and always evolving. A solid process is how I stay creative and consistent.
What I Learned
Design is not just craft — it’s problem-solving
Feedback isn’t failure — it’s fuel
Good design is accessible, scalable, and intuitive
Collaboration beats ego
A designer’s job isn’t just to design — it’s to make products work
If you're reading this ahead of my interview — thank you for taking the time. I’m excited to bring this mindset, process, and energy to your team.
More to Discover
My Design Process: From Chaos to Clarity
I’ve built a design process that helps me move from messy ideas to meaningful user experiences, efficiently and strategically.
Insights
May 2, 2025
1. Research & Discovery
Before jumping into visuals, I invest time in understanding the problem space. I ask questions, study user behavior, review analytics, and run stakeholder interviews when possible. The goal? To uncover real needs, not just surface requests.
In a recent healthcare project, this step helped me identify that older users struggled with basic navigation — not due to complexity, but due to poor contrast, text sizing, and button feedback. That insight became the north star for every design decision afterward.
2. Concept & Ideation
Armed with insights, I explore different solutions — sketching, wireframing, and creating early flows. I typically use Figma for ideation and Notion or Miro for mapping journeys and systems.
This is where I collaborate most closely with PMs and developers to validate ideas early and avoid surprises later. My goal here is to solve the right problem, not over-design the wrong one.
3. Feedback & Iteration
Once there’s a working prototype (low or high fidelity), I test it — with users if possible, or internally with teams and stakeholders. I believe design should provoke discussion, and feedback is never a setback — it’s part of refinement.
One of my favorite parts here is revisiting assumptions. Did that feature actually help? Did that animation distract? Every iteration brings more clarity.
4. Handoff & Beyond
When we’re ready to ship, I focus on a smooth design-to-dev transition. I use design systems, annotate key interactions, and stay involved through QA to ensure that what goes live reflects the intention behind the design.
But my job doesn’t stop at handoff — I track impact, learn what worked (or didn’t), and use that knowledge in the next iteration.
Why This Matters
Too often, design is seen as a straight line: idea → screen → done. But real-world product design is messy, collaborative, and always evolving. A solid process is how I stay creative and consistent.
What I Learned
Design is not just craft — it’s problem-solving
Feedback isn’t failure — it’s fuel
Good design is accessible, scalable, and intuitive
Collaboration beats ego
A designer’s job isn’t just to design — it’s to make products work
If you're reading this ahead of my interview — thank you for taking the time. I’m excited to bring this mindset, process, and energy to your team.
More to Discover
My Design Process: From Chaos to Clarity
I’ve built a design process that helps me move from messy ideas to meaningful user experiences, efficiently and strategically.
Insights
May 2, 2025
1. Research & Discovery
Before jumping into visuals, I invest time in understanding the problem space. I ask questions, study user behavior, review analytics, and run stakeholder interviews when possible. The goal? To uncover real needs, not just surface requests.
In a recent healthcare project, this step helped me identify that older users struggled with basic navigation — not due to complexity, but due to poor contrast, text sizing, and button feedback. That insight became the north star for every design decision afterward.
2. Concept & Ideation
Armed with insights, I explore different solutions — sketching, wireframing, and creating early flows. I typically use Figma for ideation and Notion or Miro for mapping journeys and systems.
This is where I collaborate most closely with PMs and developers to validate ideas early and avoid surprises later. My goal here is to solve the right problem, not over-design the wrong one.
3. Feedback & Iteration
Once there’s a working prototype (low or high fidelity), I test it — with users if possible, or internally with teams and stakeholders. I believe design should provoke discussion, and feedback is never a setback — it’s part of refinement.
One of my favorite parts here is revisiting assumptions. Did that feature actually help? Did that animation distract? Every iteration brings more clarity.
4. Handoff & Beyond
When we’re ready to ship, I focus on a smooth design-to-dev transition. I use design systems, annotate key interactions, and stay involved through QA to ensure that what goes live reflects the intention behind the design.
But my job doesn’t stop at handoff — I track impact, learn what worked (or didn’t), and use that knowledge in the next iteration.
Why This Matters
Too often, design is seen as a straight line: idea → screen → done. But real-world product design is messy, collaborative, and always evolving. A solid process is how I stay creative and consistent.
What I Learned
Design is not just craft — it’s problem-solving
Feedback isn’t failure — it’s fuel
Good design is accessible, scalable, and intuitive
Collaboration beats ego
A designer’s job isn’t just to design — it’s to make products work
If you're reading this ahead of my interview — thank you for taking the time. I’m excited to bring this mindset, process, and energy to your team.