I'd count paid practice time as part of a restaurant's technology bill. The subscription gets a line on the invoice. Helping a busy shift learn the thing can end up treated as something people will squeeze in between customers.
New research released November 5 by the National Restaurant Association gives that neglected expense some company. Training and education topped the support operators said would help them adopt technology more effectively, at 56.5%. The paper, The Future of Restaurant Technology, argues for connecting tools, data and people. I'm particularly interested in the people.
A system can be available without feeling usable to the person standing at the till. Knowing where the refund button lives is one task. Knowing what to do when a guest changes an order after paying is another. A demonstration can cover the first and leave a new employee to discover the second with a queue watching.
The practice shift belongs in the price
Here's an illustrative example, not a reported incident: a small restaurant introduces a new ordering system. The manager gets the vendor's walkthrough. A part-time employee learns it from a colleague on Saturday. A customer then wants to split a payment and remove an item already sent to the kitchen.
There may be a perfectly good way to handle all of that. If the employee hasn't practiced it, the restaurant has bought a capability it can't comfortably use at the moment it matters. The manager comes over, the line waits, and the guest gets to watch the training session.
I'd rather see a technology proposal include paid time for the actual shifts to rehearse a few ordinary complications. Let the people doing the work pick those situations. They may know more about the awkward order than the person buying the software. Include whoever will teach the next new starter, too. Otherwise, each departure can take a piece of the training with it.
That might mean a smaller first rollout or buying one less feature. I think that's a reasonable trade if it gives staff enough confidence to keep talking to the customer instead of apologizing to a screen.
Hospitality gets a vote
The Association's research combines a survey of 212 operators, conducted June 18 through July 18, with eight restaurant-leader interviews. DoorDash and PayPal sponsored the paper. It's an industry snapshot, not a promise that a particular purchase will improve your dining room.
The useful test for restaurant technology training can be quite small: after practice, can someone handle that changed order, explain the result to the guest and get back to service without summoning the manager? Watch the task, and ask the employee where it still feels awkward. Speed matters, but so does leaving the customer feeling looked after.
A New Jersey restaurant doesn't need an enterprise transformation program to try that. It needs a little protected time before the rush. Dinner service is an expensive place to discover what the walkthrough left out.
Sources and further reading
