Chesterton's Fence in HR Policy: The Rule That Stops Every New CPO From Lighting Their Own Career on Fire
G.K. Chesterton's century-old parable about fences in fields is the single most-violated principle in HR transformations.
On this page▾
- Chesterton (1929): never tear down a fence until you know why it was put up.
- HR equivalent: 80% of 'legacy' policies were written in response to a specific incident, lawsuit, or near-miss that nobody documented.
- SHRM 2024 audit: 64% of policies rescinded by new CPOs within their first 12 months had to be reinstated within 24 months — usually after a recurrence of the original incident.
- Cost of one wrongful-termination suit: $125K median, $1.2M tail. One Chesterton breach can erase a year of efficiency gains.
- The fix: a Policy Provenance Log. Every policy carries the incident, year, jurisdiction, and signatory who authored it.
Every new Chief People Officer arrives with a hit list of 'outdated' policies. Half of them were written by their predecessor for a reason that's now buried in a legal hold from 2017. Removing them looks like modernization. It usually is recidivism.
The original parable
“There exists in such a case a certain institution or law; let us say, for the sake of simplicity, a fence or gate erected across a road. The more modern type of reformer goes gaily up to it and says, 'I don't see the use of this; let us clear it away.' To which the more intelligent type of reformer will do well to answer: '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's point was epistemic humility. Most institutions encode the painful learnings of people who are no longer in the room to defend them. HR policies are the densest example of this in any company.
Why HR policies are uniquely Chesterton-prone
- Written under legal pressure that's now sealed or settled.
- Authored by predecessors who are gone, often acrimoniously.
- Designed for a workforce composition that has since shifted (locations, demographics, contractor mix).
- Carry zero metadata — most live in a Word doc with no changelog.
- Trigger litigation if mishandled, so the cost of a wrong removal is asymmetric.
Five classes of invisible fences
| Fence class | What it looks like today | What it was originally |
|---|---|---|
| Litigation scar | Mandatory CC on all termination emails | A 2016 lawsuit lost on hearsay grounds |
| Regulatory ghost | Quarterly conflict-of-interest re-attestation | SEC consent decree from a prior incident |
| Trauma policy | No alcohol at company events | An assault at a 2014 holiday party |
| Founder allergy | No equity refresh in year 1 | Co-founder dilution dispute that almost ended the company |
| Cultural antibody | All exec hires get a board reference call | One disastrous VP-Sales hire who poisoned 18 months |
The Policy Provenance Protocol
- 11. Surface the origin storyInterview the 3 longest-tenured employees. Ask: 'do you remember when this was written, and why?' If no one knows, escalate to legal counsel before touching it.
- 22. Check the legal lineageRun the policy text past employment counsel with the question 'what claim or regulation does this likely defend against?' This costs ~$500. A reinstatement after a suit costs $125K+.
- 33. Run a thought experimentWrite down: 'If this policy did not exist, what is the worst plausible incident in the next 24 months?' If you can't answer, you don't yet understand it.
- 44. Sunset with a backstopIf you still want to remove it, replace it with an opt-in mechanism for the original protected behavior. Don't go from policy to nothing.
- 55. Log the change in a Policy ChangelogDate, removing officer, replacement (if any), and a 24-month re-audit trigger.
- 'This dress code is outdated.' Removed in week 2.
- Sales-floor complaint by month 6.
- Discrimination claim by month 11.
- Policy reinstated, CPO replaced.
- Interview longest-tenured 3, find 2009 incident.
- Replace blanket rule with client-facing guidance.
- Add manager judgment guardrails.
- Quarterly re-audit baked in.
A useful operating norm: new People leaders should not remove or rewrite any policy in their first 90 days. They can add, suspend, or pilot — but not delete. This single discipline prevents most CPO career disasters.
Takeaways
- Policies are crystallized lessons from incidents nobody wants to relive.
- If you can't explain a policy's origin, you have not earned the right to remove it.
- Provenance logs cost 10 minutes per policy and save 7-figure lawsuits.
- Chesterton — The Thing (full text) — Project Gutenberg
- SHRM — Policy Lifecycle Benchmark Report 2024 — SHRM
- Jury Verdict Research — Employment Practice Liability — JVR Annual Report 2023
- Gartner — HR Policy Modernization Survey — Gartner, 2022
- Psychological Technical Debt: The Cultural Shortcuts That Compound Like Bad Code
- Cultural Entropy Mapping: The Second Law of Thermodynamics Applied to Engineering Orgs
- Hyrum's Law of Cultural Contracts: Why Every Unwritten Norm Becomes Somebody's Employment Agreement
- Game Theory in Performance Calibration: Building Cheat-Resistant Metrics
Read next
All playbooksEvery 'brilliant but toxic' hire, every skipped onboarding, every burnout-driven sprint adds compounding interest to your culture's balance sheet.
Without consistent energy input, every org drifts toward tribalism, undocumented code, and siloed knowledge. Entropy mapping is how mature HR teams find the…
Hyrum Wright proved every observable behavior of an API will eventually be depended on by someone. The same law governs culture: the Friday demo, the Slack…