Get started
Blog · Methods

Chesterton's Fence: Why You Should Never Remove a Process Before Understanding Its History

Apply Chesterton's fence to business management: discover the hidden purpose behind existing workflows before deciding to eliminate or simplify them. · 5 November 2026 · Victoria · 7 min

Chesterton's Fence: Why You Should Never Remove a Process Before Understanding Its History
A wooden fence across a country road: G.K. Chesterton's allegory applied to organizational management.
FluidOps
Clarify your operational workflows
Safely map your processes and gain operational clarity without creating hidden vulnerabilities using FluidOps.
Discover FluidOps

Table of contents

The August 1, 2012 lesson: $460 million wiped out in 45 minutes

On Wednesday, August 1, 2012, as the opening bell rang on Wall Street, market maker Knight Capital prepared to test a new software component for routing equity orders. Eight servers needed updating before trading began. In a seemingly minor technical oversight, a technician failed to deploy the new code to the eighth server. Worse still, the update repurposed an internal configuration flag that had sat dormant in the codebase for nearly a decade (U.S. Securities and Exchange Commission, 2013).

On that neglected eighth server, the repurposed flag inadvertently activated an obsolete testing algorithm named "Power Peg," originally written in 2003. Back in 2005, its internal volume-limiting safeguards had been intentionally removed on the grounds of redundancy, yet the dead code was never purged from the environment. Unconstrained by any safety limits, the algorithm began buying shares at peak prices and dumping them immediately at a loss, firing millions of errant orders into the market. Within 45 minutes, Knight Capital lost $460 million, wiped out its equity capital, and was pushed to the brink of bankruptcy (U.S. Securities and Exchange Commission, 2013).

The Knight Capital disaster provides an unforgettable case study in systemic blindness: an engineering team removes safeguards deemed redundant, retains legacy rule fragments without grasping their dependencies, and triggers a catastrophic chain reaction. What holds true for algorithmic trading applies just as directly to everyday business workflows. When a newly appointed manager casually scraps an approval form or a recurring sync meeting in the name of "streamlining," they court the exact same silent disaster.

Chesterton's parable: the reformer's paradox

This impulse to tear things down was examined as early as 1929 by British writer and philosopher G.K. Chesterton in his essay collection The Thing: Why I Am a Catholic. In Chapter IV, Chesterton formulated what has become one of the most powerful mental models in organizational decision-making: the allegory of the fence.

Chesterton describes a fence or gate erected across a country road. Two travelers come upon it. The impatient, modern reformer immediately insists: "I don't see the use of this; let us clear it away." To which the wiser reformer responds: "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" (Chesterton, 1929).

Chesterton's principle reverses the burden of proof. In business management and project execution, not understanding a procedure does not prove it is useless; it simply reveals a knowledge deficit in the observer. Robert K. Merton (1936) warned against what he termed the "imperious immediacy of interest": decision-makers, captivated by the quick win of cutting a step, willfully ignore the complex web of secondary effects that keeps the wider system intact.

The drive to eliminate operational friction often springs from a genuine desire for efficiency. Yet, much like the intricate components found in a Rube Goldberg machine, every procedural layer was initially introduced to solve an earlier problem. Ignoring that origin story condemns reformers to relive the very failures their predecessors worked to resolve.

The anatomy of organizational scars: where company rules really come from

Why do growing companies end up cluttered with purchase order sign-offs, redundant validation spreadsheets, and multi-tier approval chains? Organizational sociology offers a clear answer: processes are institutional scars (Sitkin and Bies, 1994).

Rarely designed out of sheer bureaucratic whim, these hurdles almost always represent the operational response to a past crisis: an unpaid invoice that threatened payroll, an employment tribunal, a catastrophic delivery error that cost a marquee account, or a critical inventory stockout. To ensure that specific failure never recurred, leadership instituted a procedural guardrail. Years later, the original crisis has faded from company memory, but the scar remains carved into the operating manual.

Employee turnover accelerates this vulnerability. New hires immediately feel the day-to-day friction of the rule—the minutes lost chasing a signature or filling mandatory input fields—while remaining completely blind to the operational risk the rule quietly neutralizes in the background. This is survivorship bias at work: because no disaster has occurred for years, leadership casually concludes the safety net is superfluous.

In her study of the Challenger space shuttle disaster, Diane Vaughan (1996) termed this dynamic the "normalization of deviance." When teams observe that bypassing a protocol produces no immediate catastrophe—a classic case of non-event feedback—they wrongly assume the protocol was needlessly restrictive. The gradual dismantling of protective boundaries inevitably paves the way for systemic failure.

This dynamic is further complicated by unofficial workarounds. As Steven Alter (2014) demonstrated, front-line staff constantly compensate for software and procedural limitations through informal routines: an off-the-books tracker, or a quick phone check before dispatching an order. When leadership abruptly bans or eliminates these informal steps without understanding the underlying gap they compensate for, day-to-day execution grinds to a halt (Alter, 2014).

Disentangling bureaucracy from protection: Red Tape vs. Green Tape

Honoring Chesterton's fence does not mean protecting obsolete rules forever. Not all operational checks hold equal value. In public administration and organizational theory, the distinction between pointless bureaucracy ("red tape") and effective, protective structure ("green tape") gives leaders an objective diagnostic framework (Bozeman, 1993; DeHart-Davis, 2009).

