Fable
When the lunch rush hits, a noodle shop can't just shout at people to hurry up
The noodle shop on East Street usually had only two pots, three tables and one waiter. In the morning there were few customers, everyone took their time, and the noodles did not clump. At the lunch market, dock workers poured in, the line stretched to the street corner, and the water by the pot had not even boiled yet.
The boss's first reaction was to shout at the staff to hurry. The staff ran until drenched in sweat, yet customers still waited and left. The next day he hired ten people on fixed shifts, from dawn to night. The lunch rush was indeed stable, but in the afternoon the shop was empty, with ten people staring blankly around two tables of customers.
The bookkeeper reminded him that the problem was not simply too many or too few people, but that customer flow fluctuates. The owner then tried calling neighbors to help by feel, but often called too late; by the time they arrived, the peak had passed, or just after he sent them away another wave of boat passengers came.
Later the owner put a queue sign at the door and a dough-count sign by the stove. More than twenty people in line meant firing up the third pot; more than forty meant using the backyard tables; fewer than five tables for half a shichen meant removing the temporary stove and helpers.
On the first rainy day, foot traffic suddenly dropped off a cliff, and the old approach would have kept all the helpers waiting until closing. The new rules scaled down by the number of tokens, keeping only the necessary people and pots. In the evening the boat fleet docked, the token count rose again, and the back courtyard quickly reopened.
The noodle shop did not become an infinitely large establishment, nor did it keep a permanent idle crew. It learned to scale capacity up and down according to real pressure: expand when busy, pull back when idle, neither letting the queue collapse nor burning cost on empty tables.
Later the boss added another rule: after expanding, someone must watch quality. If the third pot makes the noodle soup bland, or the backyard table causes delivery errors, you cannot expand based only on headcount. Capacity can increase, but every bowl of noodles must still be served to standard.
When the tavern down the street copied the idea, it copied only "add people when there are many customers," and soon lost money because idle-time costs were too high. The noodle shop owner understood that the key to scaling is observing pressure, setting thresholds, automatically adding or removing resources, and keeping cost and experience controllable. Later the owner added another rule: after scaling up, someone must watch quality. If the third pot makes the broth bland, or the backyard tables cause delivery errors, you cannot expand based only on headcount. Capacity can increase, but every bowl of noodles must still be served to standard. When the tavern down the street copied the idea, it copied only "add people when there are many customers," and soon lost money because idle-time costs were too high. The noodle shop owner understood that the key to scaling is observing pressure, setting thresholds, automatically adding or removing resources, and keeping cost and experience controllable.