Fable
The team that could get things done finally learned to pull in the same direction
There was a capable work crew in the city that could repair roads, write notices, move goods, and negotiate prices. Each person looked like a good hand on their own, but the real trouble began after they started handling important matters for the trading company.
Once a client asked to "change the refund clause in the contract as soon as possible." The fastest apprentice changed it immediately, saving half a day, but exceeded the shopkeeper's authority. Another time, a cautious apprentice sent everything back to the shopkeeper; safe as it was, the client waited until furious. The shopkeeper found that the trouble was not that the crew was lazy, nor that the crew was stupid. Precisely because they were capable, wrong actions could be amplified into real losses.
The chief steward first wrote slogans: be helpful, be honest, be safe. The slogans hung on the wall, the work crews nodded, and the next day they acted as usual according to their own habits.
He added a checklist too. A checklist can block obvious errors, but it cannot block finer trade-offs: when to probe further, when to refuse, when to demand evidence, when it must go to human review. The first checklist had twenty items, and the clerks ticked them off one by one. But when a customer was pressing, evidence was insufficient, or permissions were unclear, even after finishing the checklist they still did not know which way to lean.
Later the chief steward laid out real cases for comparison. Two replies could both satisfy the client, but one leaked another party's floor price; two plans could both speed things up, but one bypassed approval. The work crew began to learn boundaries from these comparisons.
They also set up a test bench specifically for dangerous requests, ambiguous instructions, conflicts of interest, and temptations to exceed authority. Every time they got it right or wrong, they had to explain the basis. After real cases were turned into drills, the work crew began discussing consequences. Some requests looked like they could help the customer but would harm a third party; some refusals looked safe but brought legitimate matters to a halt.
The steward later wrote the boundaries into the crew's everyday tools. Check authorization before quoting, check approval before changing a contract, stop automatically when a conflict of interest arises. Direction cannot rely on memory alone; it must be blocked before the action happens.
After a time, the crew did not become timid, but knew better what should be done, how to do it, and where they had to stop. The steward finally said: capability only shows that the team can have an impact; when the direction is right, the impact is worth entrusting.