Built a connected care experience for AkosMD, empowering users to book appointments, track health, and access support. Handled feature planning, UI/UX design, and stakeholder coordination in a fast-paced startup setup.
My role
Feature scoping, Research, Prototyping, UI design
Timeline
24 Weeks
Collaborators
CIO, Senior Backend Engineer, Full Stack Engineer
Outcome
Onboarded 5+ Enterprise Clients
Research
To get the context about the Akos Care and the project ahead, I started speaking to different stakeholders and getting necessary data about the Akos care vision and research or any documentation.
Developers
Functionality, Combining different systems and API integrations
Stakeholders, Business & Upper Management
Requirements and Expectations
Patients and Doctors
Making portal user friendly with the necessary features
Key Insights
To get the context about the Akos Care and the project ahead, I started speaking to different stakeholders and getting necessary data about the Akos care vision and research or any documentation.
Competition Analysis
Since the Care portal was meant to be used by employees of our customers (who took Akos Care Plan for their company), I went through an extensive competitor analysis to better understand the industry standards.
7
Major Competitors
Comparison of different features
The Excel sheet has a list of different features that the competitors offer. The data has been compiled and visualized here.
Studying the Interfaces of the competitors
To understand the interaction design of the apps due to different target audience groups.
Key Insights
Incorporating Data Analytics to offer personalized health insights, allowing users to track their health metrics and receive targeted health recommendations.
AI - Assessments and chatbots and API integrations with incorporating documents management
More specialized and customized packages for corporates with preventive and wellness programs
Emphasize on trust and transparency by providing clear, detailed information about care plan, pricing and medical information.
Creating Research Plan
After having gathered enough knowledge, We requested different companies in Smartworks, Noida to volunteer for the interview and inquiry related to their online - healthcare experience and I interviewed a few doctors to get more knowledge about the platform and important features.
After spending hours, I gained better understanding of the usability issues and challenges that the users and the doctors face as well as the use cases of the Online Healthcare platform.
Based on this, I created a research plan
Interview and Inquiry
For on-ground research, I interviewed seven different companies in Smartworks, Noida with different job roles. I observed them using other healthcare products end-to-end tasks and interviewed over 25 users, doctors, care navigators and stakeholders.
Key Insights
Delays in claim approvals frustrate both users and doctors, impacting treatment timelines and user satisfaction.
Doctors struggle with the lack of integration between healthcare insurance platforms and Electronic Health Records (EHR), complicating patient care
Users and corporates report slow response times and inadequate customer support, during emergencies and claim processing
The on-ground reality differs from the business expectations.
Compilation & Analysis
After the Phase 1 completed, we decided to focus on the user flow and architecture of the product.
Tasks
Secondary Flows
User Needs
Feelings
Gain points
Pain Points
Design Opportunities
Ideas
Observations
Dependencies
Flow and Architecture
List of Design features and dependencies
I created a list of changes and ideas along with the stakeholder dependencies. Based on this, I set up meetings with the stakeholders to discuss their priorities and expectations.
Ideation (Wireframes)
For ideation, I started by creating paper wireframes and rough layouts based on the whole research and design features, we finalized
Final Design
Flow 1 - Booking an Appointment
I went through multiple ideation session and iterations for finalising the layouts, flows and screens. Throughout this process, I was collaborating with the developers to better understand what would be possible to create for phase 1 and what wouldn’t as our priority was also on shipping the final product quickly.
Get in touch
Always open to a chat, whether it’s about an idea, a collaboration, or just an interesting conversation. Particularly interested in fast-moving teams solving exciting problems.
Say hi anytime!
Made with Espresso
Updated on June 2025