A fence across a road is an irritation if you do not know why it is there. Most of us have met one: the form that needs three signatures, the gate that stays locked, the rule nobody can explain. The urge to tear it down is natural. G.K. Chesterton, the English writer prominent in the early twentieth century, suggested a small delay before acting on that urge.
Do not remove a thing until you understand why it was established and what function it serves.
What the Principle Actually Says
The rule is short. Before you remove a thing, a rule, an institution or a tradition, find out why it was put there. Chesterton argued that a reformer who cannot explain the purpose of an obstacle has no business clearing it away.
The logic is plain bookkeeping. Fences take time, money and effort to build. Someone paid those costs, and people rarely pay them for nothing. That does not make the fence good. It only places the burden of understanding on the person who wants it gone.
It is also not a vow to keep everything as it is. The principle asks for an explanation, not deference. If you learn what the fence was for and find that the reason has expired, you may take it down with a clear conscience.
The Reverse Version: Asking Why Something Is Absent
The same habit runs in the other direction. Before building something that does not exist, ask why it does not exist. There may be a good reason: costs, risks, or conditions that make the thing unworkable.
The food desert shows the test at work. The USDA defines one as a low-income urban neighborhood with no grocery store within a mile, or a rural community with none within 10 miles. Advocates say subsidies can fill the gap. A critic at the Adam Smith Institute asks the reverse question: why have private grocers not already come? That critic argues planners tend to skip it.
The evidence is mixed in a useful way. Capitol News Illinois and ProPublica looked at 24 stores in 18 states funded through the federal Healthy Food Financing Initiative in 2020 and 2021. As of June, five had closed and six had not yet opened, with reporters citing trouble finding locations and limited access to capital. A defender of subsidies can read that as poor program design. A skeptic can read it as proof the problem is harder than it looks. The numbers alone do not settle it, and the excerpt does not give wider outcome data.
A Historical Case: Adam Smith and Lending Rates
Adam Smith never used the phrase, but a Regulatory Policy Institute essay finds the habit in his work. He supported a cap on lending rates, set at 5% in 1776, though it was a straight price control on lending and borrowing. He did not attack it, and the essay credits his interest in how restrictive rules came to exist.
His account of that origin is worth keeping. Partial interests, meaning sub-groups pursuing their own causes, lobby legislatures for favorable laws and give little weight to wider effects. Knowing that history is part of knowing the fence.
Caution is due here. The sources do not explain how Smith justified the 5% cap on its own terms. Reading the principle into that particular judgment would claim more than the record shows.
The Case Against Over-Applying the Principle
Fences are kept up by people, and those people may like the fence where it is. Civic Innovations notes that annual budgeting looks different to a legislative budget committee or an inspector general's office than it does to a product team. Whose explanation you accept shapes what you conclude.
That is the weak point. A fence built for a narrow group can stand long after its purpose has faded, and if you ask only what it does now, its beneficiaries may write the answer. The sources raise the maintainer problem but offer no full remedy.
Reformers have a sharper reply. If nobody can state a fence's purpose, the honest conclusion may be that the purpose was lost, not that it was wise. Demanding justification can become a way to stall change forever.
Using the Principle as a Working Checklist
Start with history. Ask why the rule was made and whose interests shaped it. Lobbying by partial groups can explain features that look arbitrary.
Then test whether the reason still holds. Civil service hiring rules grew from nineteenth-century reforms meant to end a spoils system that handed out government jobs as political rewards. Whether they still do that work, and at what cost, is a fair question for both sides.
Look from the side of those who depend on the obstacle. Procurement rules guard against bid rigging, vendor capture and favoritism. Budget cycles create accountability points. To someone who sees only delay, those functions are invisible.
Before building, ask the reverse question. And ask who maintains the thing and what they gain from it.
Be honest about what the sources leave out. They give no test for when a fence is no longer worth keeping and no method for weighing an old reason against present needs. Two of the three are commentary pieces, and all are excerpts. The principle gets you to the right question. The judgment about costs, evidence and who bears the consequences is still yours to make.
Sources
Marcus Adeyemi-Holt is a house writer for Deeperpectives, where he examines how ordinary routines reveal larger patterns in work, memory, and place. He draws on years of reporting on municipal records and oral histories to trace the quiet forces that shape everyday life.
