Each project is unique but here's my general approach to product design.
01.
Analysis
The first step is always to understand and articulate the problem. Before starting research I try to get as much context as possible on the motivation for a product or feature, KPIs and how it aligns to business goals.
01.
Analysis
The first step is always to understand and articulate the problem. Before starting research I try to get as much context as possible on the motivation for a product or feature, KPIs and how it aligns to business goals.
01.
Analysis
The first step is always to understand and articulate what problem am I aiming to solve. There’s no point in starting research without understanding what and why. By that I don’t mean like “the job is to design an app to order food” for instance. I mean understanding why someone needs an app to order food and what motivates a founder to build a service like that. That’s the type of answers I always try to break down before moving to research.
02.
Research and discovery
When the problem is set, I start researching. I usually begins by exploring the market, analyse competitors if there’s any, and identify gaps and opportunities. That leads to user research, understanding the target audience, their needs and pain points with interviews, surveys and/or observations. Before moving further, it’s always important to have a context on technology assessment, regulations and compliance.
02.
Research and discovery
When the problem is set, I start researching. I usually begins by exploring the market, analyse competitors if there’s any, and identify gaps and opportunities. That leads to user research, understanding the target audience, their needs and pain points with interviews, surveys and/or observations. Before moving further, it’s always important to have a context on technology assessment, regulations and compliance.
02.
Research and discovery
Once I get the problem, I’m able to start research. I usually start by a (or a few) stakeholder interview(s) to align business goals and purposes. Then exploring the market, analyse competitors if there’s any, and identify gaps and opportunities. That leads to user research, understanding the target audience with interviews, surveys and/or observations. Before moving further, it’s always important to have a context on technology assessment, regulations and compliance.
03.
Ideation and conceptualization
When there's enough context, I usually start by sketching and wireframing some possible solutions, putting up some prototypes to validate those ideas with users and stakeholders. This process goes on until one proposal is matured enough to move forward.
03.
Ideation and conceptualization
When there's enough context, I usually start by sketching and wireframing some possible solutions, putting up some prototypes to validate those ideas with users and stakeholders. This process goes on until one proposal is matured enough to move forward.
03.
Ideation and conceptualization
When I have enough context, I usually start by sketching and wireframing some possible solutions, putting up some quick prototypes to validate those ideas with users and stakeholders. This process goes on until one proposal is matured enough to move forward.
04.
Hi-Fidelity design and handoff
This phase can be initiated in various ways. I’ve tackled projects where a design system or visual style guide is pre-established, while others require starting from scratch. In the absence of predefined elements, my typical starting point involves crafting a flexible color scheme, establishing typographic hierarchy, and defining spacing/grid structures—though subject to potential adjustments. This foundational work is crucial for maintaining consistency and expediting the design of components and layouts. Fortunately modern design tools allow designers to keep this approach neat. My procedure on visual design is very much in line with the so-called “Atomic” design. It means that smaller and simpler components combined together create more complex and responsive “organisms” that compose the interface final design. Once it’s matured enough, I create comprehensive prototypes to validate the design with users and stakeholders, this time with a more realistic perspective on the final product. Once it’s validated it’s time to document and handoff for production.
04.
Hi-Fidelity design and handoff
This phase can be initiated in various ways. I’ve tackled projects where a design system or visual style guide is pre-established, while others require starting from scratch. In the absence of predefined elements, my typical starting point involves crafting a flexible color scheme, establishing typographic hierarchy, and defining spacing/grid structures—though subject to potential adjustments. This foundational work is crucial for maintaining consistency and expediting the design of components and layouts. Fortunately modern design tools allow designers to keep this approach neat. My procedure on visual design is very much in line with the so-called “Atomic” design. It means that smaller and simpler components combined together create more complex and responsive “organisms” that compose the interface final design. Once it’s matured enough, I create comprehensive prototypes to validate the design with users and stakeholders, this time with a more realistic perspective on the final product. Once it’s validated it’s time to document and handoff for production.
04.
Hi-Fidelity design and handoff
This phase can be initiated in various ways. I’ve tackled projects where a design system or visual style guide is pre-established, while others require starting from scratch. In the absence of predefined elements, my typical starting point involves crafting a flexible color scheme, establishing typographic hierarchy, and defining spacing/grid structures—though subject to potential adjustments. This foundational work is crucial for maintaining consistency and expediting the design of components and layouts. Fortunately modern design tools allow designers to keep this approach neat. My procedure on visual design is very much in line with the so-called “Atomic” design. It means that smaller and simpler components combined together create more complex and responsive “organisms” that compose the interface final design. Once it’s matured enough, I create comprehensive prototypes to validate the design with users and stakeholders, this time with a more realistic perspective on the final product. Once it’s validated it’s time to document and handoff for production.
Toolbox
Toolbox
Design and prototyping