Skip to content
Playbook
AdvancedHRFounderCEO

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.

11 min read
On this page
60-Second Summary
  • 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.'
G.K. Chesterton, The Thing, 1929

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.
64%
of rescinded policies reinstated within 24 months
SHRM benchmark audit, 2024
$125K
median cost of one wrongful-termination suit
Jury Verdict Research, 2023
73%
of HR policies have no documented origin
Gartner Policy Provenance Survey, 2022

Five classes of invisible fences

Each looks redundant in 2026. Each is a load-bearing scar.
Fence classWhat it looks like todayWhat it was originally
Litigation scarMandatory CC on all termination emailsA 2016 lawsuit lost on hearsay grounds
Regulatory ghostQuarterly conflict-of-interest re-attestationSEC consent decree from a prior incident
Trauma policyNo alcohol at company eventsAn assault at a 2014 holiday party
Founder allergyNo equity refresh in year 1Co-founder dilution dispute that almost ended the company
Cultural antibodyAll exec hires get a board reference callOne disastrous VP-Sales hire who poisoned 18 months

The Policy Provenance Protocol

Before you delete any HR policy
  1. 1
    1. Surface the origin story
    Interview 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.
  2. 2
    2. Check the legal lineage
    Run 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+.
  3. 3
    3. Run a thought experiment
    Write 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.
  4. 4
    4. Sunset with a backstop
    If 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.
  5. 5
    5. Log the change in a Policy Changelog
    Date, removing officer, replacement (if any), and a 24-month re-audit trigger.
Bad removal vs Chesterton-safe removal
Bad removal
  • 'This dress code is outdated.' Removed in week 2.
  • Sales-floor complaint by month 6.
  • Discrimination claim by month 11.
  • Policy reinstated, CPO replaced.
Chesterton-safe removal
  • Interview longest-tenured 3, find 2009 incident.
  • Replace blanket rule with client-facing guidance.
  • Add manager judgment guardrails.
  • Quarterly re-audit baked in.
The 90-day rule

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.
Written by Pawan Joshi.Sources cited inline.
First published 1 Jun 2026See site changelog →