The green tape theory formulated by Leona DeHart-Davis (2009) posits that an organizational rule is healthy and functional when it meets five core requirements:

Conversely, pathological red tape refers to procedural burdens that serve only past habits, carry costs disproportionate to any benefit, or stem from compliance rules that have long expired (Bozeman, 1993). The table below outlines how to evaluate a process before taking action:

Analytical Dimension "Protective Scar" Process (Green Tape) "Residual Waste" Process (Red Tape) Political Rule (Internal Rent-Seeking)
Historical origin Direct response to a documented incident or failure. Sediment from retired software versions or legacy workflows. Created to protect an individual manager's budget or headcount.
Cost / Risk ratio Low compliance cost (e.g., 5 min) vs. high financial or regulatory risk. High execution overhead for negligible or undefined returns. Artificial friction designed to centralize gatekeeping authority.
Team understanding Understood by tenured staff, easily explained to new hires. Unclear to everyone ("We've always done it this way"). Defended solely by the specific department holding the sign-off power.
Recommended action Retain or automate the verification without weakening the safeguard. Eliminate after running a rollback audit. Dismantle by restructuring operational governance.

Cutting rules indiscriminately is a classic management trap. As systems thinking reminds us, workflow architecture mirrors an organization's communication boundaries: this is the essence of Conway's law. Eradicating a procedural checkpoint without redesigning the underlying information flow simply shuffles chaos into an adjacent team.

The perils of conservatism: when the fence protects a turf war

While invaluable against reckless change, Chesterton's principle creates severe organizational risks if treated as dogma. Leaders must watch for three major blind spots:

First, the trap of analysis paralysis. Demanding an exhaustive historical pedigree before modifying any operational micro-step freezes the organization in place. In fast-moving competitive environments, the cost of inaction frequently dwarfs the cost of a reversible, well-contained experiment. Meir Lehman (1980), in his foundational laws of software evolution, demonstrated that systems naturally increase in internal complexity over time unless actively restructured. Inaction is never neutral: it fuels entropy.

Second, the decay of institutional memory. In growing companies with high turnover, the leaders who originally instituted a control five or ten years earlier have often moved on without leaving documentation. Applied rigidly, the maxim "touch nothing until you understand everything" ends up sanctifying absurd bottlenecks simply because the historical context was lost with someone's departure.

Third, the naive assumption of good intentions. Chesterton assumes the fence was erected in good faith for the public good. In real-world organizations, however, many procedures were never designed for operational efficiency: they were introduced to serve personal career ambitions, guard departmental silos, or extract administrative deference. When investigating the "why" reveals that a checkpoint exists solely to preserve managerial territory, tearing it down becomes an immediate leadership duty. Similarly, beware of justifications based on past investments: that is a textbook manifestation of the sunk cost fallacy.

A five-step protocol to remove a process safely

To reconcile day-to-day operational agility with Chesterton's caution, apply this pragmatic audit protocol before dismantling any existing rule:

Streamline your workflows with FluidOps

Auditing and cleaning up business operations should never rely on guesswork. FluidOps brings your processes together into a unified workspace featuring visual Kanban boards, Gantt charts, and native Scrum views. This full operational visibility allows you to spot delivery bottlenecks instantly, distinguish vital green tape from unproductive red tape, and keep project schedules synced with Google Calendar and Outlook. The Eisenhower matrix and other workload optimization tools are included from the free plan onward.

FluidOps keeps pricing transparent and predictable: a free plan at €0 per month to get started risk-free, an Individual plan at €12 per month (or €120 billed annually), and an Enterprise plan starting at €12 per seat per month on annual billing. Explore the complete feature set and align your team on our pricing page.

Conclusion: subtract with clarity

Effective management does not mean piling on checks to eliminate all uncertainty, nor does it mean tearing down rules out of an uncritical desire for novelty. It demands the intellectual humility Chesterton described: acknowledging that what currently looks like an obstacle was once a colleague's smart solution to a very real problem.

Before scratching a step off a workflow diagram or cutting an approval gate, take the time to listen to the operational history behind it. Once you know exactly what the fence was built to protect, you can decide with total confidence whether to strengthen it, automate it, or tear it down for good.

Frequently asked questions

What is Chesterton's fence in business management?

It is a decision-making heuristic stating that you should never eliminate or alter a rule, process, or workflow step until you fully understand why it was put there in the first place. Not seeing the immediate purpose of a procedure indicates a knowledge deficit, not its uselessness.

What is the difference between red tape and green tape?

Red tape refers to counterproductive, burdensome rules that consume time without delivering real value or preventing risks. Green tape, by contrast, describes well-defined, consistent, and widely accepted rules that guide operations effectively and protect the organization against critical failures.

How can you tell if an old business process is still necessary?

Interview veteran employees to uncover the original incident that prompted the rule, compare the recurring cost of compliance with the downside risk it prevents, and run a reversible, monitored trial suspension across a restricted operational scope.

Doesn't Chesterton's fence risk stalling innovation?

It can lead to inertia if misapplied dogmatically, especially when institutional memory has vanished or when a legacy rule merely protects a departmental turf war. To innovate safely, focus on reversible decisions with built-in rollback mechanisms.

Sources

← BackAll articles Next article →The Hawthorne Effect: Does Being Watched Really Change How We Work?