Scaling Welldoc’s Impact from Mobile-First to Platform-Agnostic Health Management

How strategic research and iterative design thinking helped extend a successful mobile health app to the web, increasing user reach while preserving clinical effectiveness.

Project Impact

Extended market reach through web-responsive design that captured previously underserved user segments to maximize total addressable market.

Accelerated time-to-market through rapid solution generation and cross-functional alignment, enabling agile decision-making that reduced development cycles while maintaining quality standards.

Validated MVP approach that informed the product roadmap for the next 18 months

OVERVIEW

The Challenge

Welldoc's mobile app had proven successful in helping patients manage chronic conditions, but we were missing a significant portion of our target demographic. They wanted to build on this by extending these capabilities to a broader platform through a dedicated web interface.

The heart of the problem: How do we extend mobile app functionality to web without diluting the focussed, clinical experience that made the mobile app successful?

My Role

User Experience Designer
Created a conceptual model to guide information architecture decisions.
Designed iterations of low and high fidelity wireframes.
Ensured responsive design across all devices and screen sizes.
Ensured visual consistency with Welldoc's brand identity and user experience.

Tools
Figma
Axure RP
Google Meet

Team
UX Consulting Team: (Mr. Daniel Rosenberg, Cayce Huang, Shanivi Gupta)
Client (Stakeholders at Welldoc): Senior executives, Business Analyst, Senior UX Designer, Product Manager

Timeline
8-months, delivered in 2 strategic phases

DESIGN
Understanding Welldoc's mobile DNA

The first step was getting my hands dirty with the app itself. We conducted a comprehensive heuristic evaluation to understand it's strengths and weaknesses ensuring we built on what worked while preventing any usability issues from multiplying across platforms.

Screens Evaluated

50+

across mobile app

Critical Findings

25+

high-impact improvements

Strategic Discovery

Our approach was to understand the fundamental differences between mobile and web user contexts.

Following initial discussions with the internal Welldoc team, we set out to design a web portal that not only mirrored the mobile app’s core functionality but also introduced enhanced features like a robust analytics dashboard.

Early Wireframe Exploration

We began by brainstorming various ideas for designing the portal. We envisioned a dashboard-heavy portal for data analysis on desktop, with mobile optimized for data entry: balancing user workflow with business requirements.

In this phase, we focussed on:
• Home page to function as a central analytics dashboard
• Optimal navigation for comprehensive data views
• Essential analytics and widgets to be included
• Cross-platform data sync and consistency patterns

Design decisions:
1. Preserve familiar patterns - Maintained the existing information architecture to leverage users' established mental models
2. Maximize screen real estate - Adopted a three-column layout that takes full advantage of desktop capabilities
3. Enable responsive flexibility - Chose top navigation to seamlessly adapt across devices, supporting our cross-platform strategy

Narrowing Scope

In this iteration, the idea was to divide the home screen into three columns and each column would be dedicated to important analytics:

1: Symptoms - Real-time symptom tracking and trends
2: Feed -
Mirroring the mobile app experience
3: Meals -
Nutrition logging and dietary pattern analysis


Each designer on the team took charge of one column. I was responsible for meals and started off by brainstorming the various widgets and analytics that could be included in the design. These were the top ideas:

01
Track Macros

Mobile users logged meals but couldn't easily interpret their macro intake patterns. I enhanced this data visibility on the web platform to transform raw food logs into actionable nutrition insights.

02
Explore Recipes

This popular mobile feature needed prominent placement on web to maintain cross-platform consistency and support users' meal planning workflow.

03
Plan Meals

WellDoc's new meal planner was perfect for web's "analysis" context. I featured it prominently to encourage adoption and support the planned integration with meal recording.

04
Record Meals

Meal logging was the most valued feature for chronic condition management. I made this directly accessible from the home page to ensure users who prefer web interfaces can easily track their nutrition data.

After finalizing these widgets, I started brainstorming various design ideas to effectively represent the data by exploring different layouts and visual elements.

I explored and refined various widget designs to ensure they aligned with both user comprehension and business objectives. Ultimately, I narrowed it down to two strong options. After collaborating with my team, we decided on a final design that combined the best elements of both options.

Final Sketch and Wireframe
The best laid plans of mice and men often go awry...

