Elevance Health · Maya Project
Design sprint documentation
Summary of the multi-day design sprint used to align Elevance leadership and Lurie Children’s clinical staff on a remote post-operative care concept before traditional scoping began.
Background
Maya was a partnership between Elevance and Lurie Children’s Hospital in Chicago to explore remote post-operative care for pediatric patients. The goal was to discharge patients sooner, let families recover at home, and reduce the cost of extended hospital stays while giving parents and clinicians a way to monitor recovery.
The default product path would have been top-down direction from a VP, requirements gathered by a business analyst, scoping by a PM, and UX delivering screens against that scope with limited usability testing at the end.
Sprint challenge
Validate whether a virtual post-op monitoring experience was viable for pediatric patients and their care teams, and secure alignment from senior executives and Lurie clinical leads before committing to a full build.
Participants
- Elevance senior executives
- Lurie Children’s clinical leads
- UX team (facilitation, prototyping, synthesis)
- Product and innovation partners
Process
- Understand. Reviewed the clinical and business context for early discharge and home recovery monitoring.
- Map. Mapped stakeholder concerns, patient/guardian touchpoints, and constraints around virtual care.
- Sketch & decide. Explored multiple directions and converged on a core enrollment and monitoring flow.
- Prototype. Built a clickable proof of concept focused on hospital enrollment, patient ID validation, and recovery monitoring.
- Test & review. Walked executives and clinical partners through the prototype in session.
Outcomes
- Shared product direction and executive/clinical buy-in before BA-led scoping
- Proof-of-concept prototype (not a production-ready deliverable)
- Agreement to follow the sprint with a formal research plan, clinician interviews, and scoped estimates
The sprint prototype is shown in the Elevance case study as a screen recording. It reflects direction from the sprint, not final visual design or production requirements.