Before You Pull the Fence, Find Out Who Built It
You want to cut a step that slows the crew down, and nobody can say why it exists. This shift, ask three people what goes wrong if you stop before you touch it.

The rule everybody hates is usually the rule nobody can explain. That is the dangerous one.
Picture a second-shift lead who takes over a line and finds a sign-off step that adds four minutes to every changeover. Nobody on the crew knows why it exists. The old supervisor is gone. The lead does the sensible thing and cuts it. Two weeks later a wrong part runs for three hours before anyone catches it. The step was a cheap catch for a mistake that happened once, years ago, and never happened again because of the step.
It is one of the oldest traps in leadership, and it has a name.
The fence
In The Thing (1929), G. K. Chesterton wrote about a fence across a road. A reformer sees it, says he cannot see the use of it, and wants it cleared away. Chesterton’s answer, in short: if you do not see the use of it, you may not clear it. Go away and think. Come back when you can tell me what it is for. Then we can talk about tearing it down.
People call this Chesterton’s Fence. The shop floor version below is mine, not his.
Two things people get wrong about it.
First, it is not “keep the old rule.” Chesterton’s point is that you earn the right to remove it. The test is understanding, not tradition.
Second, it is not an excuse to stall. A leader who says “we can’t touch it until we understand it” for six months has just built a new fence.
What it costs
Lose the fence blind, and you pay twice. You pay for the failure it was stopping. And you pay in trust, because the crew watched you change something you could not explain, and they will remember that the next time you ask them to follow a new one.
Keep every fence blind, and you pay a different bill. The crew learns that rules are weather. Nobody asks why. The good ones and the dead ones get the same shrug.
The move: a fence check
Before you cut, change or kill any rule, step or form, do this. Start in one shift. Some checks take longer, and that is fine.
1. Say it out loud: “I do not see the use of this.”
2. Ask three people: the longest-serving operator, the person who does the step, and the person downstream who receives the result. One question: “What goes wrong if we stop?”
3. Look for the trace. An old nonconformance, a customer complaint, a near miss, a note in a binder, a line in a procedure. Most fences leave tracks.
4. Decide in one of three ways.
Reason found and still real: keep it, and write the reason on the step.
Reason found and gone: remove it, and write down why it no longer applies.
No reason found: keep the step while you check whether it protects people, product, law or customers. Only trial a removal if the consequence of being wrong is low risk and easy to undo. If you do trial it, name the owner, the stop condition and the check date before the first shift runs without it.
That fourth path keeps you from freezing without letting you gamble. A trial with an owner, a stop condition and a check date is a reversible decision, and you were hired to make those. A step that guards a person, a customer or the law is not a trial. It stays until you know.
Two fences, two answers
Here is what the check looks like when it works.
The fence that came down. A packing area has a rule that every carton gets a second tape strip across the bottom. It costs a few seconds a box and a lot of tape. The new lead asks the three questions. The longest-serving packer remembers a box supplier from years back whose cartons split under weight. The person who does the step does not know. The shipping clerk downstream says the old cartons were replaced long ago. The lead looks for the trace and finds the old supplier’s name on a damage report in a binder, and the current supplier’s carton rating on the spec sheet, which is well above what the heaviest order weighs. Reason found and gone. The lead names the check before changing anything: the shipping clerk will count damage claims for the next four weeks, and if one bottom-seam failure comes back, the second strip returns that day. Four weeks later, no claims. The lead tells the crew at the huddle what they found and why the step went away, and writes the reason in the packing instructions so the next lead does not bring it back by habit.
The fence that stayed. A machine area has a rule that the operator calls the lead before restarting after any jam, even a small one. The crew hates it. It slows everything down, and most jams are nothing. The lead asks the three questions. The operator says it is a waste of time. The longest-serving operator says there was an injury on that machine years ago, during a restart. The maintenance tech downstream says a jam on that machine can leave a guard out of position without anyone noticing. The lead looks for the trace and finds the incident report and the procedure that came out of it. Reason found and still real. The step stays. The lead does two more things. First, the reason goes on the machine in plain words: “Call before restart. A jam can move the guard.” Second, the lead checks with the next shift a week later to see whether the calls are happening, because a rule the crew understands is a rule the crew keeps. The complaints drop, not because the step got shorter, but because now everyone knows what it is for.
Look at what was the same both times. Three questions. One search for the trace. A decision written down. A check on a date. And the crew told what was found. The answer was different. The method was not.
The invisible safeguard
There is a reason working safeguards get cut. You notice the cost of a step every shift. You almost never notice the benefit, because a prevented failure leaves nothing to see. The better a safeguard works, the more it looks like waste.
That is why “nobody can remember the last time this went wrong” is not proof the step is useless. It may be proof the step works.
One way to make the benefit visible is to count what the step catches, not only what it costs. If a sign-off caught two wrong parts this year, write that on the step. A safeguard with a score next to it is a lot harder to call waste, and the count tells you the day it stops catching anything.
It is also why this question is a good one: which mistake would be more expensive to find out about on a Friday afternoon? Cutting a step that mattered, or keeping a step that did not? If the answer is not obvious, keep the step until it is.
Why this is people work, not process work
Fences are not only steps on a line. Think of the family dinner rule, the Monday meeting, the “always copy the lead” email habit, the committee that approves everything. Somebody built each one to solve something. Ask who and why before you change the way people live and work together.
And when you find the reason, tell the crew. That one act turns a rule from an order into an agreement. A crew that knows why a step exists will tell you the day the reason goes away. A crew that does not know will just stop doing it when nobody is watching.
When you are not the one who decides
This works from the other side too. If you are the operator who thinks a step is dead weight, do not just skip it, and do not just complain about it. Bring the lead the fence check already started. “I do not see the use of this. I asked Dana and the shipping desk what goes wrong if we stop, and nobody knew. Can we find out?” That is not a complaint anymore. That is a proposal the lead can act on.
And if you are the one who built a fence, write down why. The next person to stand in front of it deserves better than a guess.
Tomorrow
Pick one rule in your area that the crew complains about and nobody can explain. Start the fence check this shift: ask the three people the one question, and look for the trace. If the step protects people, product, the law or a customer, keep it while you look. At the next huddle, tell the crew what you found, what you decided, and the date you will check. If you find the reason, write it on the step so the next lead does not have to guess.
Go deeper: Temporary Becomes Permanent and the free 5S course.
Source: G. K. Chesterton, The Thing (1929), chapter “The Drift from Domesticity.” The examples in this article are built illustrations, not events from my work.
Marc Bradburry · bigbeardedginger.com/before-you-pull-the-fence-find-out-who-built-it/