Restaurant-booking SaaS startup · UX/UI & Product Design
Tavola
The challenge
Tavola's founders knew from their analytics that a large share of users abandoned the booking flow before confirming a reservation, but the product had no design system to test changes against — every screen had been designed in isolation as the product grew.
The approach
We mapped the full booking flow step by step and ran moderated usability sessions with real diners, which surfaced a specific failure point: the date and party-size selector reset itself if a user changed restaurant mid-search. We rebuilt the flow and the underlying component system together, so the fix held across every screen, not just the one it was found on.
The outcome
Drop-off at the date/party-size step fell sharply after the fix shipped, and the new component-based design system means Tavola's own team can now design new screens that stay consistent without a design review at every step.
Booking-flow drop-off, before — 38%
Booking-flow drop-off, after — 22%
Reusable components delivered — 34
“We knew users were dropping off somewhere in the booking flow but not why. The redesign was the first time our data and our design actually agreed.”
