AutoDine
Timeframe: 1 Week (April 2024)
My Role: Storyteller/User Researcher
Team: Two UX Designers
Methods: Low-fidelity Storyboarding, User Feedback, Mid-fidelity Wireframing
Tools: Google Docs, Procreate, Figma
Product Description
AutoDine represents a groundbreaking approach to dining automation. With its compatibility across multiple devices, AutoDine enhances the efficiency of the in-person dining experience. From pre-selecting a table prior to arrival to facilitating the checkout process, AutoDine serves as a comprehensive dining facilitator.
Storyboards
Patron Storyboards
Server Storyboard
Reservation & Arrival Wireframes
Users are presented with an intuitive interface for browsing and selecting dining options tailored to their preferences. The layout showcases various restaurants. Once they've found the perfect restaurant, the reservation system allows them to book their table, with options for specifying party size, date, and time.
Users are then presented with a convenient QR code feature that enhances the dining experience. When users arrive at the restaurant, they simply need to scan the QR code provided to them. Upon scanning, the screen displays their designated table number, ensuring a seamless and efficient seating process. This eliminates the need for traditional methods of table allocation, such as waiting in line or searching for a host. After scanning, users can swiftly locate their table and start enjoying their meal without any hassle.
Table Interaction Wireframes
Upon arriving at the table, patrons are greeted with a warm welcome, as well as the option to order directly through the tablet or use their smartphones to place orders individually. Each QR code is specific to the table in which the tablet is being used. If the QR code is used, the entire order will show on the checkout menu. On this page, and all pages following, a question mark inside a help button will allow patrons to signal for help if there is any confusion/general help needed with ordering.
Notification that will pop up once a meal arrives with a notification to click to notify restaurant workers to clean up the table to further streamline the process. In future designs, this will require vibrant colors and animations that act as signifiers for patrons.
Confirmation that the order was placed with a progress bar.
A full menu is shown upon clicking the menu button. Patrons can explore the differing food options and see live updates of there cart to the right as they add to their order.
Checkout page gives patrons the option to use credit card, Apple Pay or a gift card code if they have it. Once an order is placed or order is placed via QR code, a ticket is sent to the chefs to complete the order.
Design Justification
The Design Process
To kick off the project our team participated in an initial Microsoft Teams meeting to identify project goals, objectives, and responsibilities. During the first meeting we also established an understanding for each others’ skills to create a cohesive and efficient environment. One team member created the low-fidelity storyboards and obtained preliminary user feedback. Once the feedback was shared with the other members, the information was used to craft two mid-fidelity wireframes. We worked together to address any concerns throughout the process and sought feedback often from one another to ensure cohesiveness throughout the design process.
User Feedback & How it Affected the Design
Feedback
A 24-year-old college graduate and government employee provided valuable feedback on the app. They found the concept intriguing and expressed a definite interest in using it. They highlighted its efficiency and user-friendliness, noting how it saves time by eliminating the need to make multiple phone calls and streamlining the payment process. They particularly appreciated the feature allowing separate payments, avoiding the inconvenience of a forced single check. However, they raised valid questions about the restaurant’s perspective, such as whether establishments would adopt the app and what incentives they might have to do so. They also pondered its appeal beyond Gen Z and raised concerns about the potential impact on the social interaction with waitstaff. Additionally, they questioned the most suitable environment for the app’s usage and suggested the ability to browse multiple restaurants. They observed that not all restaurants use the same booking platform, and expressed a desire for more payment options within the app itself.
Reflection
User feedback heavily influenced the development of the AutoDine wireframes for the ordering experience, particularly emphasizing system efficiency and user-friendliness as highlighted by the user feedback. This led to simplified navigation and enhanced payment flexibility, incorporating multiple options like credit card, Apple Pay and separate ordering via a QR code. Concerns about the app’s broader appeal and impact on social interactions prompted features to appeal to restaurant owners and maintain basic service elements, ensuring the design catered to diverse user preferences and encouraged broader adoption. Future iterative designs should focus on vibrant colors that act as signifiers for patrons to understand the process, as well as transitions in the ordering process giving immediate feedback throughout the process. This user-centered approach in the ordering process wireframe promotes usability and potential for successful implementation, balancing automation with respect for conventional dining experiences.