How would you design a cafeteria app for employees?
- David Mercy
Clarifications
- What kind of app are we talking here (Mobile App, Web App)? – Mobile App
- Any particular goal are we trying to achieve with this app? – Make the experience more efficient and help plan meal time better
- This cafeteria which we are talking is a shared one among companies or private one? – Shared
- This cafeteria are we talking, is it like a full meal cafeteria or just tea/coffee/snack bar type? – Full meal cafeteria
- In this cafeteria does a person pays or is it like free? – Free
- And is it free for all kind of employees? – Yes
- Can this cafeteria be accessed by guests? – Yes
Rephrasing the question
We want to design a mobile app that needs to be used by employees to reduce wastage of time in a shared full meal cafeteria where everything is free for everyone
User Segments
- Company Employees – People who are the working in different companies and have their meals at the cafeteria
- Cafeteria Employees – People who manage the cafeteria
I would like to focus on Company Employees as they are the largest base here and have the most pain points in terms of meal experience
User Journey
- You decide to have the meal
- If with someone, you ask around
- If alone you proceed
- Reach cafeteria
- Show some identification
- Figure out what to eat by visiting various counters
- Figure out the appropriate seating
- Eat
- Put the dishes
- Go back to work
Pain Points
- You sometimes are not able to figure out whether a person is in cafeteria or not
- Sometimes you forget to get your identification at your workdesk which causes problem if you reach at the identification section of the cafeteria
- Knowing the availability of the right size of seating beforehand to plan the time right is a problem
- If you have come alone to join a group and you don’t know where your group is seating becomes a problem
- In shared cafeteria, to figure out where to sit is a problem.
- If you are new, sometimes it’s difficult to figure out the navigation path in a cafeteria
- Figuring out what to eat
Prioritizing Pain Points
I will like to prioritise on the basis of the goal we had to making the experience more efficient and help plan time better so let’s evaluate where the does the most wastage happens.
- Low (You already have some other channels to figure this out)
- Med (Depends on the rules some places it is strict some places it is not)
- High
- Med (A lot of time people go together)
- High (Similar to point 3)
- Low (Typically new employee go with their teams or generally somebody accompanies them and then there are signages)
- Low (Most of the time they have fixed menus or you already know what is present)
For further discussion, I would like to focus on Point 3 and also try to solve point 5 with it as both kind of have similar characteristics
List of Solutions
- An QR code-based entry scanner that calculates the total number of people inside and displays the overall count to people inside count at the gate and also the display is available on demand on the app
- An on demand live camera feed of the cafeteria
- A table/seat booking system
Prioritising Solutions (On basis of impact to plan their meal time better)
- QR Code based entry scanner & notification system
- Impact – Med (Considering it doesn’t solve for knowing whether the appropriate table size is present or not)
- Effort – Low ( Out of box solutions for scanning and notification system are present)
- Camera Feed
- Impact – High (Considering you will know what size of tables are available, how many people are present)
- Effort – Low (CCTV solutions already exists in cafeteria typically)
- A table/seat booking system
- Impact – High (You have a pre booked seat for the time)
- Effort – High (Making a booking system is complex as it has a lot of elements)
Metrics
I would like to use the HEART framework
Happiness – Capture experience rating every time you log off the work around Rate your Meal experience
Engagement – 1. Number of people launching the app 2. Number of times people are launching the app with associated time
Retention – Number of people launching the app daily
Task Completion – Number of people finding the table immediately as they reach the cafeteria ( We will capture the same as a part of the flow)
Trade-offs
- Privacy concern – some people may not want this kind of live feed to be visible. A solution to that can be that we can show avatar or just color coded boxes rather than actually images
- It may happen that the seat is lost till the time to reach as may other people may be also watching at the same time – We can have the same information available to everyone watching that how many people are watching the space parallely

Microsoft
Capital One