The Policy Lag

You are not failing because you are bad at your job. You are failing because you are running today's operations on infrastructure built for a different organization. The process was good once. That organization no longer exists.

Most organizational dysfunction gets blamed on people or culture. The Policy Lag is different: the processes, org chart, and reporting structure were designed for an organization that no longer exists, built for forty people and three product lines, still in place at two hundred people and nine, and nobody has touched them since, even though everyone quietly knows the structure is mostly decorative.

The processes still work, in the sense that they technically exist and produce outputs. What those outputs have to do with what the organization actually needs to accomplish is a separate question, and the connection has stretched thin enough that nobody's really tracking it anymore.

How Systems Become Fossils

No one designs a system to fail. The systems running this organization were good once. Appropriate to the scale, fitted to the work, reflective of what the organization needed at the moment they were built.

Then time happened.

The organization grew. The market shifted. The strategy evolved. New priorities emerged. And the systems... didn't. They stayed where they were, doing what they were designed to do, while the thing they were designed to serve became something else entirely.

At first, people adapted. They built workarounds. They learned which parts of the process to take seriously and which parts to quietly ignore. They figured out the shortcuts, the right person to call, the way to get things done despite the official channels rather than through them.

Those workarounds became the actual operating system. The formal processes became ceremony: things you do because they're documented, not because they accomplish anything. Performance reviews that no one uses to make performance decisions. Approval chains that everyone routes around. Reports that get generated, filed, and never read.

At some point, someone tried to change one of these systems. It went badly. There was resistance, or confusion, or the new thing didn't work any better than the old thing, and everyone concluded, not entirely incorrectly, that changing systems is more trouble than it's worth. Better to leave the lag in place and work around it.

That conclusion hardened into culture. Now you have an organization that believes its systems can't be changed, which means they won't be changed, which means they become progressively more disconnected from the actual work.

The Tax

The Policy Lag extracts a tax on everything the organization does. It's not a dramatic tax: no single interaction feels catastrophic. It's cumulative. Attritional. The kind of cost you stop noticing because it's everywhere.

It's the extra thirty minutes on every decision because the decision rights are defined by a structure that doesn't match the work. It's the meeting to coordinate the teams that shouldn't need to coordinate but do because the org chart says they report to different people with different priorities. It's the three approvals for something that should need one, and the zero approvals for something that should need three.

It's the reporting. God, the reporting. Reports that exist because someone asked for them five years ago and never said to stop. Dashboards that measure vanity metrics because the real metrics would require infrastructure changes. Quarterly reviews of data nobody uses to make any decision at all.

And it's in talent. The people who could modernize the systems, who have the energy and the expertise and the willingness to do the work, tend to be exactly the people who won't tolerate working in systems that are obviously obsolete. They'll try once. Maybe twice. And when they realize the organization would rather preserve the lag than let it evolve, they'll leave. Quietly. For somewhere that takes operational effectiveness seriously.

What remains is a workforce selected for tolerance of dysfunction. That's not an insult: it's an observation. The system filters for people who can make peace with it. But "making peace with it" is not the same as "thriving," and the performance gap between organizations that evolve their systems and organizations that don't is wider than most people realize.

The Tells

Policy Lag organizations have a distinct feel. Once you recognize it, you see it everywhere.

The workarounds are institutional knowledge. The real way to get things done isn't documented. It lives in the heads of people who've been there long enough to learn it. Losing one of those people doesn't just mean losing a contributor: it means losing the map of how the organization actually functions versus how it's supposed to function.

Process changes are announced but don't stick. Someone launches a new system. People use it for three weeks. Then they quietly revert to the old way because the new way doesn't fit the surrounding infrastructure. Nobody talks about the failure. The new system becomes a ghost, technically in place, actually unused.

The leadership team talks about modernization but doesn't do it. There's a strategic priority about "operational excellence" or "process optimization" that's been on the list for four years. Occasionally someone kicks off an initiative. The initiative produces a diagnosis, sometimes recommendations, rarely implementation, and never sustained change.

People have stopped expecting the systems to improve. This is the final stage. When the workforce has concluded that suggesting changes is a waste of energy, the organization has fully adapted to its own dysfunction. The Policy Lag isn't experienced as a problem to be solved. It's experienced as weather.

Why It Persists

Policy Lag conditions persist because changing them requires something most organizations won't provide: honest acknowledgment that the systems are wrong.

Not outdated. Not "due for an update." Wrong. Built for something this organization no longer is. Continuing to exist because changing them would require admitting they should have been changed years ago.

That admission is uncomfortable. It implicates people. The leader who designed the process. The team that's been running it. The executives who approved it and never revisited it. Saying "this system doesn't work" raises the question of why it's still here, which raises the question of who let it get this bad, which raises questions nobody wants to answer.

So instead, the organization pretends. The system is "being reviewed." There's a "roadmap" for modernization. The current state is "temporary": it's been temporary for three years. The fiction lets everyone avoid the confrontation, and the system persists.

The other reason Policy Lag conditions survive is that they're stable. Bad, but stable. Everyone knows the workarounds. Everyone's adapted. Ripping out a system, even a broken one, creates uncertainty, creates transition costs, creates the possibility that the new thing might be worse than the old thing. "The devil you know" is a powerful argument when the devil you know has become familiar enough to feel like normal.

What Actually Changes It

Policy Lag conditions change when someone with authority decides the cost of preserving them is higher than the cost of replacing them.

That decision is usually triggered by one of three things: a competitive threat that makes the dysfunction undeniable, a new leader who wasn't there when the systems were built and doesn't feel the obligation to defend them, or a strategic shift that makes the gap between current systems and current needs impossible to ignore.

The work, once the decision is made, is actually not that complicated. Audit the systems honestly. Identify what's load-bearing and what's decoration. Design replacements that fit what the organization actually is, not what it was. Implement with enough structure that the new systems stick and enough humility to adjust when they don't.

What makes it hard is the honesty. Someone has to say out loud that the operating model is running on infrastructure designed for a different organization. That the workarounds have become the system. That the people who've been adapting to the dysfunction deserve better than being asked to adapt forever.

If that's where you are, running operations on systems you know are obsolete, watching good people leave because they can't tolerate the gap between what's possible and what's permitted, the honest starting point is saying out loud that the systems were built for an organization that no longer exists.