Chesterton's Fence: New Ideas vs. Institutional Memory
Image generated with AI.
Leadership · Team Culture · Deep Identity
⏱ Reading time: 4 min.
One fall afternoon, in a meeting that should have been routine, I watched a newer director go quiet.
I knew the look. They had an idea. A good one, probably. The kind that turns a flat revving engine into something that purrs and pours.
And across the table sat people who had been around the production bends. People who had tackled a host of challenges before this director ever walked into the building. Those stripes are daunting. They are supposed to be, a little.
So the idea stayed in their chest. And I watched them run the math that every newer person runs.
Is it worth saying? Or am I about to get a pat on the head?
I have sat on both sides of that table
I have been the one with the idea nobody wanted to hear. And I have been the one sitting behind the stripes, listening to a proposal while knowing something about why the current way exists that the person in front of me did not.
Neither seat feels good. The newer person feels dismissed. The seasoned person feels like the history they are carrying is being treated as stubbornness.
Most people frame this as a personality difference. Are you the kind of leader who pushes, or the kind who defers? Frame it that way and it becomes a generational argument. The newer person is impatient. The veteran is stuck. Everyone recognizes themselves in the flattering half and nothing changes.
But it is not a personality question. It is a discipline, and there is a test.
Do not take down a fence until you know why it is there
G.K. Chesterton wrote about this more than a century ago. Come across a fence in a field with no obvious purpose, he said, and the impulse is to clear it away. The wiser response is to go find out why someone built it. Then, and only then, you may be permitted to remove it.
That is not an argument for leaving things alone. It is the opposite. It is a rule about how you earn the right to change something.
And the test is simple enough to run in your head before you open your mouth.
Can you explain why the current way exists?
Not whether you agree with it. Whether you can say it out loud, accurately, in words the people who built it would recognize.
If you can, you have standing. If you cannot, you are not proposing an improvement. You are guessing in public, and everyone in the room can hear it.
Most of what looks like inefficiency in a long-running operation is not inefficiency. It is a scar. Somebody got hurt, or something got expensive, and the practice is what grew over the wound.
The test cuts both directions
This is where the conversation usually gets dishonest, because it tends to be written by someone senior aiming the advice downward.
The veteran fails the same test.
The leader who answers a real question with "we have always done it this way" cannot explain the fence either. They have simply stood next to it long enough that nobody asks anymore. That is not institutional knowledge. It is the absence of it, wearing seniority as a disguise.
Two people, one failure. One never learned why the fence is there. The other forgot, and stopped noticing they had.
The organizations that stay sharp are the ones where both people can answer the question, and where asking it is ordinary rather than a threat.
So how do you bring the idea without the pat on the head
Three moves, and none of them require anyone's permission.
Before you propose the change, go find the person who was there when the fence went up. Not your manager. The operations lead with twenty seasons, the coordinator who has been in the building longer than the department has existed. Ask what happened. There is almost always an incident behind the practice, and almost nobody has asked them about it in years.
Then lead with what you learned. "I understand this came out of what happened a few seasons back. Here is what I think has changed since then." That sentence does something no amount of enthusiasm can. It tells the room you are not erasing the people who came before you, and it makes the idea very hard to pat on the head.
And if you are the one being asked, answer the actual question. If you cannot remember why the fence is there, say so out loud. That is not a loss of authority. It is the fastest way to find out whether the fence is still doing anything at all.
Why this is sharper in live events than almost anywhere else
In an organization that persists, someone remembers. The knowledge lives in people who stay.
We do not work that way. We assemble a team, produce an event, and disperse. Seasonal staff leave. Contractors finish. Volunteers move on. The reasons behind our practices walk out the door every single year, and what stays behind is the practice without the reason attached to it.
So the fences accumulate. And fewer and fewer people can account for any of them.
That is the actual risk. Not a newer person moving too fast, and not a veteran holding too tight. It is an organization full of rules nobody living can explain, defended by people who inherited them and challenged by people who cannot see them.
The honest version
You do not have to choose between having ideas and being teachable. That was never the trade.
You have to earn the change. Find out why the fence is there. Then make your case, in front of the people whose scar it is, with the reason for it in your own mouth first.
Do that and you will find something worth knowing. Most of the time the fence comes down easily, because the person guarding it had been waiting for someone to care enough to ask.
As for that meeting, I keep thinking about the two questions that were sitting right there and never got asked.
Nobody asked the newer director what they were holding.
And the newer director never asked why we do it the way we do.
Both questions were free. Neither one got spent. That cost is paid quietly, in every organization, all the time.
If you lead a team where good ideas keep colliding with long memories, that friction is not a personality problem to manage around. It is a culture question. And culture questions have answers.
The Leadership House
When the Same Conflicts Repeat Every Season
Rising Festival Leaders is a three-part strengths-based series that runs across your season, built for festival, venue, hospitality, and live events teams. Because a single workshop fades before load-out is finished.
See the Team Series →