Every organization, every codebase, every family has a rule nobody can explain. A form that asks for information no one reads. A step in the process everyone quietly skips. A field left blank in every record because filling it in never mattered — until, one day, it did.
The instinct, especially for a newcomer, is to treat this as an obvious inefficiency and remove it. G. K. Chesterton, writing in 1929, described the shape of that instinct exactly: picture a fence built across a road for no reason you can see. The reformer says, “This is clearly useless, let’s tear it down.” Chesterton’s answer is not “leave it alone forever” — it’s a test:
“If you don’t see the use of it, I certainly won’t let you clear it away. Go away and think. Then, when you can come back and tell me that you do see the use of it, I may allow you to destroy it.”
What the test actually asks for
Chesterton’s fence isn’t an argument for conservatism. It’s an argument for sequencing: understand, then act — not act, then discover why you shouldn’t have. The fence might genuinely be useless. It might have been built for a reason that expired years ago. The principle doesn’t forbid removing it. It forbids removing it before you know what it was for.
This matters most exactly where the naive reformer is most confident — legacy processes, reporting lines, approval chains that look like pure friction to someone encountering them fresh. The people who built them were usually responding to a real failure mode. Maybe that failure mode is gone. Maybe it isn’t. You can’t tell the difference without going and looking.
Where this connects
Chesterton’s fence sits next to scout mindset: genuine intellectual honesty means understanding the strongest version of a position before you argue against it. Tearing down a rule without knowing its origin is the opposite move — arguing against a position you never bothered to hear.
Closing
The fence isn’t sacred. But “I don’t see the point of this” is the start of an investigation, not the end of one.