Every operator has a story about an LTO that should have worked. Good margin, decent food cost, marketing pushed it hard, and it still limped through its run. Nine times out of ten, the problem was never the item. It was the rollout.
Most restaurants treat a new LTO like a menu print job. Corporate or the culinary team finalizes the item, ops sends a one-page spec sheet, and managers are expected to brief the floor in a five-minute huddle before doors open. Nobody actually tastes the thing. Nobody practices saying the name out loud. Nobody knows what to say when a guest asks what makes it different from the regular burger. That gap between kitchen-ready and floor-ready is where LTO revenue goes to die.
Here is what a real launch checklist looks like, and it starts a full week before the item hits the menu, not the morning of.
Taste it before you sell it. Every server, host, and bartender should eat or drink the actual item before launch day, not read about it. You cannot sell a flavor profile you have never experienced. Run a tasting during a pre-shift, let the team react honestly, and collect the actual words they use to describe it. Those words become your talking points, because they sound like a person, not a menu description.
Give the floor a real pitch, not a name. Do not just tell servers the LTO exists. Give them a one-sentence hook they can say without thinking. Something like this is not enough: mention the new item to every table. Something like this works: it is our smoked brisket mac, comes out in a cast iron, most people split it as an app. That sentence sells itself because it is specific and it sounds like a recommendation, not a script.
Set a mention target and track it daily. If the goal is for every table to hear about the LTO, somebody has to check whether that is actually happening. Most restaurants find out three weeks in that half the floor forgot the item existed by day four. A quick daily check-in, even just a manager asking two or three servers what they said about the LTO on their last table, catches that drop-off before it costs you the whole run.
Watch first three days, not week one. The first three shifts tell you almost everything. If ticket times spike, if the kitchen is fumbling plating, if servers are quietly steering guests away from it because it is a pain to execute, that shows up immediately. Waiting until the weekly sales report to catch this means you have already lost the best chunk of your run.
Price it like a decision, not an afterthought. If your LTO price point trains guests to wait for the next discount instead of trying regular menu items, you are running a promotion, not a menu addition. Decide upfront whether this item needs to make full margin on its own or whether it exists to drive traffic, and price and portion it on purpose instead of backing into a number that felt safe in the meeting.
Brief the shift leads separately from the floor. Shift leads need to know the why behind the item, expected volume, prep constraints, and what to do if you 86 it early. Servers need the sell. Those are two different conversations, and combining them into one all-staff meeting usually means neither group gets what they actually need.
Decide the kill criteria before launch, not during it. Know in advance what a failed LTO looks like for your restaurant. Is it under a certain number of orders per day by day five? Complaints on ticket times? Food cost creeping past a threshold? Decide that number before the emotional attachment to the launch sets in, because mid-run is the worst time to make that call objectively.
An LTO is a test of your training systems as much as your menu. If your team cannot execute a consistent pitch across every shift, every server, every location, the item was never going to hit its numbers no matter how good it tasted in R&D.
Wingman helps you run that pitch consistently by putting the talking points, the tasting notes, and the daily accountability checks in one place your shift leads actually use, so the LTO gets a fair shot on shift four the same way it did on day one. See how Wingman keeps every launch on track.