What is Zuri Health?

Providing affordable and accessible healthcare solutions is at the heart of Zuri Health. Zuri Health is an all inclusive integrated mobile app and web app that digitally connects patients with doctors.

Millions of people in Africa do not have access to quality medical care. Zuri Health has taken time to develop a product that will fill that gap, giving doctors and health workers a wider and easier platform to reach patients who need them. With Zuri Health the underserved populace can now access affordable and sustainable healthcare.

Understanding the problem

I conducted a brainstorming workshop with the product team and interviewed existing users and to uncover pains felt by users. It was revealed that:

• Some of our potential users had old or low grade smartphones that might not be able to download the app from the playstore/app store.
• Some potential users may need the app for a one time transaction and may not be interested in giving off vital information or downloading the app for that.
• Some of our potential users had phones with low memory and maybe disincentivized from downloading this app because of this.
• The user flow from downloading the app to purchasing a drug was too long and users may not have that time.
• Smartphone users just have too many apps on their phone.

‍

Realigning product with company vision and solution heading forwarding

From these findings, we concluded that the product as it stand don’t not align it with company vision and key business goals:

• We want users to access healthcare easily and quickly at the palm of their hands.
• We want an inclusive platform that services everybody
• We want to change the way people approach or access health in africa.

EXPLORING ALTERNATIVES

Subsequently, we carried out a competitive analysis of other digital pharmacy to see how these businesses had been able to approach the same problems and execute similar ideas.

Trying out firsthand experiences with some of these applications enabled the team to note down the things they had done right and connected with our current understanding of why they had done it, or how they had gone about it.

Key Objectives

• Reduces the average user flow time i.e amount time it takes a user to complete a task 
• To Services the users needs, without them having to provide their vital information or just requiring as little information as possible.
• Not requiring the users to download the app before they can buy drugs.

‍

Strategy

Selling a web solution. 

Separating the pharmacy section from the main app. As usual the web came to the rescue. Designing an ecommerce website solved most of the problem, as 

• It didn't require users to download the app or have the high grade or the latest smartphone devices to access them. 
• And links to any drug on the shelf are easily shareable. 
• It cuts away time, it takes users who live in areas with low network coverage to download the app.

The Prioritization dilemma

We decided to build a website solely dedicated to pharmacy products, which didn’t require the user  to login or produce too much information before they can buy drugs. 

 In order to achieve this, we took the extra step of categorizing the features into broader Epics to provide the Product team with visibility into the key areas of the product that needed to be addressed from a usability standpoint. This not only helped to prioritize features in order of need but also helped to shape the product roadmap.

‍

The product team came to the conclusion that the following feature had to be removed or modified, for it would require additional information from the user to properly design. 

• Favorites / Saved items
• Order section(This would handle by via email or phone update )
• Login/Sign up section.

‍

Important user information required was identified to be 

• Users Full Name 
• Email or phone number
• Delivery address
• Prescription(as it is a pharmacy).

The personal shopper experiment

 In order to further reduce the user screen time, a feature which helps the users search and buy the drugs and have them delivered to their prefered location, Instead of users having to sort through our catalog of thousands of medications, which would increase their screen time. This is an interactive chat session where users can speak to a certified pharmacy and have them do buying.

‍

Design process

‍

Choreographing the User Experience

I wanted users to be able to complete their goals with the fewest number of screens possible.I created two user flow diagrams, one for when the user is buying an over the counter(OTC) drug and another when the user is buying a prescription drug, so that I could visualize the user experience and see what the necessary screens were.

‍

‍

‍

Wireframing the solution

The main takeaway from my low-fidelity wireframe was to consider how I could incorporate the solution discussed above into a better way for users to buy drugs.

‍

‍

‍

‍

‍

Final Designs (for now)!

After some team feedback during our weekly demo meetings and few more iterations, a couple of things were changed:

I built the high-fidelity prototype using Figma. The existing system had an already established color scheme and layout, so I had to work around implementing the new features, while unifying the visual direction for the entire product.

Designing for different break point

‍

‍

‍

‍

‍

‍

‍

‍

Design showcase

‍

‍

Results and takeaways

We have gotten results for this yet, as this designs are still in developments.

I learnt the following important takeaways from this project concerning product and business processes:

• Keep it simple Don't bug the user down with unnecessary information or pages, go straight to the point.
• Set a priority Setting priority help you during the course of a design sprint, to eliminate unnecessary features or information.
• Your are competing for the attention of a user, use it wisely

‍

Special Thanks

Glory Essien - My faithful collaborator.