The System That Stopped Listening

There is a document I have seen in more organizations than I can count.

It is usually called something like the Progressive Discipline Policy or the Performance Management Framework or, in the more aspirationally worded versions, the Employee Development and Accountability Procedure.

It is always long.

The one I am thinking of specifically was forty-three pages. It had been written by a legal team, reviewed by HR, approved by a governance committee, and distributed to all managers through a learning management system that tracked completion. It covered every scenario. Verbal warnings. Written warnings. Performance improvement plans. Suspension with pay. Suspension without pay. The specific language required at each stage. The timelines. The documentation requirements. The approval chains.

It had been designed to protect the organization. And it did protect the organization. In the seven years since it was written, it had been used successfully in multiple legal proceedings.

What it had not been designed to do was help a manager have a conversation with an employee who was struggling.

That gap, between what the document said it was and what the document actually was, is the thing I want to talk about. Because the moment an organization stops listening is almost never logged anywhere. There is no meeting where someone decided to stop. It just stopped. This essay is about how that happens without anyone deciding it should.

The pattern

I have spent my career inside large, complex organizations. Regulated environments. Public sector bodies. Multi-country operations with thousands of employees and dozens of collective agreements and the particular institutional gravity that comes with having operated the same way for a long time.

In every one of these organizations, I have watched the same pattern play out.

It starts with a legitimate need. The organization needs consistency. It needs protection from liability. It needs to ensure that managers are treating people fairly and not making decisions arbitrarily. These are real needs. The documents and policies and procedures that get built to address them are built in good faith by people who understand what happens when organizations do not have them.

And then, slowly, the documents stop being tools and become walls.

The manager who wants to have a direct conversation with a struggling employee instead learns to lead with documentation. The HR business partner who wants to support a team through a difficult transition instead spends their time ensuring the process has been followed correctly. The grievance that could be resolved in a conversation instead becomes a file. The file requires a response. The response requires review. The review requires approval. And somewhere in that chain the actual human problem, the one that could have been addressed in fifteen minutes if two people had sat in a room and spoken honestly to each other, gets buried under paper.

I have been on both sides of this. I have been the HR leader who built the systems. I have also been the person who sat in rooms watching those systems do exactly the opposite of what they were built to do.

Regulatory capture

The technical term for what I am describing is regulatory capture, borrowed from economics, where it refers to the phenomenon of regulatory agencies that end up serving the interests of the industries they were created to regulate. The parallel is imprecise but useful. HR functions, built to serve employees and the organization simultaneously, have a tendency over time to tip toward serving the organization's risk management needs at the expense of everything else.

This is not a failure of individual people. The HR professionals inside these systems are, almost universally, trying to do the right thing. They believe in the policies they administer. They believe in consistency and fairness and legal defensibility. They are not wrong to believe in these things.

The failure is architectural.

When the system is designed primarily around risk management, it optimizes for risk management. Every case that goes through the system is processed through the lens of what the organization needs to be protected from. The employee's experience of that process is real, and it matters, but it is not what the system is designed to optimize for.

And over time, the people inside the system start to see every situation through that lens. Not because they are callous. Because the lens is built into the tools.

Three scenes

I have watched an employee submit a complaint about a manager and receive, six weeks later, a letter informing them that an investigation had been conducted and that appropriate measures had been taken. The letter did not say what the measures were. It did not ask how the employee was doing. It did not offer any follow-up.

The process had been followed correctly.

I have watched a long-tenured employee, someone who had been with an organization for eighteen years and had built more institutional knowledge than anyone could easily replace, receive a performance improvement plan for the first time in their career after a new manager arrived with different expectations. The plan was technically constructed. Every element was documented. The HR process was clean.

The person resigned four months later. No one was surprised.

I have watched a team that had been through a genuinely difficult period, a restructure, a leadership transition, a year of elevated workload that nobody had adequately compensated for, receive an engagement survey and a summary of the results. The summary identified that engagement was lower than it had been two years ago. A working group was formed to develop action items.

The working group met twice.

Processing is not listening

