When starting a project, I first gather as much relevant info as possible. Then, outline product goals and understand the requirements.

I follow by reviewing existing data and defining my approach for future steps.

I get a good sense of the stakeholders and understand who is the main audience for what we’re building.

I then draw up a map of existing ideas and assumptions to categorize them as validated or not. Based on these, we should be able to identify success criteria for what we’re about to do.

Before diving in, I research any existing solutions to better understand the market. I interview stakeholders and users to understand the problems they’re facing and confirm assumptions.

This will allow me to partner with product managers and developers in tackling validated assumptions.

At this point, it's key to design for the proper fidelity (wireframe / hi-fi mockups). They're instrumental in getting validation & buy-in from stakeholders and then users.

Based on topics that converge, the concept is further refined, along with the definition of leading metrics & KPIs.

After carving out the happy path, it’s time to branch out into supporting scenarios.

This can include error handling, empty states or, if needed, adapting things to overcome technical challenges. Developers often enjoy well-defined scenarios, so I try to make it as clear as possible through specs or event tracking.

Usually, after launch, a product or feature needs further attention.

I closely track metrics and user feedback, drawing conclusions for future improvements.