Epic MyChart Redesign
2026
Reimagining patient experience in healthcare
first itinerary explorer and builder on the market
Problem area
Inspired to travel, overwhelmed to plan
Travel planning lived across social feeds, notes, and spreadsheets. The lack of structure turned inspiration into friction, driving hours of manual effort, high cognitive load, and frequent abandonment.
Current state of Travel Planning
Opportunity 1
How might we design a planning system that optimizes for scannability, clarity, and speed of decision making at scale?
Opportunity 2
How might we replace fragmented social search with a unified discovery experience for complete, reusable itineraries?
Redesign goals
What I aimed to achieve
Test Results
Allow travelers to organize an entire trip in one structured, flexible place.
Responsible AI
Ensure itineraries are easy to understand at a glance, especially on mobile.
Design decision 01 - Scheduling
Introducing intuitive scheduling for healthcare visits
The Appointments experience was redesigned to prioritize context aware scheduling, dynamically organizing options based on provider requests, recent visits, demographic signals (age and gender), and historical care patterns, while ensuring all recommendations remain within the patient’s provider network. The goal of this enhancement is to guide patients toward relevant care pathways without introducing cognitive overload.
The design leverages progressive disclosure and clear information hierarchy so recommendations feel supportive rather than prescriptive. The interface prioritizes upcoming visits first, followed by provider initiated requests, system generated recommendations, history based visit suggestions, and past appointments. This structure helps patients quickly distinguish what requires immediate scheduling versus care that can be deferred, improving clarity and decision confidence.
Top KPIs selected
Completeness
Full, end-to-end itineraries instead of fragments
Credibility
Social proof and real world usage signals surfaced early
Adaptability
Itineraries designed to be edited, saved, and built upon
Actionability
Clear pathways from discovery → itinerary building
Design decision 02 - Planning
Ditch the spreadsheet, plan a polished itinerary
Research showed that even after finding inspiration, travelers struggled to organize an entire trip in one place. Existing tools were either too rigid or too complex, pushing users back to spreadsheets, notes, and documents that were difficult to maintain, edit, and reuse.
I designed a structured yet flexible itinerary system that balances clarity with customization. The mobile first planning flow provides enough structure to organize a complete trip while preserving user control, removing the need for spreadsheets without introducing friction.
1. Structured itinerary framework
Guides users through a full trip timeline without enforcing rigid templates.
2. Lightweight customization
Enables easy reordering, editing, and duplication without breaking structure.
3. Mobile-first planning flow
Makes itinerary building fast, usable, and maintainable on the go.
Design decision 03 - Scannability
Designing itineraries to be understood at a glance
I explored two directions: information dense itinerary layouts that surfaced everything at once, and scannable layouts that emphasized hierarchy and progressive disclosure. After testing the prototype with our key persona, I chose clarity over density because travel plans are most often referenced on mobile, in motion, and under time pressure.
The scannable approach reduced cognitive load by surfacing what mattered most: day, location, and key activities, while allowing users to dive deeper only when needed. This helped travelers quickly assess trip readiness and feel confident the itinerary was complete.
Version 01: What I learned testing with travelers: dense itineraries failed on mobile
Learning 01
Poor hierarchy increased cognitive load: Travelers had difficulty understanding their plans quickly while on the move.
Learning 02
Incomplete itineraries appeared “done”: Without hierarchy, users assumed trips were complete when they weren’t.
Retrospective
