4.X — Urgent on Problems, Patient on Progress #
Here’s the line that separates good operators from great ones: urgent on problems, patient on progress.
If your food cost spiked 8 points this week, you act today. Not tomorrow. Not after you’ve “studied” the numbers. Today. The cost of delay on a real problem is always higher than the cost of acting imperfectly now.
But if you rolled out a new service sequence and it’s creating friction after 10 days, you give it 30. Systems need time to settle. People need time to own a new behavior. The failure mode on one side is operators who see a problem and study it while it compounds. The failure mode on the other side is operators who change the system every two weeks because it “isn’t working yet” — when the real problem is they haven’t given the team time to own it.
Problems demand urgency. Progress demands patience. Confusing the two is one of the most expensive mistakes an operator can make.
The cost of delay on a real problem is always higher than the cost of acting imperfectly now. A food cost problem that costs you $500 this week will cost you $2,000 by the time you spend a month studying it. A morale problem that loses you one good cast member this week will lose you three by the time you address it next quarter. A Guest experience issue that costs you ten covers this week will cost you fifty by the time you get around to it.
Speed is not about rushing. It’s about the disciplined refusal to let known problems fester while you wait for perfect conditions to act. Perfect conditions never come. The operators who win act when conditions are good enough — and then refine as they go.
