Fable
No one could say which notice ruined the business
The pharmacy had a set of notice templates for writing replies to customers. The manager felt the wording was too harsh, so he had the clerk revise a few sentences. The next day, return complaints decreased, and everyone thought the revision was good.
A few weeks later, another clerk changed the opening again, a third person changed the compensation explanation, and a fourth person deleted the risk warning. The template still had the same name, and no one in the shop knew from which day the current version had been in use.
At first it was only minor confusion. Later, a compliance review found that some replies had unnecessary disclaimers; the customer success team then found that renewing customers were receiving a colder tone. Everyone argued about which change had caused it.
The shopkeeper first required that any future template change be announced in the group chat. But group messages were quickly buried, and no one could still work backward from the results to tell which version the live system was actually using.
During a major promotion, the return rate suddenly rose. The staff wanted to roll back to the old template, but could not find the last stable version, so they could only rewrite from memory, and the more they fixed, the more chaotic the problems became.
The new accountant treated templates as formal assets. Every revision had a version number, author, change description, applicable scenarios, launch date and associated evaluation results.
After a template is deployed, the system records which version each reply used. If metrics worsen, you can compare by version, switch via canary release, roll back, and lock the good version as the baseline.
Later someone proposed making the tone friendlier. The accountant did not block the change, but required testing it first on a small traffic share and comparing it with the old version on complaint rate, compliance hits and human takeover rate. The shopkeeper said: once a prompt participates in production, it is no longer a casually written sentence, but a versionable configuration that affects business results. Later the pharmacy put template changes on a fixed cadence. What proves effective stays, what brings risk is rolled back; every reusable sentence must know which version it came from and when it should be retired. When new apprentices join the shop, what they learn first is not which sentence sounds best, but which version is in use, why it is used, and which version to roll back to if something goes wrong. This made even the writers respect every change.