CloudBar
Intro
CloudBar is the backend website system for DrinkBot. Integrating machine operations, business marketing, restaurant management, maintenance and service, menu design, and customized beverage options into a comprehensive, all-in-one professional service.
It is committed to developing a robust backend system that empowers machine operations and enhances restaurant revenue performance. By incorporating IoT, it allows restaurant owners to effortlessly access all information, ultimately boosting sales performance.
Pain Point
In the early stages of the startup, web design was handled by frontend engineers who adjusted the design based on requests from anyone. However, little consideration was given to the user's logical operations and experience, resulting in an imperfect design that often generated error messages during use.
Taking over this project was somewhat chaotic, as many functions were stuck in the architectural phase. Even though it was known that the current design could confuse users, compromises had to be made due to backend design issues.
The project was affected by personnel changes, as there was initially no project manager to coordinate the project's progress, causing a delay in development.
New Design Guideline
The design team has optimized the previous visual, moving away from dark, engineering-oriented screens. Colors have been changed to clear, easily readable white for a more intuitive experience.
Brand colors have been defined, button components standardized, and improvements made to table and dropdown menu designs to create modular components.
These defined components have been documented, allowing the engineering team to better understand requirements and variations during development, including states and variants.
Menu Management
We offers different menus for large restaurant chains and small to medium-sized restaurants. The menu dashboard page is used to manage all menus used by restaurants. Our goal in designing the entire process is to make the entire process more seamless.
We aim to make it more systematic for account managers to create menus.
The primary purpose is to create and edit menus, set drink settings, and finally deploy them to the machines.
Currently, there are hundreds of menus and hundreds of drink options in use.。 A batch edit feature has been implemented for chain enterprises.
Default Menu Settings
Because of the many options and settings available for Menu settings it is creating a lot of user error when implementing in the field across multiple locations in the same chain. This has resulted in bad drink quality (mis-setup of total dispense), mismatched drink names and bad quality control across the chain.
Research
Through the research with account owner, per the user feedback we found the key problems:
Inconsistent drink settings and menu sort across users from the same chain using the same menu resulting in bad drink quality (improper set-up of dispense amounts) and varying quality across different locations.
Bad drink quality was also caused by the fact that smoothies are always at a default of 10.5oz when they should be 6oz, this caused smoothies to be very watery . This has now been fixed by changing the standard size, but does illustrate why improper drink settings can lead to bad quality.
When launching large chains (P64s) Botrista team members may each be assigned to a particular location(s) and be in charge of helping “launch” them. This may mean teams of 20+ heading out and dealing with each store and setting them up properly on CloudBar.
Goal
We will see a drop in requests to help troubleshoot drink settings and menu sort from the sales teams.
We will see a decrease in incorrect drink settings and menu sort across large chains such as Shipley.