Chesterton's Fence
Before removing an inherited rule or structure, understand what problem it was intended to solve and whether that problem remains.
A rule can look pointless when its original context has disappeared. Someone arriving later may see only the inconvenience: a barrier, a form, or a step that seems to slow down work.
A library asks staff to record rare-book movements in a ledger. The step may appear old-fashioned, but it could help locate fragile items and identify handling patterns. A digital replacement should preserve those functions rather than merely eliminate the paper.
Chesterton's Fence is a principle of cautious reform: do not remove a structure until you understand why it was put there. The principle asks for inquiry, not automatic preservation of every inherited arrangement.
A company may require two people to approve a large payment. The process can feel bureaucratic, but it might have been introduced after duplicate invoices or unauthorized transfers caused losses.
The reverse is also possible. The original risk may be gone, while the control creates delay or exclusion. Understanding the history helps distinguish a continuing safeguard from an outdated response that deserves redesign.
The rule is especially useful when a change could have consequences beyond the person making it. Removing a moderation step, safety check, or public service requirement may affect people whose interests are not represented in the redesign meeting.
A software team wants to delete a code review requirement that slows releases. Old incident notes might reveal that the review caught risky changes. A short trial with targeted reviews could show whether the safeguard can be narrowed without losing its purpose.
Inquiry need not be endless. Look for decision records, incident reports, and people familiar with the system. If evidence is missing, a reversible pilot can test the change more safely than an immediate permanent removal.
Ask what failure the structure was intended to prevent, how often that failure occurs now, and whether the rule still addresses it. Then compare its present costs with the harms it plausibly prevents.
Preserve useful intent while improving poor implementation. A second approval might become an automated alert for low-risk transactions and a human review for unusually large or suspicious payments.
Treat inherited rules as hypotheses with histories. They deserve examination rather than reverence, and removal deserves evidence rather than impatience. That balance makes reform more informed and easier to explain.
When you encounter an inconvenient rule, what evidence would help you decide whether it protects a real need or simply survives by habit?
Psychological perspective
This is a reasoning principle, not a psychological diagnosis. It counters the understandable pull of present-day visibility: today's inconvenience is easy to see, while the historical problem that prompted a rule may be forgotten.
People can also become attached to familiar procedures. A fair review makes space for both concerns by asking what the rule does now, who benefits, and who pays its costs.
Thinking clearly
Write the suspected purpose of the rule in one sentence, then look for records or knowledgeable people who can confirm or revise that account.
List current benefits, burdens, and affected groups. Compare the rule with alternatives that might preserve its protective function while reducing delay or unfair exclusion.
When uncertainty remains, use a limited, reversible trial with a clear stop condition. Monitor the failure the old rule addressed, not just the convenience gained by removing it.
They deserve examination rather than reverence, and removal deserves evidence rather than impatience.
What original problem might an inherited safeguard have addressed, and how would you test whether it still matters?