Some say implementing a back-office system is the most complicated system to deploy in a restaurant company.
July 8, 2016 by Dave Bennett — President & CEO, Mirus Restaurant Solutions
Editor's note: This is the first in a two-part series on the topic of restaurant food costing and perpetual inventory systems.
In most cases, these are two parts of a typical restaurant back office (BOH) system. I'd like to collect your input on today's question:
How long did it take you to set up and deploy your back office system?
Over the years, I have heard hundreds of horror stories about how long and complicated it can be to successfully complete a bac- office implementation. Some say it is the most complicated system to deploy in a restaurant company. And, it doesn't seem to matter which solution was selected. At last count, there are over 40 companies that offer a restaurant back-office solution.
The problem
The biggest complications seem to be human related. A food-cost system requires a lot of configuration for ingredients, recipes, prices and pack sizes; a lot of technical stuff. However, I have heard many people describe human challenges as being the hardest part of the project, and not the technology. The roll-out of a back office system touches lots of people up and down your organization chart.
One of the early human challenges is to get the Operations and Finance executives to believe the numbers being calculated by the system. The numbers are either too high or too low. Comments like "The variances seem to be off," or "The problem must be with the recipes" are not uncommon when the system is tested in the first store. Getting people to believe the numbers has delayed deployment of some projects by 6 months or more.
Later in the process, the implementation's success is dependent on getting every general manager and assistant manager at every location to learn their responsibilities around the system. Everyone who enters data into the system is expected to be precise, every time. You know the old adage—garbage in, garbage out. Many managers will get it right away, but it only takes a few bad apples to make the company summary of food cost useless. Everyone must perform to near perfection if the system is going to present useful information.
The solution
If you are considering a back-office system for the first time in your restaurants, do you think your store level managers are ready for the tasks you will be asking them to perform? Are you ready to deploy the human and financial resources it will take to effectively implement the system? Do you have a timetable target? Are you willing to invest the time it will take to train the users at all levels? Asking and addressing these questions and more early in the process may save you money, time and energy deploying a system that your team will be ready for.