Designing Symptom-Based Booking: Patient21 Case Study
Explore how Patient21 used AI and symptom-based UI to resolve organizational conflict and improve online medical booking conversion and clinic safety.
Case Study: Patient21
From Organizational Conflict to Symptom‑Based Booking
Lead / Principal Designer
1. Context & Mandate
Company: Patient21 (70+ mixed-discipline clinics)
Role: Lead / Principal Designer
Mandate: Increase online booking success while aligning business efficiency, clinic operations, and medical quality standards.
2. The Structural Conflict
The CEO's Goal
One single, extremely simple booking entry point to maximize conversion.
The Clinics' Reality
Detailed medical treatment lists to avoid operational risks and misbooking.
“We are not choosing between simplicity and safety. We are failing because we are asking users to think like doctors.”
3. THE REFRAME
4. Validating the Hypothesis
Key Insight: The Language Gap
“I have a sharp pain near the back.”
“It hurts when I drink cold water.”
“Something broke off while eating.”
Methodology: 16 usability interviews • Funnel drop-off analysis • Clinic call logs review
5. The Solution: Symptom-Based UI
Starts from user language (symptoms)
Adapts in real-time (Dynamic Form)
Asks only what is clinically needed
6. Why AI Was Critical
AI was not a feature — it was the translator.
Symptom → User Intent
Intent → Medical Logic
Logic → Triage Routing
7. Governance: The RACI Intervention
As momentum grew, progress slowed as everyone wanted a say. I introduced a clear framework to restore velocity.
Experience Strategy
Design
Medical Logic
Chief Medical Off.
AI & Tech
Engineering
8. Business & Medical Impact
< 2 min
Avg Booking Time
10. Core Leadership Learnings
Handle conflict by reframing the problem, not negotiating the UI.
Lead through decisions and ownership, not facilitation alone.
Use AI strategically for structural change, not cosmetically.
- case-study
- ux-design
- product-leadership
- healthcare-ai
- medical-booking
- conversion-optimization
- raci-framework