Care Coordination at Amazon Health
Lead Sr. UX Designer & Researcher
June 2024 - May 2025
I led design strategy for Amazon Health’s first cross-service care coordination platform. Presented the work to SVP and VP leadership across three organizations and helped launch a system that connected thousands of people in just 4.5 months.

The Problem
Every day, millions of people step in to care for someone they love, yet our healthcare system often makes that harder than it needs to be. When Ana wants her son Diego to help manage medications, the process involves forms, phone calls, long waits, and repeating the same steps for every provider. Many people eventually give up and share passwords instead. It works in the moment, but creates real security risks. At Pillpack, we saw that about 15% of customers already relied on someone else to help manage their medications, pointing to a broader need for care coordination across Amazon Health.
Design Principles
Care receivers own the keys
Design for the relationship, not the system
Boundaries protect trust
Think system, not use case
Understanding the Problem Space
To design something that could work across Amazon Health, I spent time understanding how people actually help each other, how products describe those relationships, and where people struggle in real caregiving journeys.
Relationships Landscape
Looking at Amazon household data, I noticed relationships shift over time. To make that visible, I created a visual map of household structures and connections. Spouses support each other, adult children coordinate care across states, and neighbors step in for everyday tasks like picking up prescriptions. Yet healthcare systems often reduce all of this to a single label: "caregiver."
Real care relationships are fluid, and a single role label cannot capture that complexity.
Language Landscape
To understand how other products handle this, I analyzed 50 health and wellness apps and mapped the roles they use for people who help manage care. The pattern was clear. Products are slowly moving away from rigid clinical roles and toward language that reflects real relationships.
Fixed role labels may make it harder for people to see themselves in the system.
Personas & Journey Maps
Building on the earlier generative research, I synthesized the patterns into three caregiver personas and journey maps. They helped the team see how different caregiving situations create different needs, pressures, and opportunities for support.

Design Decisions
I designed the core care coordination experience and interaction patterns that allow people to safely involve someone they trust in managing medications. Presenting to 1 SVP, 3 VPs, and 2 Directors across three organizations, I pushed for three decisions that shaped the platform:
Action Based Language
Reducing Friction to Enable Helping
Accessibility From Day One
The Experience






Invite someone to help
Add up to six trusted people with a mobile number, with entry points throughout the experience so it’s easy to start anytime.
Verify quickly and securely
Verification takes seconds using a date of birth and phone number match, keeping access secure without adding friction.
Stay oriented while helping
A clear “Shopping for [name]” indicator keeps context visible across Amazon Pharmacy.
Manage medications together
Place orders, manage prescriptions, and handle insurance and programs, all from separate accounts without sharing credentials.
Stay informed and in control
Every action triggers notifications, and access can be updated or revoked at any time through a dedicated Health Access dashboard.
Validation Research
I ran two usability studies with 16 people, testing both the care receiver and helper experience. Both studies used Figma prototypes with people who help manage medications for loved ones, or receive that help.
The invitation flow scored high across the board: 100% task completion, 4.75/5 ease rating. People appreciated that all they needed was a name and phone number.
But the studies also surfaced three problems I needed to fix:
Finding settings was too hard. People averaged 18.75 clicks to find health access management, buried in a menu. I worked with the dashboard team to add a direct entry point, and by week 24 it drove 77% of all traffic to the feature.
Insurance during signup confused people. 87.5% of helpers questioned why they needed to enter their own insurance when they were just helping someone else. I removed the requirement from initial signup and moved it to a later stage.
Profile switching needed a nudge. Helpers needed to understand they were now acting on someone else's account. A bottom sheet shown right after signup achieved 100% task completion in 30 seconds, with zero confusion afterward.
"The simplicity of it is very nice and just the straightforwardness, it's really nice just to be like, I just need a name and phone number and we can get the person authorized to help you... not having to fill out like giant forms to do it. Um, I really like this."
— Research Participant
Results & Impact
Conversion rate
High conversion showed the experience felt simple and trustworthy for people helping someone they care about.
New customers acquired
Many people receiving help were new to Amazon Pharmacy, expanding the platform beyond existing customers.
People helping placing orders
People helping weren’t just added to accounts. They actively managed medications.
Faster than projected timeline
Adoption grew faster than forecast as people began inviting trusted helpers.
Reusable infrastructure
Designed to work across services, not just Pharmacy. Teams are now building on this foundation as care coordination expands to additional Amazon Health programs.
Design patterns adopted
Authentication, MFA, and relationship picker components became reusable patterns across health experiences.
Accessibility practice
Established accessibility office hours and pre-launch play sessions now used by teams across Amazon Health.
What's Next
I authored the product vision for how care coordination scales across Amazon Health, with one core idea: make involving trusted people in your health as natural as sharing Prime benefits. Not a crisis response, but something people do proactively. Teams are now building on this foundation as care coordination expands beyond Pharmacy.
What I Learned
Pick your battles strategically
Inclusive language expands markets
Platform thinking from day one
More case studies

Identity Verification at Amazon
Lead Sr. UX Designer
I redesigned identity verification across Amazon, bringing it in-house so customers never have to leave Amazon's environment. The new system maintained 80% completion rates while reducing Pharmacy cancellations from 10% to 2%.
View case study
Designing COMET at Amazon Care
Lead UX Designer
Created the first comprehensive process map of clinical operations, revealing invisible chaos across 8+ teams and driving strategic platform decisions that scaled Amazon Care from 100K to 1M members.
View case study
Kindle Library Experience
Principal UX Designer & Design Lead
I led a platform-wide redesign introducing smart badges, automatic read/unread tracking, adaptive filters, and clear notifications to help readers organize and track hundreds of books. The improvements boosted the iOS app rating to 5 stars and helped millions focus on their next great read.
View case study