Fable
Every change in the city requires someone to know what it will collide with
The automatic accounting office in Liuqiao City started out very small. The accountant could change the abacus mnemonic whenever he wanted, the shopfront could add a ledger column whenever it wanted, and the waiter could even get a new seal issued the same day. Everyone liked that speed.
Later, the back office took over quotes, contract summaries, customer tiers, and follow-up reminders. Every small change could affect revenue, applicable definitions and criteria, liability, or customer data, and the old habit of casually making edits began to become dangerous.
A waiter once changed the customer tiering rules to be more aggressive, and that evening a large number of low-intent customers were tagged as high priority. The sales team was flooded with the wrong tasks the next day, while truly high-value customers had no one following up.
The supervisor first had the person making the change call it out at the tea table. But the voice was quickly drowned out by other matters; no one checked the trial calculation results, no one knew which storefronts would be affected, and no one reserved time to roll back to the old rules.
The new process wrote each change onto a single form: what to change, why to change it, which ledgers and customers are affected, how to run trial calculations, who stamps approval, when to release, and how to roll back after failure. Small changes took the fast track; large changes required review.
They also put the mnemonic rhymes, abacus versions, seal permissions, ledger mappings, and handling paths into the same change log. Changing only one place was not considered complete; anything that would change the behavior of the accounting office had to leave a record of causes and consequences.
The first release under the new process looked half a day slower. But the storefronts got the instructions in advance, sales knew which tasks would be recalculated, and the old rules could be restored in time. The city lord later admitted that good change rules don't block change; they make change visible, controllable, and accountable, and the city therefore dared to keep running fast.
Later the city needed to adjust the follow-up reminders again. By old habit, this was just changing a phrase; by the new rules, it would affect sales order, customer experience and responsibility. Everyone ran a trial calculation for one night in advance and found that the old accounts of two shops would be falsely triggered, so they added safeguards before release. From then on, speed no longer equaled who was fastest. What was truly fast was fewer reworks after a change is released, fewer accidental harms, the ability to roll back, and everyone knowing which path the next change would take. Later, during the retrospective, everyone wrote this lesson into the daily rules: first look at where on the site the result was truly changed, then decide what to keep, what to repair and what to restrict.