Staff shortage in hospitality: offering an experience with fewer people
Almost every establishment runs tighter than five years ago. You don't notice it in the food, because the kitchen holds up. You notice it in the dining room: less time per table, longer waits to order something, and less room for the chat that makes a visit personal.
The reflex is to work harder. That holds up for a while and then costs you people. The other path is looking at what work can be removed without the guest losing out on anything.
Where the pressure really lies
If you follow a night, you notice that most interruptions don't come from the order itself but from the waiting around it:
- Guests who raise their hand for something small and wait five minutes until someone walks by.
- Impatience at tables where the food takes long, which leads to extra questions to the staff.
- Chasing reviews afterward, usually by email and usually without result.
- Children who become restless and around whom the staff have to work.
None of those four is service. It's all work that arises because something else isn't running smoothly.
What you can take away
Reordering without waiting
A button on the table with which a guest orders an extra drink removes the main source of hand-raising. The order arrives at the place where it belongs, and the staff walk once instead of twice.
Waiting time that fills itself
A table that has something to do calls less. Table games ask no action at all from your staff: no materials, no explanation, nothing to clear away. See how it works.
Reviews at the right moment
Asking while the experience is fresh yields more than an email afterward and costs nobody any time.
What you want to take away is not contact with the guest, but the waiting that eats up that contact.
Keeping people is cheaper than looking for people
Replacing an employee costs a job posting, interviews, training time, and a period in which the rest cover for it. Count on six to eight weeks before someone is as fast as the person who left. In those weeks, quality drops in everything that person touched.
That makes the sum different from how it looks. Every measure that lightens the workload pays for itself as soon as it prevents one departure a year.
Why people really leave
Rarely for the wage alone. What keeps coming up in exit interviews:
- Schedules that are known too late to plan anything around.
- Shifts where you're structurally short-staffed, so you can't do anything well.
- The feeling that guest complaints land on you while you can't change anything about it.
- No moment at all to catch your breath between two peaks.
The first two are about planning. The last two are about how much the work costs you, and that's exactly what this article is about.
Scheduling on the moments, not on the hours
Most schedules are built on opening hours: someone starts at five, someone else at six. But the pressure in a dining room isn't spread evenly across the evening.
There are three peaks, and they all last briefly: the moment the first tables come in and all want to order at once, the moment the first main courses go out, and the moment three tables want to settle up at the same time. In between it's quieter than it feels.
Anyone who puts their staffing on those three peaks instead of spreading it evenly across the evening gets more calm with the same hours. That does require knowing when those peaks fall for you, and that differs per establishment and per day.
What the staff themselves notice
There's a difference between a heavy shift and an unpleasant shift, and that difference isn't in the number of plates.
- A shift where you walk from A to B and finish it feels light, even if there's a lot of it.
- A shift where you're called away halfway three times feels heavy, even if there's less of it.
- One guest who gets impatient costs more energy than five guests who don't.
Everything that lowers the number of interruptions thereby lowers the felt workload. That's not a soft gain: it's the main reason people quit hospitality.
What you should specifically not automate
There's a line, and it's sharper than the providers of these kinds of systems suggest. These three should remain human work:
- The welcome. A guest who walks in and is greeted by a screen starts at a disadvantage.
- The moment something goes wrong. A well-resolved mistake often yields a higher rating than a flawless visit, but only if there's a person facing them.
- The goodbye. That's the last thing someone takes with them.
Everything in between is largely logistics, and logistics may be made easier.
What it delivers for your staff
Fewer interruptions means less walking around and fewer moments where someone is called away halfway through something else. That saves physically, but especially mentally: it's the constant switching that makes a shift heavy, not the number of plates.
And it gives back something that's the first casualty with a tight team: time for the conversation at the table that guests remember.
What this costs for your number of tables is on the pricing page.
How do you offer good service with too few staff?
By removing the work that arises from waiting - hand-raising for a drink, impatience at the table, chasing reviews - and specifically leaving contact with the guest intact.
What should you not automate in hospitality?
The welcome, resolving a mistake, and the goodbye. Those are exactly the moments where a guest forms their judgement.
Does table entertainment help against staff pressure?
Indirectly. A table that has something to do calls for attention less often, and games via a QR code ask no action at all from the staff.
What is the biggest hidden time-waster in service?
Constantly being interrupted. It's not the number of plates that makes a shift heavy, but the number of times someone is called away halfway through something else.
Want to try games on the table yourself?
Give your guests more experience from the very first day.
