Review & Book
Rebuilding a critical booking step and recovering from an underperforming launch
Project overview
After an initial effort to improve qualification earlier in the booking flow failed, the Conversion team re-sequenced the work toward Review & Book, the final step of booking.
I became the primary design owner for rebuilding the experience, moving one of Zocdoc’s last major legacy surfaces onto newer architecture and its updated design system while addressing a roughly 30% drop-off.
When the first MVP underperformed, I worked across Product, Engineering, and Analytics to understand why, then redesigned the experience around a simpler model that ultimately recovered conversion.
Date
2022-2023
Role
Senior Product Designer
Team
Product, Engineering, Analytics, UXR, Design Systems
Scope
Desktop/ mobile web, Booking-flow strategy, Review & Book redesign and migration, MVP definition, usability validation, experimentation, diagnosis, and redesign
Outcome
+2.7% booking conversion on desktop and +1.9% on Mobile Web, representing roughly 2,700 projected additional bookings per month.
Understanding the conversion problem
The newly formed Conversion team was tasked with improving Zocdoc’s “booking flow”: after selecting a timeslot, a patient either logged in or went directly to Review & Book.
Only about 70% of patients who reached that final step completed their booking. Errors, late qualification requirements, and weak recovery states could still interrupt patients just as they made it all the way to our highest intent page.
But just because those problems surfaced on Review & Book did not mean they began there. We needed to understand how the earlier parts of the patient’s journey fit with this moment, and where the friction was coming from.
Patients could select an appointment, reach the final step, and only then learn that the time was no longer available, revealing a problem that began earlier in the booking journey.
Making the booking journey visible
I mapped the booking journey across desktop, Mobile Web surfaces, and iOS, and Android platforms to understand where information entered the flow, how those inputs interacted, and where breakdowns emerged.
The result was the first end-to-end view of the booking journey in one place, giving the team a shared reference for understanding how the system fit together. It also made it easier to see that some problems appearing on Review & Book were connected to information collected earlier in the journey.
The map connected the booking journey across platforms, making it easier to see where information entered the flow and how downstream problems could emerge from earlier steps.
Finding where the final step broke down
With the broader journey mapped, I turned back to Review & Book itself. I identified more than 30 usability issues across hierarchy, editing, errors, and recovery.
The harder problem was understanding the error experience. There was no shared view connecting backend error states to what patients actually saw, so I worked with Product to map those errors back to their UI states and understand where recovery was breaking down.
Mapping the existing journey helped make the dependencies between qualification, availability, and Review & Book visible.
Even at their lowest point, some patients were turned away and left without any clear path forward
Mapping the existing journey helped make the dependencies between qualification, availability, and Review & Book visible.
Rethinking when qualification happens
The work surfaced a structural problem: patients could select a provider and appointment before Zocdoc had enough information to know whether that appointment was actually valid. Important inputs like insurance, visit reason, patient status, and provider requirements were often collected later, with limited guidance about how changing them could affect availability. That could leave patients facing conflicts or dead ends on Review & Book.
The broader question became a tradeoff: Should we qualify patients earlier to make availability more reliable, or preserve easy access to times and build stronger guidance and recovery later?
I designed three Booking Vision concepts that explored different points along that spectrum.
Testing qualification earlier
The team chose Step-by-Step as the longer-term direction, and I designed an Insurance Stepper to test collecting insurance before timeslot selection.
The experiment did not improve overall conversion. We suspected friction in the existing insurance picker was adding enough friction to obscure the value of collecting insurance earlier.
Rather than continue investing upstream, the team changed the near-term goal: improve conversion at the end of the funnel first.
Mapping the existing journey helped make the dependencies between qualification, availability, and Review & Book visible.
That work also surfaced smaller improvements we could address immediately while the broader booking strategy continued.
Before vs after low hanging fruit improvement
Direct to Cart: Keep entry into booking fast. Patients select an appointment early, then provide qualification and personal information as they move through Sign-up and Review & Book. This preserves momentum and patient autonomy, but requires stronger guidance and recovery if new information changes the appointment they selected.
Step by Step: Turn booking into a more guided sequence. Key information is collected progressively, with more context about why it matters and how it affects the appointment. The goal is to balance easy access to booking with enough qualification to reduce surprises later in the flow.
Gatekeep Timeslots: Collect more qualifying information before exposing exact appointment times. Patients see availability only after Zocdoc has more confidence that the provider and appointment are a valid match. This makes availability more reliable, but introduces more friction before a patient can choose a time.
The experiment tested earlier qualification, but friction in the existing insurance experience made the effect of timing difficult to isolate.
Rebuilding a legacy booking surface
With the team now focused on the end of the funnel, I took design ownership of rebuilding Review & Book.
It was one of Zocdoc’s last major booking surfaces still running on legacy technology, with years of qualification rules, provider requirements, editing behavior, and recovery states layered underneath it. The challenge was to create a simpler patient experience while that underlying complexity still had to be supported.
Shaping the new experience
I started mobile first, breaking the legacy page into its underlying content and interaction blocks rather than reproducing the existing layout screen for screen.
From there, I explored different ways of grouping and arranging appointment, patient, and insurance information, along with how much provider and appointment context patients needed at the final step.
These explorations helped me work through the page hierarchy before moving into the detailed MVP design.
I explored different ways of grouping and arranging appointment, patient, and insurance information to create a clearer hierarchy and a more direct path to booking.
The legacy page looked relatively straightforward, but each section sat on top of years of booking rules, dependencies, and exception states.
I used lower-fidelity content blocks to work through hierarchy, grouping, and interaction structure before committing to the final interface.
Appointment editing had previously been scattered across the page. I explored ways to consolidate those controls and simplify how patients reviewed or changed their appointment.
Because the page and its many use cases still lived on the legacy experience, the rebuild also meant bringing Review & Book onto Zocdoc’s current design system. Throughout the process, I worked with the Mezzanine design system team on components and edge cases the system did not yet support.
Phase 1 MVP
Rebuilding every legacy rule and exception at once would have made the project too large to learn from quickly, and bringing all the use cases out of the legacy experience would be a big undertaking. I worked with Product and Engineering to define a narrower first release focused on the core booking path.
Patients arrived with key booking inputs visit reason, patient status, and insurance already established, then reviewed the information needed to complete the booking. The exception was new and eixsiting patient. which would provide an error and a new path to recovery.
More complex scenarios and edits that the new system did not yet support still returned patients to the legacy experience, making Phase 1 an intentionally transitional system.
Phase 1 moved the core booking path onto the new experience while unsupported scenarios temporarily remained on legacy Review & Book.
The MVP moved the core path onto the new system while leaving an escape hatch to legacy for interactions it did not yet support.
Making the final step easier to review
The legacy page scattered information, gave most sections similar visual weight, and pushed important details lower on the page, making the final step feel more like another form than a focused review.
For the MVP, I reorganized the experience around what patients needed to verify before booking. Related information was grouped together, secondary content was deemphasized, and appointment details became easier to scan.
Designing beyond the MVP
Phase 1 was intentionally narrow, but it was only the first step in the migration.
While the MVP was being built, I was already designing how more of the booking experience could move onto the new system. That included recovery paths, additional editing behavior, and more complex scenarios such as video visits, mental health appointments, required addresses, subpatients, and referring-physician information.
The goal was to reduce reliance on legacy Review & Book while extending the same underlying framework to a broader range of booking needs.
The new structure separated appointment, patient, and insurance information more clearly while keeping the booking decision in focus.
These explorations extended the new Review & Book beyond the core path, covering recovery and more complex booking requirements before those scenarios were brought onto the new system.
Validating and launching Phase 1
Before launch, I wrote the research brief and ran usability testing around the interactions I considered riskiest, including editing appointment details, completing missing information, and recovering when changes affected availability.
The core interaction model held up. Patients understood the page and were able to complete and edit the information they needed without major usability issues.
We launched Phase 1 in May 2023. The first production read looked roughly flat, but as we dug further into the experiment, it became clear that the new experience was underperforming.
Understanding what went wrong
The negative result did not point to a single cause.
I worked with Product, Engineering, and Analytics to separate implementation and measurement problems from experience-level hypotheses. We investigated legacy redirects, insurance behavior, error states, CTA visibility, platform differences, and how patients were moving through the new experience.
We found several bugs in the build that clearly needed to be fixed, but we also needed to understand which parts of the design might be contributing to the drop in performance.
Simplifying the experience
Once the known implementation issues were addressed, I focused the next iteration on the experience itself.
I redesigned Review & Book around a simpler idea: make the final step feel like a review, not another form to work through.
The two-column layout became a single-column hierarchy. I shortened the page, moved the Book action higher, removed repeated information and unnecessary labels, pushed secondary fields behind links, and made error states more directional. I also narrowed editing and recovery so patients were less likely to trigger cascading availability errors while making changes.
Whenever users hit an issue, we now trigger a modal that directs them to new care. They have much clearer inline options to recover from this last minute roadblock.
The redesign reduced form-like structure and brought the booking action into clearer focus across both platforms.
Something about condensing for a shorter page
The redesign recovered conversion
The redesigned Review & Book improved booking conversion across both platforms.
+2.7% Desktop conversion
+1.9% Mobile Web conversion
Together, the results represented roughly 2,700 projected additional bookings per month.