Fable
After the fire is out, why does the carpenter still measure that beam
A warehouse bridge in Wooden Bridge Town collapsed after a night rain. Torches shone on the broken beams, and cargo boxes were scattered by the river. The mayor's first sentence was to find out who had last walked across the bridge, and everyone was also eager to find someone to blame.
The last to cross the bridge was the young cart driver. He admitted there were two extra sacks of salt on the cart, and the mayor nearly wrote the accident up as overloading. But the old carpenter crouched by the beam and felt the long-blackened water stains inside the break.
For the first repair, the mayor posted a notice: from now on, each cart would carry two fewer bags. When the rainy season came, the small bridge nearby also began to creak. Carrying less cargo could relieve some pressure, but it did not explain why the beam had been damp for so long.
The old carpenter re-measured the site after the fire was out. The bridge deck slope, drainage ditches, beam replacement records, earlier small cracks, and who had received reports were all written into the same ledger.
Only then did everyone see that the accident was not caused by one person in one night. The drainage ditch was blocked by fallen leaves, the bridge inspector saw cracks but only gave a verbal warning, and the budget meeting postponed replacing the beam until after autumn.
The mayor initially disliked this, thinking it was dredging up old accounts. The old carpenter said, if you only punish the cart driver, the next cart driver will come along and the bridge will still collapse. A retrospective should find places that can change future outcomes, not just find an outlet for the past.
Later, the town built drainage, changed the reporting method, and also stipulated that any crack over one inch required closing the bridge. The accident log did not restore the bridge, but it kept the next bridge from taking the same broken path.
The mayor later placed the incident log in the council hall, not to shame anyone, but so it could be brought out during the next budget allocation and inspection. If a retrospective only says "someone was careless," it will soon be forgotten; if it clearly records the conditions, signals, decisions, and remedies, it becomes a tool that helps those who come later make one less mistake. Later, when minor incidents occurred again, people felt less urge to cover them up. Because the purpose of a retrospective is not to find a scapegoat, but to find the steps where next time we can see earlier, stop earlier, and repair earlier. The town's safety depends on embedding lessons into systems, time and again. Later, when townspeople saw the incident log, they no longer thought about who was unlucky, but about where reinforcement could still be added in advance. This phrase was later written into the handbook for newcomers, reminding everyone to look at the on-site cost first before discussing labor savings. And because of this reminder, when similar difficulties arose later, people would not rush to apply old methods. They learned to first ask which step bears the risk, then decide whether to let go, tighten up, or rearrange the process.