Two Versions Of The Same Idea
Picture two food and beverage spots opening in the same small town, same month, same size building. One makes it past year two in good shape. The other struggles or closes. Most of the time, the difference is not the recipe or the location. It’s a set of small decisions that get made, or don’t get made, in the first few months.
I have made both kinds of decisions. I have also watched them play out in a kitchen and behind a bar, not just on paper. So I want to walk through what the good version of a few common situations looks like, right next to the bad one.
The Menu
Bad version: the menu tries to be everything. Twenty entrees, five kinds of fries, a burrito next to a burger next to a soup. The kitchen is slow because every cook has to hold too many recipes in their head at once.
Good version: the menu is smaller than the owner wants it to be. Every item earns its spot because it sells, or because it’s the thing that gets talked about. A tight menu means faster food, less waste, and a kitchen team that can actually get good at what they’re making instead of just getting through the shift.
I would rather cut three items nobody asks about than add three more to compete with a place down the road.
The Staffing Plan
Bad version: you hire for the schedule you have today and hope everyone stays forever. When someone quits, you’re short-staffed and scrambling, and the whole place feels it that week.
Good version: you’re always slightly ahead on hiring and training, even when it costs a little more in the short term. New people shadow someone before they’re on their own. Nobody gets thrown onto the line the first week they walk in the door.
This one is hard to justify on paper. It looks like extra labor cost. It shows up as fewer bad nights.
Handling A Slow Week
Bad version: a slow week turns into panic. Prices get changed, hours get cut, promotions go out that don’t match what the business actually is. Customers notice the scramble.
Good version: a slow week gets looked at against a full year, not against last week. Weather, a local event, a holiday, all of that moves numbers around without meaning anything is actually wrong. I check in on my goals monthly, not daily, so one bad Tuesday doesn’t send me chasing a fix for a problem that isn’t real.
Talking To Customers When Something Goes Wrong
Bad version: an order comes out wrong or slow, and the response is an apology and nothing else. The customer leaves feeling like a number.
Good version: someone from the business, not just whoever happens to be closest, comes over and actually deals with it. Fixes the plate, comps something small, asks what happened. That takes maybe two extra minutes. It’s the difference between someone posting a complaint and someone coming back next month.
Growth Decisions
Bad version: growth happens because it feels like the next step, not because the current operation can support it. A second product line, a bigger space, more hours, all added at once, all straining the same small team.
Good version: growth happens one piece at a time, and each piece gets tested before the next one starts. Add the thing, watch it for a stretch, see if it actually works before building on top of it. It’s slower. It’s also a lot less likely to collapse under its own weight.
Why The Gap Is Usually Small
None of this is complicated. That’s actually the point. The gap between the business that lasts and the one that doesn’t isn’t usually a big strategic call. It’s a string of small ones: how many items on the menu, how far ahead you hire, what you do in week three of a slow month, who walks over to the table when something’s wrong.
Get enough of those small ones right in a row, and you end up with something that holds up.
Get enough of them wrong, and no single mistake ever looks big enough to explain why things fell apart. That’s usually because it wasn’t one mistake. It was thirty small ones nobody caught in time.