YesDoctor App Design: Getting ready to crack the market
Industry
Healthcare, Fintech
Duration
16 weeks
Category
UX Design, Product Design, UX Research
Tools
Figma, Miro
Background:
I joined Yes Doctor before the first launch of the product, and the previous designer had left the design half-finished.
Stakeholders set a 4 months deadline to getting product ready to go to market a User-Centric application for both side (Patients and Doctors) but in this case study I want to talk about patient app.
What was the problem?
How can we make early adapters comfortable with this product?
In a design that has not been completed, what needs to be designed or changed? ( within the deadline)
What did I do?
1. Finding problems:
I decided to use the usability audit method with our stakeholders to look for dead-ends' flows and Complexity of the product.
This was the fastest way to find problems in the short time before the launch. While using this method, I've drew the existing flows on Miro so that the directions were written and I could refer to them later.
Which flows are more important? Which flows are dead-end? Which flows are missed? Which flows are unnecessary?
These questions were my main questions at that point.
We discussed dead-end flows based on business goals:
Critical flows (Payment, booking appointment, ..): our decision was to start the design process quickly.
Nearest future goals that need new flows, we put in the next priority.
Optional flows (refer a friend, get a discount, etc.) that their development cost was high at that moment (before first launch), we hide them to think about them after the first release and attract first customers' attention.
2. Information Gathering:
I.From users:
I started to prepare a document about (who are we, what we want to do and add a Whatsapp link and ask them to join) then I ask our partners (Doctors who wanted to work with us) to share this document with their patients who are in the middle of doing surgery process. I shared this document in a Fasebook groups related to doing plastic surgery too.
I wanted to know their perspective and I asked them how they do their surgery now (without YesDoctor)
II.From Stakeholders:
Making a clear vision of business's future, including its possibilities and limitations
I ran a usability test with focus group and tracked their behaviors and quotes and put them into a Costumer journey map for easy communication among stakeholders, developers, and product managers.
Check out the image's detail here.
As a result of this CJM, the flow was divided into three sections, which I mentioned earlier. Each Scrum sprint, the product manager and I prioritize problems and come up with design solutions.
3. Design Completing (Results):
To present new proposals, it was necessary to pay special attention to the integrity of the product and the information architecture, all of the changes started from here.
Main flow:
Check out the image's detail here.
Registration flow:
Check out the image's detail here.
Here's a small part of my approach, I've made the information architecture for each section and then designed the wireframes. This approach helped us track versions and changes, also makes communications between developers and product team much easier!
Check out the image's detail here.
Some of UI results + Figma delivered file which make our communications easier and help us avoid confusion in different versions of each parts
Check out the image's detail here.
YesDoctor App Design: Getting ready to crack the market
Industry
Healthcare, Fintech
Duration
16 weeks
Category
UX Design, Product Design, UX Research
Tools
Figma, Miro
Background:
I joined Yes Doctor before the first launch of the product, and the previous designer had left the design half-finished.
Stakeholders set a 4 months deadline to getting product ready to go to market a User-Centric application for both side (Patients and Doctors) but in this case study I want to talk about patient app.
What was the problem?
How can we make early adapters comfortable with this product?
In a design that has not been completed, what needs to be designed or changed? ( within the deadline)
What did I do?
1. Finding problems:
I decided to use the usability audit method with our stakeholders to look for dead-ends' flows and Complexity of the product.
This was the fastest way to find problems in the short time before the launch. While using this method, I've drew the existing flows on Miro so that the directions were written and I could refer to them later.
Which flows are more important? Which flows are dead-end? Which flows are missed? Which flows are unnecessary?
These questions were my main questions at that point.
We discussed dead-end flows based on business goals:
Critical flows (Payment, booking appointment, ..): our decision was to start the design process quickly.
Nearest future goals that need new flows, we put in the next priority.
Optional flows (refer a friend, get a discount, etc.) that their development cost was high at that moment (before first launch), we hide them to think about them after the first release and attract first customers' attention.
2. Information Gathering:
I.From users:
I started to prepare a document about (who are we, what we want to do and add a Whatsapp link and ask them to join) then I ask our partners (Doctors who wanted to work with us) to share this document with their patients who are in the middle of doing surgery process. I shared this document in a Fasebook groups related to doing plastic surgery too.
I wanted to know their perspective and I asked them how they do their surgery now (without YesDoctor)
II.From Stakeholders:
Making a clear vision of business's future, including its possibilities and limitations
I ran a usability test with focus group and tracked their behaviors and quotes and put them into a Costumer journey map for easy communication among stakeholders, developers, and product managers.
Check out the image's detail here.
As a result of this CJM, the flow was divided into three sections, which I mentioned earlier. Each Scrum sprint, the product manager and I prioritize problems and come up with design solutions.
3. Design Completing (Results):
To present new proposals, it was necessary to pay special attention to the integrity of the product and the information architecture, all of the changes started from here.
Main flow:
Check out the image's detail here.
Registration flow:
Check out the image's detail here.
Here's a small part of my approach, I've made the information architecture for each section and then designed the wireframes. This approach helped us track versions and changes, also makes communications between developers and product team much easier!
Check out the image's detail here.
Some of UI results + Figma delivered file which make our communications easier and help us avoid confusion in different versions of each parts
Check out the image's detail here.
YesDoctor App Design: Getting ready to crack the market
Healthcare, Fintech
16 weeks
UX Design, Product Design, UX Research
Tools
Figma, Miro
Background:
I joined Yes Doctor before the first launch of the product, and the previous designer had left the design half-finished.
Stakeholders set a 4 months deadline to getting product ready to go to market a User-Centric application for both side (Patients and Doctors) but in this case study I want to talk about patient app.
What was the problem?
How can we make early adapters comfortable with this product?
In a design that has not been completed, what needs to be designed or changed? ( within the deadline)
What did I do?
1. Finding problems:
I decided to use the usability audit method with our stakeholders to look for dead-ends' flows and Complexity of the product.
This was the fastest way to find problems in the short time before the launch. While using this method, I've drew the existing flows on Miro so that the directions were written and I could refer to them later.
Which flows are more important? Which flows are dead-end? Which flows are missed? Which flows are unnecessary?
These questions were my main questions at that point.
We discussed dead-end flows based on business goals:
Critical flows (Payment, booking appointment, ..): our decision was to start the design process quickly.
Nearest future goals that need new flows, we put in the next priority.
Optional flows (refer a friend, get a discount, etc.) that their development cost was high at that moment (before first launch), we hide them to think about them after the first release and attract first customers' attention.
2. Information Gathering:
I.From users:
I started to prepare a document about (who are we, what we want to do and add a Whatsapp link and ask them to join) then I ask our partners (Doctors who wanted to work with us) to share this document with their patients who are in the middle of doing surgery process. I shared this document in a Fasebook groups related to doing plastic surgery too.
I wanted to know their perspective and I asked them how they do their surgery now (without YesDoctor)
II.From Stakeholders:
Making a clear vision of business's future, including its possibilities and limitations
I ran a usability test with focus group and tracked their behaviors and quotes and put them into a Costumer journey map for easy communication among stakeholders, developers, and product managers.
Check out the image's detail here.
As a result of this CJM, the flow was divided into three sections, which I mentioned earlier. Each Scrum sprint, the product manager and I prioritize problems and come up with design solutions.
3. Design Completing (Results):
To present new proposals, it was necessary to pay special attention to the integrity of the product and the information architecture, all of the changes started from here.
Main flow:
Check out the image's detail here.
Registration flow:
Check out the image's detail here.
Here's a small part of my approach, I've made the information architecture for each section and then designed the wireframes. This approach helped us track versions and changes, also makes communications between developers and product team much easier!
Check out the image's detail here.
Some of UI results + Figma delivered file which make our communications easier and help us avoid confusion in different versions of each parts
Check out the image's detail here.
YesDoctor App Design: Getting ready to crack the market
Industry
Healthcare, Fintech
Duration
16 weeks
Category
UX Design, Product Design, UX Research
Tools
Figma, Miro
Background:
I joined Yes Doctor before the first launch of the product, and the previous designer had left the design half-finished.
Stakeholders set a 4 months deadline to getting product ready to go to market a User-Centric application for both side (Patients and Doctors) but in this case study I want to talk about patient app.
What was the problem?
How can we make early adapters comfortable with this product?
In a design that has not been completed, what needs to be designed or changed? ( within the deadline)
What did I do?
1. Finding problems:
I decided to use the usability audit method with our stakeholders to look for dead-ends' flows and Complexity of the product.
This was the fastest way to find problems in the short time before the launch. While using this method, I've drew the existing flows on Miro so that the directions were written and I could refer to them later.
Which flows are more important? Which flows are dead-end? Which flows are missed? Which flows are unnecessary?
These questions were my main questions at that point.
We discussed dead-end flows based on business goals:
Critical flows (Payment, booking appointment, ..): our decision was to start the design process quickly.
Nearest future goals that need new flows, we put in the next priority.
Optional flows (refer a friend, get a discount, etc.) that their development cost was high at that moment (before first launch), we hide them to think about them after the first release and attract first customers' attention.
2. Information Gathering:
I.From users:
I started to prepare a document about (who are we, what we want to do and add a Whatsapp link and ask them to join) then I ask our partners (Doctors who wanted to work with us) to share this document with their patients who are in the middle of doing surgery process. I shared this document in a Fasebook groups related to doing plastic surgery too.
I wanted to know their perspective and I asked them how they do their surgery now (without YesDoctor)
II.From Stakeholders:
Making a clear vision of business's future, including its possibilities and limitations
I ran a usability test with focus group and tracked their behaviors and quotes and put them into a Costumer journey map for easy communication among stakeholders, developers, and product managers.
Check out the image's detail here.
As a result of this CJM, the flow was divided into three sections, which I mentioned earlier. Each Scrum sprint, the product manager and I prioritize problems and come up with design solutions.
3. Design Completing (Results):
To present new proposals, it was necessary to pay special attention to the integrity of the product and the information architecture, all of the changes started from here.
Main flow:
Check out the image's detail here.
Registration flow:
Check out the image's detail here.
Here's a small part of my approach, I've made the information architecture for each section and then designed the wireframes. This approach helped us track versions and changes, also makes communications between developers and product team much easier!
Check out the image's detail here.
Some of UI results + Figma delivered file which make our communications easier and help us avoid confusion in different versions of each parts
Check out the image's detail here.
