UI/UX + Design Research
Lights Out
Design Sprint Research
Problem
It takes servers a long time to close down their assigned workstation.
Goal
Create an interactive screen for restaurants that will make the closing process fair, easy, and fast for the employees in a welcoming manner.
Proposal
Create a mobile application that will assist servers in completing their assigned workstation faster.
Understanding the restaurant closing process…
In reality, this process isn’t ideal. For example, completeness and accountability could be questioned.
After a serving shift, the manager assigns a closing workstation to each server. Servers close down either the line, patio, restroom, wait station, or sauces.
Each assigned station requires a step-by-step process.
After servers complete their workstation, they ask the managers to check their stations to see if everything is complete.
If improvement is needed, servers will need to fix the mistakes and should be good to go after that.
Sprint Questions
I had various design ideas when I first heard about the project. Sprint questions helped me break down the problem and narrow my possible ideas into these few main points.
If we want to make the application fair to use, what needs to be true?
Accountability + Customizability
If we want to make the application easy to use, what needs to be true?
Organized + Chronological Order
If we want to make the application fast to use, what needs to be true?
Minimal Steps
If we want to make the application welcoming, what needs to be true?
Competitive + Friendly
Lighting Demo
Some positives about Zenput: it focuses on quality execution, allows the users to perform audits, and allows the users to compare performance between stores.
Some negatives about Zenput: un-welcoming tone/not exciting and is geared towards large fast-food chains rather than restaurants.
Interview Questions
By creating multiple questions that might or not lead me to the pain points… I was able to set the tone for the interview. In the end, I found these questions most helpful.
What is the main issue when you close down the restaurant?
What is a determining factor when assigning a closing workstation?
What is usually the problem if it takes an extended time to close?
Do you feel like you go home at a reasonable time? If not, why?
Why is Ruben my user persona?
Ruben is a manager and a server at a restaurant. He’s been serving for about 3-4 years now. Unfortunately, Ruben must go home early because someone usually gives him a ride home, or he has to walk home late.
Pain Points
As a manager, he has to check up on servers constantly
Servers fail to complete their closing workstation fully
Managers aren’t checking over the workstations properly
It takes an hour past closing time to close the restaurant
Managers are unfair when assigning workstations
Goals
Wants servers to close as a team
Wants servers to complete their tasks fully
Wants each workstation closed down properly with no mistakes
Wants everyone to take less than an hour with their closing station
Wants servers to be held accountable for their closing workstation
User Journey Map
How Might We’s
-
![]()
HMW Categories
Fairness, completion, etc., are sub-categories to the problem. Eventually, this method will help me create possible solutions.
-
![]()
HMW's
These are some of the most successful HMWs that I’ve gathered. The majority of the HMWs came from the User Journey Map. I had to remind myself that I am not trying to come up with answers but questions that might lead me to the solution.
-
![]()
Possible Solutions
I would consider this step the most important step since it is my guideline for designing the mobile app. I prototyped these possible answers and tested them to see how effective they were.
Paper Prototype
While testing my paper prototype, I made sure to voice record the user test and take notes on any mobile features I should fix. This assisted me in reflecting and iterating my paper prototype to move on to my wireframes.
Wireframes
After altering my paper prototypes, I created wireframes and spoke with my art director to gain feedback. He suggested integrating a few more features, like a comment section, to communicate problems with the manager and demonstrate what a capture screen would look like. After incorporating that feedback, I went forward to user-testing it again.
