Fable
From apprentice to night-shift shopkeeper
Three apprentices came to the carpenter's shop. On the first day, the master had Xiaolin only hand over tools. When the master said plane, he handed the plane; when the master said stop, he stopped immediately. He did a bit of the work, but all decisions were in the master's hands.
A month later, Kobayashi could sand chair legs according to the drawings. The master no longer watched every cut, only checked at key dimensions. Kobayashi could decide which side to sand first, but he could not change the drawings or deliver the chair to the customer.
Half a year later, the master let him independently repair ordinary tables and chairs. Xiaolin could take orders, estimate time, choose wood, and register after completion, but whenever he encountered expensive wood, strange requests, or orders that might lose money, he had to call the master.
Another apprentice, Xiao Zhou, moved too fast. He had just learned to plane wood when he privately took on a full set of cabinets, and when the dimensions came out wrong, he promised to redo them for free. Only then did the master realize the problem was not whether the apprentice was clever, but at which points he was allowed to decide for himself.
Later, the carpenter's shop hung four signs on the wall: advisory only, execute step by step, low-risk autonomy, high-risk requires approval, full-process accountability. Before taking on a job, each apprentice first checked which level they were at. The higher the level, the less they were directed step by step—not the less work they did—and the more judgment and consequences they bore.
The master also set guardrails for each level. An apprentice who only suggests can't touch customer commitments; a low-risk autonomous apprentice can only handle fixed price lists; and although the night-shift manager can take orders independently, he must wake the master before any large compensation.
The carpenter's shop thus reduced two kinds of mistakes: tying capable people too tightly, and placing unprepared people too far out. Autonomy is not a single phrase "go ahead and do it," but a clear set of permissions, boundaries and takeover points.
Later the manager wrote this experience into the daily rules: first look at the scenario, then look at the boundaries, and finally look at who can take over when something fails. Only when all of these are clear does a polished demo become deliverable work. During reviews, they would also check against old incidents to confirm that the new rules were not just good on paper, but could actually block the same mistakes in a chaotic live setting.