02 · Lack of Visual & Interaction Consistency.
"The same action looks completely different on three different screens. Users won't trust it does the same thing."
Observation - The audit revealed UHG had an established design system but no mobile-specific components. Without them, developers were defaulting to their own solutions, resulting in UI elements that varied from screen to screen with no mobile consideration.
Hypothesis - Building a mobile component library on top of the existing system would give the team a consistent foundation and remove the guesswork from development.
What We Did
Audited the existing design system to understand tokens and patterns already in place
Built mobile-specific components extending the system, not replacing it
Covered buttons, form fields, cards, navigation elements and interaction states
Documented each component so the US dev team could reference them independently
03 · High Cognitive Load in Forms.
"I always lose track of what I've already filled in."
Observation - Drop-off data from the product analyst flagged enrollment and claims forms as the biggest problem areas. Multi-column layouts designed for desktop were forcing mobile users to scroll both horizontally and vertically, breaking reading flow.
Hypothesis - Mobile users process information linearly. Forcing a multi-column structure on a small screen creates unnecessary cognitive load that compounds with form length.
What We Did
Moved from multi-column to single-column layout, eliminating horizontal scroll entirely
Broke forms into labelled steps with a persistent progress indicator
Added inline validation so errors surfaced immediately, not on submission
04 · Simplifying Navigation Hierarchy
"The features I use most aren't in the bottom navigation. Why are these ones here?"
Observation - Key features were duplicated across the homepage, navigation bar and hamburger menu with no clear logic or order. There were no shared criteria for what belonged where, and it was creating friction both for users and between teams.
Hypothesis - Navigation placement driven by real usage data rather than team opinion would create a structure that was logical for users and defensible to stakeholders.
What We Did
Pulled Google Analytics and Firebase data to identify the most frequently accessed features
Placed the top four features in the bottom navigation bar for persistent, one-tap access
Moved remaining features into the hamburger menu, ordered by usage from most to least
05 · Limited Findability & Discovery.
"It takes me longer to find the record than to actually do the work."
Observation - The app had large data tables but no usable search, filtering or sorting. Users had no way to narrow down what they were looking at, making it difficult to find specific records or take action quickly.
Hypothesis - Introducing search with autocomplete alongside contextual filters, built around the variables users actually care about, would significantly reduce the time spent hunting through data.
What We Did
Ran workshops with different teams to identify the key variables and filters relevant to each dataset.
Introduced search with autocomplete suggestions scoped to relevant content types
Designed filter states that persisted so users did not lose context when switching views
