Expanding a weight tracker into an insight-driven health experience
Role
Product Designer
Duration
2 Weeks
Team
1 Product Manager 1 Product Designer 5 Engineers
Making health logging worth returning to by turning each entry into meaningful feedback, visible progress, and lightweight motivation.
Problem & Direction
Understanding the limits of weight-only tracking
Before redesigning the logging experience, I analyzed usage data from My Weight — the existing weight logging feature. Across all key markets, engagement was consistently low. 3–8% of users ever interacted with the feature, and among those who logged their weight, weekly retention dropped below 10%. These numbers revealed that:
Discovery was poor → Most users never found the feature
Perceived value was low → Logging gave no feedback or insights
Habit-building failed → Retention dropped after first log
From a product perspective, this feature was not just underperforming; it was fundamentally misaligned with user behavior and expectations. My challenge was not simply to improve the user interface, but to redesign the experience around behavioral reinforcement.
My Weight data across markets
Behavioral gaps in the existing experience
“What prevents expectant mothers from building a logging habit, and how can we help them succeed?” To answer this, I used Fogg’s Behavior Model to analyze user behavior around My Weight. This states that behavior happens when Motivation, Ability, and a Prompt converge. If any of them is missing, desired behavior is unlikely to happen.
A focused gap analysis revealed key breakdowns across all three components, explaining not just what was lacking, but why users failed to build a logging habit.
Breakdown
Lack of Motivation: No value returned after logging
Low Ability: Manual, isolated input with no context
Missing Prompt: No reminders or in-app nudges
Design opportunity
Show insights, progress, and reassurance
Simplify flow + include comprehensive logging
Add streaks, triggers, and notifications
Comparative UX patterns that informed strategy
To avoid reinventing the wheel, I conducted a focused comparative analysis of 6+ products across pregnancy, wellness, and symptom-tracking apps. The goal wasn’t to copy features but to study interaction patterns that successfully encouraged repeat use. These patterns grounded our design in user behavior, not assumptions.
Key patterns
Quick, low-friction input → higher repeat use
Visual or emotional feedback → stronger perceived value
Streaks and in-context nudges → habit reinforcement
Grouped inputs and icons → lower cognitive load
Contextual follow-ups → increased retention after logging
Comparative analysis
What the redesign needed to change
Usage data showed limited participation and repeat logging in My Weight. Reviewing the existing experience and comparable tracking apps helped me translate these gaps into four design priorities.
Make each entry useful
Provide clear feedback and trends to help users understand their records and see changes over time.
Keep logging manageable
Use straightforward inputs and grouped categories to keep the expanded tracking experience easy to navigate.
Support repeat use
Give users reasons to return through useful insights, visible progress, and lightweight reminders.
Add pregnancy context
Bring mood, symptoms, and notes alongside weight, with relevant insights that connect records to the pregnancy journey.
Design Decisions
Prioritizing features for useful feedback and repeat use
I used the Hooked Model to explore how the experience could support repeat logging: what would prompt an entry, what value users would receive afterward, and what could encourage them to return. This helped connect feature ideas to specific moments in the logging journey.
I then used an effort–impact matrix to balance expected user value with implementation effort and define a manageable MVP scope. The selected features below became the basis for the design explorations that followed.
Key features
Quick logging from the home screen
Healthy-range visual feedback
Streak tracking and reminders
Weekly summary cards
AI insights
Design rationale
Provide direct access to logging, with an overall design target of completing a log in under 15 seconds.
Help users interpret their weight entries in relation to the relevant pregnancy weight range.
Make consistent logging visible and prompt users to return.
Bring recent records together so users can see changes over time.
Offer guidance related to the symptoms users recorded.
Ideation guided by Hooked Model
Giving health insights priority over streaks
The first design exploration aimed to make health insights easier to understand and give users a reason to keep logging. I brought together streak tracking, weekly insights, and categorized logging cards to explore how useful feedback and visible progress could work within one experience.
Team review highlighted changes needed in information hierarchy, scannability, and consistency with the app’s design system. The following decisions guided the next iteration.
Team feedback highlights
Health insights lacked visibility: The streak occupied prominent space while key health information sat below the fold.
Insights were difficult to scan: Related data points were presented separately, making trends harder to recognize.
Insight cards were inconsistent: Card styling did not follow the app’s existing design-system patterns.
Design decisions made in response
Prioritize insights over the streak: Move health insights above the fold and reduce the streak’s visual prominence.
Bring related information together: Adjust layout, typography, and spacing so users can scan the insights and compare data more easily.
Apply consistent card patterns: Align the insight cards with established components and styles used elsewhere in the app.
Reducing header space and making sample data visible
Building on feedback from the first exploration, I revised the hierarchy and presentation of health insights for the second iteration. The aim was to make the information easier to find and understand, including for users who had not yet recorded their own data.
The next team review identified further changes to the header and sample-data presentation, informing the design decisions below.
Team feedback highlights
The header occupied too much space: The title bar and progress elements left limited room for health insights.
The title bar felt inconsistent: Its design did not match established UI patterns elsewhere in the app.
Blurred sample data obscured the value: New users could not clearly see what the insights would offer before recording their own data.
Design decisions made in response
Reduce the header’s footprint: Make the header more compact to give health insights more screen space.
Use the established title-bar pattern: Align the header’s components and styling with the app’s design system.
Show clear sample data: Remove the blur so users can preview the information they would receive from logging.
Final Experience
Bringing health records, trends, and guidance together
Synthesizing insights from multiple design explorations, I delivered a habit-supporting, insight-driven experience that turned passive tracking into an active, rewarding behavior. The Key features include:
Real-time feedback to help users understand whether their weight is within a healthy range.
Clear visualizations for trend tracking across key symptoms and health categories.
Guided engagement with visible CTAs, animations, and sample data to reduce friction.
Motivational tools like streaks, AI insights, and timely reminders to encourage consistent use.
By improving clarity, delivering meaningful insights, and reinforcing habits, the new logging feature, My Health, helps expectant mothers feel informed and in control throughout their pregnancy.
Finding My Health and getting started with logging
To make logging intuitive and lower the barrier to entry, I introduced clearer access points and visual cues that guide user behavior:
A weekly insights preview and a CTA on the home screen encourage daily engagement.
Sample data is shown to new users, demonstrating the feature’s value before first use.
A subtle pulse animation on the FAB directs attention to the logging function within the tab.
These improve discoverability, reduce cognitive friction, and boost first-time and recurring use.
Viewing health records and weight trends
To make health data actionable, I redesigned the insights display using consistent and meaningful visual elements:
Unified card components, icons, and color cues make insights easier to scan and interpret.
Health categories are organized to help users focus on what's most relevant.
A redesigned weight tracking chart provides visual trends and benchmarks based on pregnancy progress and pre-pregnancy data.
This visual clarity supports informed decision-making and strengthens the user's sense of control over their health.
Supporting repeat logging with insights, streaks, and reminders
To build consistent tracking habits, I integrated features that combine motivation and reminders:
Streak rewards gamify daily logging, encouraging continued engagement.
AI insights provide context-specific guidance based on logged symptoms.
Smart notifications remind users to log at the right moment without being intrusive.
These create a positive feedback loop that turns one-time actions into sustainable routines.
Impact
Broader discovery and stronger repeat logging
Early results showed that My Health reached a larger share of active users than My Weight, while people who completed a log were more likely to log the following week again.
1.6–2.3× weekly feature visitation: The share of weekly active users visiting My Health was higher than the My Weight baseline across Indonesia, Vietnam, and the U.S.
2.0–2.7× next-week repeat logging: Across the three markets, users who completed a health log were more likely to return and complete another log the following week.
The expanded tracking options also saw adoption. Of 2,212 logs created in the first week, 81% included symptoms and 69% included mood.
The results revealed a tradeoff: despite higher visitation, a smaller share of weekly active users completed a log. The team considered the broader scope a possible factor, highlighting the need to balance richer health tracking with the effort of everyday logging.
1.6–2.3×
Increase in weekly feature visitation
Share of weekly active users visiting the feature, compared with My Weight.
2.0–2.7×
Growth in next-week repeat logging
Rate of logging again the following week, compared with My Weight.
Reflection
Making the value of logging clear
Expanding weight tracking to include mood, symptoms, and notes made the value of logging more important to communicate. I gave health insights more prominence than the logging streak and used sample data to show what users could gain. The launch results reinforced the need to understand barriers to completing a log before deciding whether to change the explanation, the input flow, or both.
With five engineers involved, establishing a clear point of contact helped resolve questions around data visualization and reduced miscommunication. I would put that coordination in place at the outset of a similar project, so the team has a shared way to raise questions and communicate decisions.