Training Staff at a New American Restaurant: Local Sourcing, Rotating Menus, and the Table That Asks Where Everything Comes From
Hey Team!
There's a table in every New American restaurant that I love and dread at the same time. You know the one. They order the grain bowl or the pork shoulder or the roasted beet plate, and before the food even hits the table, somebody asks: "Where does this come from?" Not "is it local?" They want the actual farm name. The county. Whether it's certified regenerative or just marketed that way. They've done more research before dinner than some of your servers will do all week.
And that's the real problem with running a New American concept. You built your margins around the story. The sourcing. The relationship with the farmer forty miles out. You're charging $28 for a pork chop because it came from a specific herd on a specific piece of land and your chef can tell you exactly when it was harvested. But if the server says "yeah it's locally sourced" and can't get past that? You just torched the premium you worked months to build. The guest paid for the story and got a shrug.
Here's what makes this harder than training at a concept with a static menu. New American kitchens rotate constantly. Seasonally if you're disciplined, weekly if your chef is ambitious, sometimes mid-week when a farm calls with something unexpected. That's genuinely exciting. It's also a training nightmare, because every time the menu flips, the sourcing facts flip with it. The beet salad that was running Satur Farms last month is running a different producer now. The fish special changed twice since Tuesday. Your servers are still talking about the heritage pork from the farm you stopped working with in September.
I've seen operators invest real money into sourcing relationships and then watch it dissolve at the table because nobody built a system to move that information from the chef's brain to the server's mouth before service. The chef knows every detail. The owner knows. The menu insert mentions it in eight-point font. But the 24-year-old on a four-table section on a Friday night? She's guessing. And guests can feel a guess.
The fix isn't a longer pre-shift meeting. Pre-shifts are already too long, and stacking more verbal information on top of a staff that just clocked in doesn't stick. What actually works is building the sourcing facts directly into the quiz cycle so they refresh every time the menu does.
Think about what a sourcing fact actually is: it's a short, specific, memorable piece of information. The chicken comes from Prairie Wind Family Farm in Elgin. The tomatoes are dry-farmed. The mushrooms are foraged locally, not cultivated. These aren't complicated concepts. They're facts that need to travel from a document into a staff member's working memory before the first cover walks in. A well-constructed quiz question does that in under thirty seconds. "What farm supplies the pork shoulder currently on the menu?" is a better training tool than a five-minute lecture, because the staff member has to retrieve the answer, not just nod at it.
The key word there is "currently." When your menu changes, your questions have to change with it. That sounds obvious, but most operators are working with training materials that take days to update. Someone has to rewrite the flashcards or redo the document or chase down the manager to add slides to the deck. By the time that happens, the dish has already been 86'd and something new is running. The training never catches up.
What I built with ShiftTrained was designed specifically around this problem. Upload the new menu as a PDF when it changes, and the platform generates a fresh batch of quiz questions in minutes. Sourcing details, technique descriptors, allergen flags, pairing suggestions, all of it pulled directly from whatever you gave it. Your staff is quizzing on the current menu, not last month's. And because they're doing it on their phones, they're running through questions between tables, before their shift, on the bus. The repetition is the whole point. Repetition is what makes "Prairie Wind Family Farm" come out naturally at the table instead of "um, somewhere local, I think."
Now let me tell you what changes when this actually works. The server stops saying "locally sourced" as a dead-end phrase and starts saying "this is from Kinnikinnick Farm out in Caledonia, they do a dry-aged process and the chef has been working with them for two seasons." That sentence is worth real money to you. It justifies the price point. It creates a connection between the guest and the food. It turns a transaction into the kind of experience people come back for and tell other people about.
The table that asks where everything comes from isn't a difficult table. They're your best table. They chose you on purpose. They're primed to spend, to engage, to order the bottle and the dessert course, to leave a review that actually says something specific. The only way you lose them is if your staff can't hold up their end of the conversation.
Your menu story is only as good as the person delivering it at 7:30 on a Saturday night. That person needs the facts. They need them fresh. And they need to have practiced them enough that the answer comes out clean, not clunky.
The relationship with the farm matters. Train like it.
Have a great day! — Terry Psaltakis
Your AI Restaurant Guy
For more on putting this into practice, see how ShiftTrained approaches restaurant training software.