During stakeholder review, business priorities had shifted.

They wanted a simple, fast launch (MVP) instead of a complex analytics platform.

Instead of viewing this as a setback, I realized we could test our hypotheses quickly and cheaply, then build the right features based on real user feedback.

THE STRATEGIC PIVOT

Upon recognizing the misalignment, the UX team knew a significant shift in approach was necessary.

This led to a pivot towards a user-centric redesign based on business goals, industry best practices, user needs and the current product life cycle phase. Traditional user research methods were not employed due to lack of resources. We broke the problem and thought of a solution that lies at the intersection.

How might we deliver meaningful user value with minimal development effort, while collecting insights to guide future iterations?

Gathering Business Goals

The simplest way to learn about business goals was to ask. So, we met with Business Analysts, Product managers and the VP to understand their goals and expectations:

1. Cater to a broader user base
2. Retain core functionalities, maintain consistency with existing design system and ensure familiarity for users
3. Meet customer expectations by offering the anticipated web portal

Market Context

1. Competitor Analysis: Researched major competitors' strengths and weaknesses, focusing on established industry standards

2. Cross-Industry References: Drew inspiration from web platforms like LinkedIn and Facebook for responsive design patterns

Collaboration with Human Factors Engineer
‍‍
1. Analyzed past demographic reports and user testing recordings

2. Reviewed FDA guidelines for emergency use cases and accessibility standards

Second Design Iteration

1. Streamline Information Architecture by deciding hierarchy of information
2. Maintain a consistent visual and functional relationship with the mobile app
3. Provide insightful health analytics to test for the MVP

01

NAVIGATION: SOLVING FOR COGNITIVE LOAD

Challenge: Mobile app's tab based navigation didn't scale to web's information density.

Solution: Three-tier navigation system that progressively discloses information

Primary Navigation: Core functions (mirroring mobile for familiarity)
We also added a global enter button to allow for easy data entry.
Secondary Navigation: Context-specific tools
Tertiary Navigation: Deep dive features

02

RESPONSIVE DESIGN

Challenge: Designing for both tablet users in clinical settings and desktop users at home

Solution: Designed "Context-aware" layouts

Responsive cards
Break points for screens
Responsive spacing between cards

03

ANALYTICS DASHBOARD: MVP Approach

Rather than building a comprehensive analytics, I designed a focussed dashboard that addressed the top 3 user needs identified in research:

1. Trend Visualization: Simple line charts showing key metrics over time
2. Goal progress tracking: Visual indicators of patient adherence
3. Anomaly highlighting: Automated flags for concerning patterns

04

DESIGN SYSTEM COMPONENTS

Built a cohesive design system for the web interface, drawing significant inspiration from the mobile app. This ensured consistency across platforms without cognitive friction or interface confusion.

MEASURING SUCCESS AND IMPACT
Strategic Business Impact

Expanded Addressable Market
by supporting users who previously couldn't use mobile-only solution

Reduced Development Risk
by aiming to validate core assumptions before major feature investment

Created Data-Driven Roadmap based on actual user behavior rather than assumptions

Strategic Lessons
Flexibility and Speed

This project taught me the importance of being flexible in the design process to adapt to changing requirements. When we encountered misalignment with our client, we collaborated effectively with PMs and engineers to realign and stay agile. By iterating quickly, we were able to respond effectively to the new opportunity.

Leveraging Past Research and Industry Standards

It was a setback when we learned that the company didn't have the budget for new research. However, we leveraged past research and industry standards to work within these limitations. This experience showed me that it's still possible to deliver effective and informed designs with limited research. We provided multiple solutions to problems based on existing knowledge and best practices.

Balancing Business Goals and User Needs

I learned to balance business goals with user needs for successful product design. Our team ensured a consistent and inclusive user experience across all devices while supporting business strategies.

Going forward from here

As next steps, I would like to measure the success of the product once it goes into production, and more specifically, the engagement metrics and other analytics.

Understanding if users are satisfied with the experience and how many active users are using the platforms

Analyzing Cross-Platform Behavior: Understand how users move between the mobile app and the web portal, and identify any patterns or preferences.

User Segmentation: Segment users based on their preferred platform (web-only, mobile-only, or cross-platform) to tailor engagement strategies accordingly.

Explore more projects