MedHealth

Medhealth is a a telemedical platform that provide seamless communication and medical services between patients and healthcare providers through web and mobile applications.

CONTEXT

The COVID-19 Pandemic has highlighted more clearly than ever the fact that there is need for institutions to operate remotely, the medical healthcare space is not exempted and obviously this comes with its own set of challenges but for the sake of meeting human needs, the Medhealth team probably decided to embark on this project.
The Medhealth project is projected to offer a range of services which includes Virtual consultations, online appointment booking, emergency assistance and drug ordering, providing remote healthcare consultations and support. The platform aims to improve access to healthcare services, streamline medical consultations, and enhance overall patient experience.

RESEARCH

For this product, I was a Senior Product designer and I worked in a vast team who are scattered acoss multiple timezones. I was involved in almost all the product design sessions but majored more on UX workflows to visual designs collaborating with other team members to achieve success.

At medhealth, we followed a  series of processes which Includes;
- Defining the business need
- Conducting research to gain insight
- Analysing research outcomes and ideation.
- Creating information architecture and user flows
- Creating lo-fi prototypes
- Proceeding to create hi-fi prototypes
- Test

Understanding the different persona types was crucial for this project so we started by conducting a series of user interviews across our persona types with people(both young and old) and medical and health practitioners.
Summary of my Design Process

User interview breakdown with key insights

To manage the amount of data collected from the interviews, we created a database using Coda to log all the key insights. Previously we discovered that research findings get lost in confluence or wherever they are stored. Coda let us organise the insights in a format that allowed us to quickly filter and find insights/pain points/feature requests around a specific topic. This became a powerful resource and was a convenient reference for us and other stakeholders moving forward. We managed to connect our customer feedback directly to the database using Zapier to link the API, so new insights were continually being added.

From here we needed a way to synthesise all these insights into something we could use to move forward. We ran an affinity mapping session with the entire team where we pulled out the key insights from all the interviews and grouped them into common themes. We then voted on which themes we felt were most important from a user and business perspective. This gave us a starting point for areas to focus on for our initial designs.

One of the things that surfaced was the need for having secured a telemedical platform. Users are concerned about their data being shared to a 3rd party... also we found out that the user's concerns resonated around ensuring the platform is secured and reliable. Based on what we learned from the research our design process took the route of of exploring different concepts that focused on answering those user questions.

We took the best ideas we got and incorporated them into paper sketches.

We created a list view of specialised doctors and pharmacist  that gives users the  freedom of going through the Doctors' specialisation, proficiency, experience and everyother thing we might need to know about them.. the aim of this process is To help boost user confidence and trust when using the app. Smooth onboarding user flow that gives users an overview perspective of the possibilities of the mobile application.Notice that from the sketches below, we are able to ideate a possible list/directory presentation for doctors available for consultation in such a way that users can be able to view their certification, qualifications, history and personal details... We used this method to  build confidence in the heart of the users and to end skepticism and fear because the users are able to see that these are not fake.

ARTIST DISCOVERY

"Barrier of Conviction" is a term i use to describe a situation were people are willing to use a product, excited about the concept, understand their benefits upon participation but not willing to take the step forward due to previous stonghold ideologies or past experiences. This wass a typical issue we experienced as our target audience (users) were people living and staying in rural African communities.

MICRO DESIGN SPRINT

We ended up running a micro design sprint to get to the ideation phase as quickly as possible. This was a lean project with internal teams, so without the pressure of a consumer facing release we could move quickly. Over two days we established a set of proto personas and a core set of Jobs To Be Done that related to these.
From here we created a set of "How Might We" statements. Working with the team, this method was a good way to surface the issues most important to their workflow. For them, being quicker and more efficient in the searching process was crucial, alongside surfacing trends before they become visible to the wider industry. All of this culminated in a set of feature ideas that we could start to design against.
"How might we" statements

WIREFRAMES AND DESIGNS

We then went straight into sketching and wireframes, all the time looping these back into the team for immediate feedback. The journey from here to high fidelity was very quick. You have such an advantage designing for an internal team, as the workflow for testing and feedback is almost frictionless compared to an external product.

CONCLUSION

I learnt an incredible amount about the process of getting customer research while building this project. I've never been anywhere that had such easy access to users, be that internal and external — having that feedback was so helpful to iterating quickly on designs. It really drove home the point that having empathy for the user and understanding their motivations and pain points is fundamental for effective product design. This project become one of brilliant importance and which means a lot to me. It became the first comprehensive project that I became entirely accountable for the achievement or failure of. It challenged me in approaches that reinforced my research, grew my empathy, and refined my layout skills.