Turning slot selection into a confident decision
As Playo grew, booking became harder than it needed to be. Users found venues but hesitated at the final step of choosing a slot.
Users could find a venue and reach the slot selection screen, but making the final decision wasn't always straightforward. They had to figure out when their session would end, how long they were booking, what they would pay, and whether they were getting the best available option.
The existing slot selection — users had to mentally calculate end time and duration
The opportunity wasn't to add more information. It was to make the information already available easier to understand at the moment of decision.
Three separate data points — time, duration and price — needed to become one connected understanding
We tested multiple approaches before landing on a solution that made time and duration immediately understandable.
Design explorations — different approaches to simplify slot comparison
The dual pointer timeline changed how users understood their session. Start time, duration and end time became one connected interaction.
The dual pointer timeline — start time, duration and end time in one connected interaction
Once the core time selection was simplified, we looked at the decisions around it. Date, price, rewards and booking context were redesigned to help users move forward without second guessing.
Plan your game with clarity. See the real-time availability and pick the exact time that works for you.
We surfaced venue specific offers at the moment users were deciding, making promotions easier to discover without interrupting the booking flow.
When a user's preferred slot wasn't available, we didn't treat it as the end of the journey. We surfaced nearby venues with availability for the same time.
We introduced insurance during checkout, giving users an additional layer of protection while creating a relevant opportunity to opt in at the moment of purchase.
The redesigned experience improved conversion and helped more users move from selecting a slot to completing payment.
Launch validated the core experience, but real usage uncovered behaviours we hadn't anticipated. Those became the next opportunities to improve the journey.
Post-launch iterations — handling edge cases surfaced by real usage
We removed the uncertainty that was stopping people from finishing it.