Lytic Health
Web and mobile apps for patients and doctors to automatically determine preliminary diagnosis and schedule the appointments.
In August 2022, I was part of a team that designed and prototyped an idea for a patient doctor communication web and mobile app. The goal was to validate it and help raise funding to continue the project.
Inroduction
Intoduction
MY ROLE
-
User Experience
-
User Interface
-
Journey Mapping
-
Wireframing
-
Usability Testing
-
Interaction Design
TOOLS USED
-
Figma
-
Overflow
-
Zeplin
-
Miro
PLATFORM
-
iOS
-
Android
-
Web
TIMELINE
-
2 Months
Inroduction
What is Lytic Health?
Lytic Health is a Web and mobile app that allows for patients and doctors to automatically determine preliminary diagnosis and schedule the appointments.
My role
I led the design of Lytic Health mobile and web app concept, from feature ideas and user journeys, to the final prototype — including communication with product stakeholders and a remote development team.
Insights and ideation
I conducted “guerrilla research” to gather insights into how patients and doctors interact with one another then translated my findings into features that address their behaviours and motivations.
Main Idea
Doctors spend lots of time on patients that don't have symptoms requiring medical treatment, whereas they could have spent that time on people that are really in need of medical attention. The idea is to automate that process and free up the doctors' time.
Experience strategy and vision
I created journeys and prototypes to share the product vision and execution strategy. This helped to gain alignment and drive decision making.
Planning and scope definition
I defined the product with the stakeholders. I was advocating for balancing customer goals and business goals, prioritised and negotiated features for the initial demo, MVP, and beyond.
Design execution
I designed for mobile Web Platform, executed journeys, wireframes, prototypes and designs specs, preparing the UI for handover to the development team.
Challenge
Demonstrate idea viability and product value through a design prototype
As with any self-funded startup, my commodity was time and scope; the former was limited to 2 months, the latter was initially too broad for an MVP.
​
Our challenge was to create a prototype that could show potential customers and investors, that self-diagmoses and appointment booking could be simple, effective and prosperous for all involved.
Approach
Evaluate existing assumptions. Discard what’s superfluous. Follow the path of least resistance.
Before I was brought on-board for the project, the founders had done some market research on their intended audience. They had already decided on how their app should function, without validating any of their theories first.
What they envisioned was a chatbot and development team had already started developing it.
After a careful consideration backed by a breakdown of design and technical constraints feedback from the development team I started the design process.
​
We worked in bi-weekly sprints using existing evidence from previous user research to form a basis for expanding our understanding of patient doctor communication. To get the idea fast to the market, our strategy was set based on the MVP principles and the product thinking framework.
Styling
Color palette
I chose calm, natural Color Palette with shades of grey and blue.
#8796EC
#FF6A9C
#13D7BC
#3E4554
Styling
Typography
Kept it classic and in style.
Lato
Regular
​
I watched the storm, so beautiful yet terrific.
Lato
Medium
It was going to be a lonely trip back.
Lato
Bold
​
Almost before we knew it, we had left the ground.
Mobile App
Mobile App
Home
The Home screen comprises of a general navigation, symptom search first step, saved searches and appointments pending doctor's approval.
Search
The Search screen includes suggested search functionality along with tagging, that allows having multiple symptoms and more exact diagnosis as a result.
Chat Bot
The Chat Bot asks a number of question based on the symptoms chosen on the previous step.
A typical messenger like view gives a comfortable impression that one is talking to a human being and not a machine.
Appointment
The Chat Bot can suggest making an appointment with doctor in case there are health threatening situation.
The scheduling process requires just 3 clicks to complete.
Web App
Web App
Dashboard
The Dashboard consists of a clean summary of most relevant information and quick access to chat and patient statistics.
Patient Profile
The most important part of the doctors app as it keeps track of all the critical patient data.
Colors help to attract the attention to places requiring some action.
Patient List
The Table view of all the Patient List includes their recent statuses.
I also took into account the ability to sort and search for patients.
What's next ?
What’s next?
While developers are busy implementing the MVP, Lytich Health is planning to revisit the designs and spend more than the initial 2 months on the user experience, polishing and solving complex issues such as billing and multiple doctor consultation
01
Takeaways
Things to reflect on and learn from
Lytich Health started developing the app some time before I was brought on-board, and as such they had no product direction beyond founders’ ideas. They focused on creating features rather than a consistent and helpful user experience, essentially wasting a lot of time on rewriting the application after my designs were validated and handed over for implementation.
Proof-of-concept before the product
02
Even when you think the sprint goals and priorities are on point, there might be something that could wedge in and derail the timeline. In our case it was the initial lack of consistency when it comes to founder’s priorities. Eventually we managed to get things going by agreeing to stop moving the goalposts half-way through each sprint.
Prioritising can be hard
03
Once we got to the prototyping stage, I decided to use Overflow, a relatively new prototyping tool that’s quite fast for linking up artboards. Unfortunately, I did not realise that Overflow does not work well on mobile, where the prototype would be showcased. This meant switching back to Adobe XD, as it delivers a more consistent mobile experience, and as such redoing some of the work.