top of page



1. Discovery



Define clearly your desired outcome and share it to everyone

Define your user target and your context

Define the duration of the discovery


The goal can be to understand and list the jobs to be done (key use cases) and also describe users workflows.


We also observe, list and qualify current pain points,

check if it's fit to business goals and industry best practices


Discovery should be a continuous mindset of the product team, it's necessary in order to feed your knowledge about your users, about your product, and also to mesure and prioritise your roadmap and change it on time and reorder OKR thanks to this material.


Benchmarking, understand your field, talk to people, understand how to find data and people to answer to your questions and try to clean your hypothesis.


Interviews preparation


Design the user interview guide. Be aware to biases. Share it to the team and get feedbacks.
Collaboration and strategic alignment are key.


Recruite users for the interviews : 

  • with the help of sales team, accounts managers, support team, marketing team and your interviewee it self can refer user to you... 

  • You can also use social media and communication platform (Facebook groups, Linkedin Slack, Whatsapp),

  • or guerrilla interviews on the field

  • or use a recruiting service (low effort, high cost)


Send massive email campaign (300 emails around 8% of answers) and think about rewards in return (cash, discount, goodies, invitation for events, premium access to the new feature...).


At least two people to interview your users in order to cross different mindset and help you to focus on users behaviours not only on your notes.


Extract Interviews informations


All your interviews should be in a data board, with key informations and the link to the notes.

Thank to your user interview guide, all your interviews have a common structure. On the top of the page don't forget to add an abstract of learnings.

Do not underestimate the value of classifying the users verbatim, it should help you quantify some of the emotional recurrences of your users and highlight some issues.


Make on opportunity tree to clarify the discovery space.


During the interview phase, share frequently your learnings, feelings, questions and pains to the team. As usual anyone can be useful.
Finally show your opportunity tree and decide which one have the biggest value (also for who).


2. Wireframing User flow 


It"s time to map user flow and map your feature.


what's the job to be done in this context : Information architecture and visual hierarchisation.


Accessibility check DWCAG 2.0



Competitive analysis and User experience benchmark from other fields.


Build an interactive prototype, test it as soon as possible. You should test the solutions one by one in order to have a clear view of the reception of each and prioritise the development. 


3. UI 


Lucky you, there is a design system, so use it .


Well you don't have one ? So, build a consistent library of components, think with the atomic design methodology and combine it with the branding style guide and don't forget to determine the tone of voice.


Your high fidelity prototype is ready to be test by users. 


Share your design as soon as possible to get feedbacks from developers and keep the feasibility and the time to market as clear as possible.


4. Development 


Schedule a Kick off meeting : show the roadmap and answer to the questions.


Build KPI in order to delete the feature and understand if it's a fail or a win.

Dont forget the tracking and follow the life of your feature with qualitatives and quantitatives datas.

bottom of page