Rush hour in Pizza Shop is a systems test. Queue length, patience decay, and serve speed interact continuously. You cannot maximize all three at once, so you must optimize balance.
Begin by protecting patience collapse points. Identify how many simultaneous waiting customers your current setup can handle safely. Above that level, switch to stabilization mode: prioritize faster orders and reduce decision complexity.
Serve speed is not just movement speed. It includes decision speed. If your hands are fast but your choices are slow, total output still drops. Build pre-commit rules so you spend less time thinking during peak.
Queue control improves when you avoid overcommitting high-complexity orders at the wrong moment. One difficult order can block three easy wins. Use complexity pacing to maintain consistent completions.
After rush hour, run a micro-review: when did queue spike, what caused patience crash, and which rule helped recovery. Small improvements each shift create large long-term gains.
Rush is where champions are made. Pizza Shop rewards players who stay systematic under pressure.
Use a simple rush-hour scenario matrix to choose your mode faster. Scenario A: high queue and low patience, switch to stabilization output. Scenario B: medium queue and stable patience, run balanced flow with selective high-value orders. Scenario C: low queue and high patience, capture margin opportunities without overloading the line.
Set numerical trigger points before peak starts. For example, if queue exceeds six active orders or average patience drops below a defined threshold, force an immediate simplification protocol. Predefined triggers stop emotional overcorrection.
Finally, train “re-entry discipline” after recovery. Once pressure drops, do not instantly return to maximum complexity. Reintroduce difficult orders step by step so your service rhythm stays intact across the full shift.