Fable
The chief steward did not move a single stone, yet he got the bridge closed on schedule.
Hewan City needed to build a new bridge before the rainy season. Masons could cut stone, carpenters could build scaffolding, boatmen could transport materials, and accountants could handle the money. In past small projects, whoever was free would find the next task, and with a few old foremen shouting orders, the bridge would slowly get built.
This time was different. The bridge had to span three rapids and keep the ferry business running at the same time. If the stone did not arrive, the wooden frame could not be erected; if the wooden frame was late, the boatmen would have to be rented for three more days; if the accountant missed one entry, the lord would think the money could last another half month. Everyone was working, but no one could see the true progress of the whole bridge.
The city lord first added a rule: all craftsmen must submit a sheet every evening stating how much they had completed. The papers piled higher and higher, but the problems did not decrease. The stonemason wrote that he was 80% done, the carpenter wrote that he was waiting for stone, and the boatman wrote that the docks were congested. All three sheets were true, but together they could not tell the city lord what to change tomorrow.
Someone then proposed letting the smartest stonemason also oversee the whole project. The stonemason was very dutiful, chiseling stone by day and reviewing papers by night. A few days later he was so exhausted that he overlooked a crack in the wooden frame, and the boatman, receiving no instructions, sent a batch of timber to the old warehouse. Everyone was busier, but the bridge moved even more slowly.
The real accident happened on the seventeenth day. Two crews removed the temporary supports at the same time; one thought the other had already reinforced, and the other thought it was only clearing the site. Half the scaffolding sank into the water. No one made a deliberate mistake—there was simply no role continuously checking dependencies, filling gaps, spotting conflicts and deciding when to stop.
The next day, the city lord invited a chief steward. The steward did not take up the hammer, nor did he write accounts for the bookkeeper. He first drew the task map for the entire bridge: who depends on whom, which step can run in parallel, which step must wait for acceptance, which kind of failure requires rescheduling, and which kind of risk requires immediately asking the city lord for approval.
From then on, the craftsmen no longer reported only their own busyness each day, but submitted their status to the same bridge ledger. When the overseer saw stone was delayed, he moved carpenters to repair the old frame; when he saw two teams both needed to work on supports, he paused one of them; when he saw the accounts budget hit the line, he presented the alternatives and risks together.
A month later, the bridge closed before the rainy season. The city residents discovered that the chief steward's most important skill was not knowing more than every craftsman, but enabling many capable people to collaborate within the same map of schedule, boundaries, and responsibilities. Without this role, the more smart people there were, the more conflicts arose.