Dave, Brian, and Chef Anthony take on menu bloat — why independent restaurant menusballoon to six-plus pages, the real cost of decision fatigue and operationaldrag, and a data-first process for trimming back with confidence. Along the waythey cover menu engineering, using AI to knock out the build-sheet grunt workin minutes, how to weather the social-media backlash when you cut a regular'sfavorite dish, and why staying in your lane beats chasing every trend.WhatYou'll Learn•    Why menus bloat — the "everybody loves it, put it on the menu"trap, TikTok trend-chasing, and emotional attachment to legacy dishes.•    The true cost of bloat — decision fatigue for guests, plus harder inventory,ordering, prep, storage, and execution behind the line.•    The five-guys principle — the closer you get to a tight, focused menu, the easierthe whole operation runs.•    Menu engineering refresher — pull your PMIX, cost every dish, and sort into stars,plow horses, puzzles, and dogs.•    Beating the build-sheetroadblock with AI — snap a photo, drop in your menudescription, and let it draft a build sheet in minutes — then correct thehallucinations.•    Make it a team decision — get managers and chefs vested so you're not defendingthe cut alone when the backlash hits.•    Weathering the backlash — short-term pain, long-term relief; don't argue in thecomments; the vocal minority is not your loyal majority.•    Tapping servers and customers — a short VIP questionnaire surfaces market intel thechef's jaded palate misses.•    Staying in your lane — don't bolt a trendy dish onto a concept it doesn't fit.No Sushi Wednesday at the rib place.TheProcess (Do This)1.  Cost out your menu — at minimuma rough costing on every dish.2.  Pull your PMIX to get units soldand profitability per item.3.  Run it through menu engineering(spreadsheet or software) and categorize each dish.4.  Use AI to draft build sheetsfast: photo of the dish + your menu description, then fix what's off.5.  Bring in stakeholders so thedecision — and the heat — is shared across the team.6.  Gather frontline intel withserver input and a quick VIP customer questionnaire.7.  Make the cuts, then hold theline. The storm blows over faster than you think.MomentsWorth Replaying"You're the reason the menu ends up sixpages." — Anthony, on the server who wants every special added"Short-term pain always causes long-termrelief." — on cutting the menu down"It's simple. It's not easy."  — on the build-sheetwork"I'd rather win than be right."  — on dropping the egoand collaborating"No one's going to the rib place to getsushi." — on staying in your laneConnectStuckon where to start? The guys are highly accessible — shoot the show an email andthey'll jump on to help, wherever you are. More at restaurantopia.com.Learn more about your ad choices. Visit megaphone.fm/adchoices