Change feels exciting. It promises progress, fresh thinking and the chance to fix what looks broken. In workplaces, governments and communities, people often say, “That rule doesn’t make sense anymore,” or “We’ve always done it that way, but we shouldn’t.” Sometimes they’re right. But as G. K. Chesterton warned a century ago, rushing to remove what you don’t understand can cause bigger problems than the ones you set out to solve.
Chesterton illustrated his point with a simple image. A man finds a fence built across a road and decides it’s pointless. He plans to tear it down. A wiser companion stops him and says, “If you don’t see the use of it, I won’t let you clear it away until you do.” The message is plain: before changing or removing something, learn why it exists. Only then can you decide whether it should stay or go.
This idea, known as Chesterton’s Fence, applies far beyond literal fences. It reminds us that rules, systems and traditions often have hidden purposes. They might seem unnecessary today, but many were built to prevent problems that can easily return if we forget their origins.
When good intentions go wrong
History offers plenty of examples of reforms that failed because people ignored this wisdom.
In the 1950s and 60s, many Western cities cleared older neighbourhoods they considered “slums.” The aim was to modernise housing and improve living standards. Yet in the process, planners broke apart tight-knit communities, forced families out of their homes and destroyed local economies. The old housing had faults, but it also held social bonds that kept people connected. The planners had removed a fence without asking why it was there.
A similar story played out in education. Around the early 2000s, many schools replaced phonics-based reading lessons with “whole language” methods that seemed more modern. Only later did research show that phonics was crucial for literacy, especially for struggling readers. Reformers had scrapped an old system without fully understanding what problem it had been solving.
Even in business, the same mistake happens. A company might remove its peer review step in project approvals to save time. At first, things speed up. Then small errors slip through, quality drops and clients complain. Managers soon reinstate the process. The fence had been invisible until it was gone.
When organisations apply the same wisdom
Some organisations have built Chesterton’s lesson into their culture. They don’t use his name, but the principle runs through their practices: never remove or replace something until you know why it exists.
The British civil service is one example. Its slow pace of reform often frustrates politicians, but that caution exists for a reason. Senior officials understand that many long-standing policies protect essential functions such as welfare payments and public safety. Before making changes, they study the history and purpose of existing systems. What looks like resistance is often deliberate care.
NASA learned a similar lesson through tragedy. After the Challenger and Columbia shuttle disasters, the agency introduced strict controls on change. Every checklist and procedure now has a documented reason behind it. Engineers cannot alter a step without first understanding its purpose. This discipline prevents the quiet assumptions that once led to catastrophe.
Toyota’s famous kaizen philosophy also mirrors Chesterton’s thinking. Workers are encouraged to improve production processes, but only after they grasp how the current system works. They must ask why each step exists before suggesting changes. That approach produces steady, informed progress instead of careless disruption.
The U.S. military takes the same approach through its “lessons learned” system. Every policy, training method and field procedure is recorded with the story of how it came to be. New leaders who want to alter something must first review that history. It prevents the repetition of old mistakes under new names.
The aviation industry might demonstrate the principle best of all. Every safety rule, checklist and training drill has its roots in an incident or accident. Airlines rarely change procedures without full investigation, because each rule has been bought with lessons from the past. These fences aren’t decorative. They save lives.
Across all these examples, the same pattern appears. Good organisations don’t fear change, but they approach it with respect. They pause, learn and then act. That’s Chesterton’s Fence in practice.
Balancing tradition and progress
Chesterton’s idea doesn’t call for blind loyalty to tradition. It’s a reminder that progress works best when grounded in understanding. The question isn’t whether to change, but how to change wisely. Before discarding what came before, we need to know what purpose it served.
In everyday life, the same rule applies. When we question family routines, community habits or long-standing social norms, it helps to understand why they exist. A rule that once served a clear purpose might still hold value today, or it might be ready for replacement. Either way, knowledge comes before action.
We live in an age of fast updates and short attention spans. It’s easy to believe that everything old is outdated. Chesterton’s Fence reminds us that some of what looks unnecessary is actually holding important things together.
Before reaching for the hammer, ask why the fence was built. The answer might save you from undoing something that still quietly works.