Medical clinic network
Redesigned multi-step booking and account-area flows for a clinic network, focused on mobile form effort, appointment confidence, and return-patient continuation.
Case snapshot
- Outcome
- +38% booking completion
- Timeline
- 19 days
- Proof level
- Anonymized client result
- Scope
- Booking journey review + Mobile form hierarchy
Client context
The case starts with the decision a real user has to make, not the design deliverable.
Situation
A clinic network needed patients to complete a multi-step booking journey across service selection, account steps, mobile forms, and confirmation states.
Question to answer
Where does the booking path ask for too much effort before the patient feels confident that an appointment is actually being secured?
Friction found
The problem statement is written as user-facing hesitation, not a generic redesign brief.
Patients were dropping out across a multi-step booking flow where service choice, account steps, and mobile form effort competed with appointment completion.
What changed
Each case is framed around visible product experience and the fixes a team can actually ship.
- Simplified the booking path around the next required patient action.
- Reduced mobile form friction and clarified confirmation states.
- Reworked account-area hierarchy so returning patients could resume faster.
Scope
The work is framed as a bounded review or implementation path, so the next step is easier to price and approve.
- Booking journey review
- Mobile form hierarchy
- Account-area continuation states
- Confirmation and recovery-state copy
Proof and limits
This section separates what can be verified from what is kept private or shown as a sample.
Measurement
+38% booking completion is client-reported against the previous booking flow. Raw analytics and clinic identity are not public.
- The client-reported result compares booking completion against the previous flow.
- Client identity and raw analytics are kept private because this was a healthcare engagement.
- The current visual artifact is an open-source booking UI placeholder until redacted client screens can be published.
Anonymized client case. Result is client-reported against the previous booking flow.
Artifacts
Temporary open-source placeholders are labeled below so they can be replaced with client screenshots later.
Related case studies
- E-commerceVehicle styling services · ShopifyPublic Shopify refresh · clearer service discovery · 2 weeks
- AI-built appsAI-built MVP · launch-readiness reviewLaunch blockers separated from polish · 2 days
- UX auditReward-based digital experience · UX auditClarity risks turned into a prioritized roadmap · 3 weeks
Have a similar flow to review?