Why your HR policies aren’t working

I’ve spent 25 years in HR and I hate policies.

Not the principle. The principle is sound. People need clear frameworks. Managers need to know what good looks like. Organisations need consistency. I have no argument with any of that.

What I hate is what we’ve turned them into.

Forty pages that nobody reads. Guidance notes that nobody opens. FAQs that answer questions nobody asked. All wrapped up and handed to managers who are already stretched, with a “there you go” and a sense that our job is done.

It isn’t.

The policy as shield

When something goes wrong in an ER case, and it will, the first thing most HR teams reach for is “but we provided the policy.” As if handing someone a document they will never read counts as equipping them to manage people well. As if it absolves us of all responsibility.

We have built a system that protects HR’s position and leaves managers floundering. Then we wonder why they don’t follow the process.

They didn’t follow it because they couldn’t find it. Or they found it and couldn’t understand it. Or they understood it and couldn’t see how it applied to the actual human being sitting in front of them.

That is not a manager problem. That is a policy problem.

How we got here

Most HR policies start with good intentions and end up bloated because of fear. Fear of legal challenge, fear of inconsistency, fear of not covering every conceivable scenario. So we add clauses. We add appendices. We add flowcharts. Each one makes perfect sense in isolation. Together, they create something that no reasonable person would sit down and read voluntarily.

There is also a professional pride problem. HR teams spend weeks crafting policy suites. The length becomes a proxy for thoroughness. A two-page policy feels lightweight, even if it covers everything a manager needs. A thirty-page policy feels comprehensive, even if nobody gets past page four.

The result is a library of documents that exist primarily to demonstrate that HR has done its job, rather than to help anyone else do theirs.

What managers actually need

Disciplinaries, grievances, absence reviews, performance conversations. The manager failures I see most often are not caused by ignorance or bad intent. They are caused by confusion.

The manager who did not realise they needed to offer the right to be accompanied. The manager who jumped straight to a written warning because they thought that was what the policy required. The manager who avoided having the conversation at all because the process felt too complicated to get right.

None of those managers were lazy. They were let down by tools that were designed for lawyers, not for the person who has to deliver a difficult message at 4pm on a Wednesday while also worrying about the team rota and a client deadline.

Managers need policies that are short. Clear. Written in language they can follow when they are tired, stressed, and short on time. If it needs a glossary, it is too long. If it needs an FAQ, it was not clear enough in the first place.

The real test

Here is a useful test for any HR policy. Give it to a line manager who has never seen it before, someone who has been in post for about six months, someone who is good at their job but has never managed a formal process. Ask them to read it and then tell you what they would do if the situation arose tomorrow.

If they can tell you clearly, your policy works. If they look confused or start asking questions about things the policy was supposed to answer, it does not work. It does not matter how legally robust it is. It does not matter how many stakeholders signed it off. If the person who needs to use it cannot use it, it has failed.

Most policies fail this test. That should bother us more than it does.

What good looks like

The best HR policies I have seen share a few things in common. They are rarely more than a few pages. They tell you what to do, in what order, and where to go if you need help. They use plain English. They separate the “must do” from the “should consider” so that the essential steps are impossible to miss.

They are also paired with something else: a conversation. A proper briefing with managers about what the policy means in practice, what the common pitfalls are, and what support looks like. Not a one-hour e-learning module with a quiz at the end. An actual conversation with someone who knows the subject and can answer real questions.

That combination, a clear document and a real conversation, is what equips managers. A forty-page PDF on the intranet does not.

There is a difference between a long policy and a structured toolkit. Twelve short documents that each do one job well is not the same as a forty-page PDF. One sits in a drawer. The other gets used.

This is not about lowering the standard

I am not arguing against rigour. I am arguing against the illusion of rigour. A long policy is not a rigorous policy. A clear policy that people actually follow is.

We need policies. Organisations cannot run without them, and managers should not be expected to navigate employment law from memory. But we need to stop pretending that writing them is the same as making them work. The policy is not the endpoint. It is the starting point. What we do after we hand it over is where the real work begins.

If your managers are not following the process, the answer is probably not another policy update. It is probably a conversation about whether the process was ever designed with them in mind.