Stop Writing Training Content — Your Menu Already Is the Curriculum
Hey Team!
Most restaurant training programs never get built. Not because operators don't care about training. Not because they're lazy. Because step one feels like becoming a teacher, and nobody signed up for that.
I've opened over twenty concepts across multiple markets. I've hired more servers, line cooks, and bartenders than I can count. And every single time, the conversation about building a real training program started the same way. Someone says "we need to get this documented." Everyone nods. Then the week fills up, a vendor doesn't show, a manager calls out, Saturday hits, and the document never gets written.
That's not a motivation problem. That's a design problem. The old model required you to become an instructional designer on top of being an operator, and that was never going to work at scale across 40,000 independent restaurants.
Here's what nobody in the training world will say out loud: you don't have a content problem. You never did. The menu is already the curriculum, and it's been sitting on your desk the whole time.
Think about what's actually inside a menu PDF. It's got dish names, descriptions, ingredients, proteins, preparation styles, dietary flags, and price points. It's got your tap list, your cocktail builds, your mocktail options. It's got the things your staff gets asked about every single night. "Does this have gluten?" "What's in the ranch?" "Can I get that without dairy?" Every one of those questions has an answer, and your menu has it. The content exists. It just hasn't been turned into training yet.
The old model asked you to extract that content, rephrase it into learning objectives, format it into slides or a packet, print it, hand it out, and hope someone read it before their first Saturday night. Every step in that chain required time you didn't have and a skill set that has nothing to do with running a restaurant.
This is exactly what Theodore Levitt was writing about in 1960 when he described companies that defined themselves by what they made instead of what their customers needed. The training tool companies of the last two decades built better and better ways to author content, manage content, and distribute content. What operators actually needed was for the content problem to not exist. Nobody wanted to write modules. They wanted trained staff.
Our competitors are still making better buggy-whips. That's a real thing, and I say it without any drama. If your entire product assumes the operator is going to sit down and author training from scratch, you've built the wrong thing for the 400,000 independent restaurant locations in this country where the GM is also doing the ordering, the scheduling, and the 2pm produce check-in.
What changed is that AI can now read your menu and generate the questions your staff needs to answer. Not generic hospitality questions. Not "what is good customer service" questions that any chain's LMS has been recycling since 2005. Specific questions. "The Smokehouse Burger comes with what two cheeses?" "Which appetizers on the current menu can be made vegan?" "The Ranch Chicken Sandwich contains which of the following allergens?" Those questions live inside your menu. They always did. It just used to take a human hours to pull them out.
When I built ShiftTrained, this was the thing I kept coming back to. I've been in kitchens since I was washing dishes as a teenager, and I knew the training problem wasn't lack of content. It was friction. Every hour you spend building training is an hour you're not on the floor, not with your staff, not handling the hundred things that actually need you. So the only system that gets used is one where the content builds itself.
At Black Barrel Tavern, we upload the menu and have training questions live in minutes. Not days. Not a weekend project. Minutes. The staff takes them on their phones, they retake them voluntarily, and when something changes on the menu, we update the source document and regenerate. The curriculum updates because the menu updated. That's how it should work.
Now let me say the part that's obvious once you see it but took me a long time to articulate. Training programs fail at the authoring stage because operators treat training like a project with a beginning, middle, and end. Write the content, roll it out, done. But menus change. Specials rotate. Ingredients swap out because of supplier issues. Allergen information has to stay current or someone gets hurt. A training program built as a static document is out of date the moment something on the menu changes, which means it's never really done anyway. If your training system isn't connected to your menu as a living document, you're just generating outdated paper.
The operators who've figured this out don't think about training content at all anymore. They think about the menu. They keep the menu accurate. The training follows automatically. That's the shift. Not from bad training to good training. From manual to automatic. From authored to generated.
If you're still staring at a blank Google Doc wondering how to start building your training program, I want you to close that doc. Pick up your menu. That's your curriculum. It's already written. The only question is whether your tools can read it.
Have a great day! — Terry Psaltakis
Your AI Restaurant Guy
For more on putting this into practice, see how ShiftTrained approaches server training.
