Run

The weaving workshop received many work orders every day: mending a bolt of cloth, dyeing a vat blue, rush-making banners for a merchant caravan. The manager used to look only at whether the work order was written well, thinking that once it was written well, the matter had begun.

But once the work orders actually started moving, troubles came one after another. The dye vat ran short of materials, the loom jammed, the master took sudden leave, and the customer changed the dimensions again. Between that line of requirements on paper and the cloth finally delivered to the customer lay a long stretch of road.

For the first fix, the shopkeeper had the assistant write more explanations beside the work order. The explanations grew longer and longer, yet new situations still arose on site. No one knew which step this order was currently at, and no one knew where to resume after a failure.

The second time, he required every craftsman to shout once when done. The shouts rose and fell throughout the weaving workshop, but when things got busy no one could remember. If one shout was missed, the whole order seemed to fall into a crack.

The old steward gave each work order an itinerary: receive order, prepare materials, machine operation, quality inspection, rework, delivery, wrap-up. At each step, status, responsible person, materials used, and next step were recorded; failures also stayed on the same itinerary.

A few days later, the shopkeeper could answer a customer for the first time: your banner has been dyed and is drying; if the wind stops in the afternoon, it will be delayed by half a day. The weaving workshop could also see which types of work orders always got stuck at material preparation, and which craftsman had the most rework.

The shopkeeper understood that the entire process by which a work order is actually executed is the real operation. It is not the intention itself, but the state, actions, and results that the intention goes through step by step on site.

Later, when the weaving workshop reviewed a failed work order, it no longer only asked whether the original request had been written incorrectly, but followed the journey: whether material preparation was delayed, whether rework was repeated, whether delivery was confirmed. The path left by operations let managers see the real work, rather than only the wish at the beginning and the success or failure at the end. The old steward also discovered that the same work order could be run multiple times: after the first failure came rework, the second run changed materials and went through again, and the third run completed delivery. Each run needed its own state and traces. Otherwise people would only remember "it was done," without knowing how it was done. Later, when customers urged the order, the weaving workshop no longer answered "it's almost ready," but where the order currently stood. This sentence was later written into the handbook for newcomers, reminding everyone to look at the on-site cost first before talking about saving effort. And because of this reminder, when similar difficulties arose later, people would not rush to apply old methods.