The Principle Behind Chesterton's Fence
G.K. Chesterton once proposed a thought experiment. Imagine you encounter a fence built across a road. A reformer says, "I don't see the use of this fence; let's clear it away." A wiser person responds, "If you don't see the use of it, I won't let you clear it away. Go away and think. Then, when you can tell me why it was built, I may allow you to tear it down."
This is Chesterton's Fence — the principle that you should never remove something until you understand why it exists in the first place. It is one of the most practical mental models for anyone who builds, manages, or improves systems.
Why This Matters More Than Ever
We live in a culture that celebrates disruption. Move fast and break things. Challenge the status quo. Tear down legacy systems. These mantras have genuine value, but they become dangerous when applied without understanding.
Every existing system, process, or tradition was put in place for a reason. That reason might be outdated. It might be wrong. But it exists, and ignoring it means you are making changes based on ignorance rather than insight.
The cost of removing something you do not understand is almost always higher than the cost of taking time to understand it.
Real-World Examples
In software engineering: A developer inherits a codebase and finds a mysterious function that seems to do nothing useful. They delete it. Two weeks later, a critical edge case breaks in production — the function handled a rare but catastrophic scenario the original developer had encountered years ago. The fence existed for a reason.
In management: A new manager joins a team and immediately eliminates the weekly standup meeting because it seems like a waste of time. Within a month, communication gaps emerge, deadlines slip, and small problems escalate into crises. The meeting was the team's only consistent synchronization point.
In public policy: A city removes a "redundant" regulation on building materials to cut costs. Years later, a flood reveals that the regulation existed because the area was historically prone to water damage. The knowledge was embedded in the rule, not in the memories of current officials.
How to Apply Chesterton's Fence
Step 1: Pause before removing. When you encounter something that seems pointless — a process, a rule, a tradition, a piece of code — resist the urge to eliminate it immediately.
Step 2: Investigate the origin. Ask the people who were there when it was created. Read the documentation. Look at the history. Understand the context in which the decision was made.
Step 3: Identify the problem it solved. Every fence was built to address something. Maybe it was a real threat. Maybe it was a perceived one. Either way, understanding the original problem tells you whether the fence is still needed.
Step 4: Decide with full context. Once you understand why the fence exists, you can make an informed decision. Maybe the original problem is gone and the fence should come down. Maybe the problem persists and the fence needs reinforcement. Either way, your decision is grounded in understanding rather than assumption.
Building a habit of pausing before changing things is powerful. If you want to internalize mental models like Chesterton's Fence, KeepRule helps you save and revisit the thinking frameworks that improve your judgment over time.
The Balance Between Caution and Progress
Chesterton's Fence is not an argument against change. It is an argument against uninformed change. The distinction matters enormously.
Some of the worst decisions in business, technology, and governance come from people who were confident they understood a system but had only seen the surface. They tore down fences without knowing what they kept out.
The best decision-makers combine a bias toward action with a discipline of understanding. They move quickly, but they never skip the step of asking "why does this exist?"
Before you remove the next fence in your path, take a moment to understand who built it and what it was guarding against. That moment of curiosity might save you from a very expensive mistake. Explore more thinking tools like this on the KeepRule blog and start building a personal library of mental models with KeepRule.
Top comments (0)