Tablz summer 23
Creating a smooth restaurant discovery experience for customers by designing Tablz’s search and booking flow from 0 - 1
Summary
timeline
12 Weeks
role
Lead Designer
process
Tablz is a restaurant booking portal leveraging 3D technology to showcase tables in a more immersive, visual format.
During my 4-month internship, I co-led the design of a web-app that lets customers discover restaurants using visual previews and seamlessly book a table—all centralized rather than through disparate restaurant sites.
Result
Over the time of 3 months, I rebranded and redesigned the whole platform and shipped it, contributing to 30% user growth within 1 month and a 25% increase of adoption rate.
User Growth
30%
new users starts using Data Platform after the 2 weeks of the first launch
Task Completion
27%
increase in completing the task of requesting a data asset from landing page
01
Define
Tablz's current product - 3-directional portal for restaurants - is underused
Tablz’s current product, 3DR, allows users to explore the full 3D view of a restaurant before booking a table. However, The technology was severely underused. Most users still booked tables through Google Maps links instead of exploring inside the product. This showed that the immersive 3D feature wasn’t integrated into the core booking journey, and needed to be rethought to make discovery feel more engaging and natural.
Hence, we asked…
How Might We
Help users explore and reserve tables based on experience preferences?
How Might We
Design a platform that highlights restaurant ambience while enabling efficient booking?
02
Understanding user personas
Diving into our ideation process, we interviewed 9 users across 3 personas: Experience Seekers, Occasion Planners, and Business Diners.
🥐️🍽️
Experience Seeker
📅
Occasion Planner
👩💼💻
Business Diner
Research insights
Based on the interviews, we gathered the following insights, which will help us to define our HMW statements for ideation:
7/9
of respondents find current reservation platforms complicated
8/9
uses location and pricing filters to help them narrow selections
6/9
of respondents find visual of restaurant helpful for selections
5/9
do not prefer to open external link to reserve a table
Card sorting: deciding on 3 flow - landing, search and booking
We developed the information architecture through a card sorting exercise, grouping features into must-haves, nice-to-haves, and backlog. User interviews highlighted the need for effective filters and search parameters, so we included them on both the landing and search results pages. After several iterations, the team agreed on the final set of filter options.
Developing design goals from card sorting - focusing on search flow
Summarizing the objectives of the design and the research conducted, we established three main design flows:
01 landing flow
Highlights the unique dining experiences of each restaurant to inspire exploration
Separates restaurant and table views while integrating the 3D portal for immersive discovery
03 Booking flow
Provide clear, detailed information to support confident and seamless reservations
I focused on designing the Search flow, which included structuring filters, defining restaurant/table views, and integrating the 3D portal into exploration.
03
Restaurant vs. Table view: combined or separate?
For the restaurant search flow that I led the design for, I explored two patterns: a combined restaurant/table view and a separate view. The team loved Design B—separate views made everything clearer with dedicated filters and features, while still letting users preview tables right from the restaurant page for easy, flexible booking.
04
Switching between restaurant and table view
By toggling between the restaurant view and table view, users can easily explore all options that match their search parameters.
They can then choose to click on the 3D View button, which opens an immersive portal to preview either the entire restaurant or a specific table.
Restaurant filter vs. Table filter
Based on the differences between the two views, I tailored the filters to match user needs.
For the restaurant view, filters include cuisine, price, accommodation, and experience (e.g., live music or game nights).
For the table view, filters include dynamic pricing, vibe (e.g., spacious or private), and seating.
04
Takeaways
My learnings
Conducting user interviews
This was my first attempt at user interviews, where I explored user needs through recruiting participants, creating interview plans, and writing scripts. Along the way, I tried methods like laddering and started to build a foundation for asking better questions.
Organizing Workflows
I learned that designing isn’t only about aiming for the perfect long-term solution. Coming up with practical, short-term fixes that address immediate user pain points can be just as impactful.