None of these things happened because bad people made bad decisions. They happened because the systems were not designed to listen. They were designed to process.

Processing and listening are not the same thing.

Processing takes an input, runs it through an established procedure, and produces a compliant output. Listening takes an input and asks what the person is actually experiencing, what it would take to address that experience, and whether the current system has the capacity to do that.

Most HR systems are very good at processing. Most HR systems are not designed to listen.

The irony is that listening is what HR was originally supposed to do. The function exists, in its foundational form, to be the part of the organization that sits between the institution and the people inside it and says here is what the people are experiencing, here is what they need, here is what the organization needs to do differently to retain and develop and not waste them.

Somewhere in the evolution from that original mandate to the forty-three-page progressive discipline policy, something got inverted.

If this essay named something you have been sitting with, subscribe. Beyond the Title sends one essay a week on the architecture of work.

What rebuilding requires

I have built HR functions from the ground up. I have also inherited HR functions that had been running the same way for a decade and were producing the results that any system produces when it optimizes for the wrong thing. Technically compliant processes. Low trust. High turnover among the people the organization most needed to keep. A widespread belief among employees that HR was not there to help them.

The belief was not wrong. The system was not designed to help them. It was designed to protect the organization.

The work of rebuilding those systems is not primarily a technology problem or a process design problem, although both are involved. It is a diagnosis problem. It requires someone to stand in the gap between what the system says it does and what the system actually does, and name the difference clearly, without making it personal, without assigning blame to the individuals who have been faithfully administering the thing they were given.

The first move is admitting, out loud, that the system has been optimizing for something other than listening. This is harder than it sounds. Every senior leader in the room has been approving the current architecture for years. Naming the gap implicates them, not as bad actors, but as people who inherited a design and never had the mandate to redesign it. That admission is the work.

The second move is redesigning the instruments of listening to measure what actually matters. Most engagement surveys are written to be answered evasively. They have to be rewritten to be answered honestly. The new instrument is shorter, sharper, harder to respond to without saying something real. It includes at least one question that the leadership team is genuinely afraid of the answer to. That fear is the signal that the system is beginning to listen again.

The third move is changing what happens to the findings. Instead of distilling raw responses into five recommended actions presented to the senior leadership team, the raw themes are published widely and the functional leaders closest to the themes are asked to own the response. The response includes the option of saying, in writing, that a theme has been heard and deprioritized, with a reason. That option paradoxically is what restores the credibility of the system. An organization that names what it is choosing not to address is listening more than an organization that quietly drops the finding from next year's report.

The fourth move is protecting the people who raise difficult things. This is the hardest. The instinct of every organization under pressure is to silence the messenger. The organizations that rebuild are the ones that learn, structurally, to route discomfort back into the system without punishing the person who introduced it. This does not happen through training. It happens through specific, visible cases in which a difficult message was raised, received, and acted on, in a way that protected the person who raised it. Those cases are the curriculum.

What I have learned

The system stopped listening. Not because the people stopped caring. Because the architecture optimized for something other than listening and the people adapted to the architecture.

This is fixable. It is hard, and it is slow, and it requires the organization to be willing to hear things it would rather not hear, which is, in itself, a form of listening that the system has often been specifically designed to avoid.

But it is fixable.

The forty-three-page document I started with still exists, as far as I know, in the organization where I encountered it. It is probably still being administered correctly. The managers still complete the required training in the learning management system.

What I do not know is whether the employees inside that organization feel, when they have a problem, that there is somewhere to take it.

That is the question the document cannot answer. That is the question that only a system designed to listen can answer.

The discipline framework tells you what to do when someone has already given up. The listening system is what happens before that.

The forty-three-page document did not write itself. Someone wrote it to solve a real problem. The problem is that nobody went back to check whether the solution had become one.

When was the last time your HR function asked an employee what they actually needed, and genuinely changed something based on the answer?

Roy Tran Beyond the Title

If something here landed, or something snagged, the comments are open. I read every one.

The person who comes to mind right now is who this was written for.

Send it to them.