What Once Protected Your Business Can Hold It Back Later

A costly mistake on an important launch had created exactly the kind of reaction you’d expect. The company tightened one decision point and required senior approval before similar changes could move forward. The added control worked. The same mistake didn’t happen again.

Later, the business had changed. The team was more experienced, decision authority had moved closer to the work, and the original risk was being managed in other ways. Someone finally asked whether the senior approval was still necessary.

The answer was simple: The control was working, so there was no reason to change it.

That’s where a useful response becomes an execution problem. Leaders assume that if a process stopped a serious failure, keeping it in place is the safest choice. The more successful the response has been, the harder it becomes to prove that the business no longer needs it.

Success becomes evidence for keeping the wrong thing

When leaders respond to a failure, they aren’t creating friction for the sake of it. They’re protecting the business from something that has already happened and could happen again.

A missed launch, costly pricing error or customer problem justifies tighter approval, more senior review or another control. When the new response stops the problem, leadership gets something it didn’t have before: a visible result.

The danger appears later. The organization grows, capability improves, and the conditions around the original problem change — but the old response still has a strong piece of evidence behind it. The problem stopped after the response was introduced.

That creates a powerful but incomplete conclusion. If the failure hasn’t returned, the response must still be necessary.

I’ve seen this pattern in large organizations where a control introduced after a serious miss becomes part of normal operating practice. Years later, people question whether it still belongs there, but the historical record points in only one direction. Before the control, something went wrong. After the control, it didn’t.

What nobody can see as clearly is the counterfactual. Would the problem return if the response changed now, after the business itself has changed?

The question gets asked and still produces the wrong answer

This is what separates the problem from ordinary process debt.

The response doesn’t have to survive because nobody noticed it, nobody owned it or nobody was willing to challenge it. Leaders can review it directly and still decide to keep it.

They have strong evidence that the response worked and much weaker evidence that it is no longer required. That difference matters.

The approval from the launch example is now sitting several levels above the people doing the work. The regional team has stronger experience, clearer decision rights and better information than it had when the original mistake occurred. Yet the decision still travels upward because the senior approval remains part of the process.

Someone asks whether the approval can move lower.

Leadership looks at the record. There hasn’t been another major failure since the approval was introduced. Removing it now feels like abandoning the very thing that prevented the problem.

So the process stays.

Nobody ignored the issue. Nobody failed to review it. The organization looked at the evidence and treated proof that the response worked as proof that the response was still necessary.

Past protection becomes present drag

The cost rarely arrives as one dramatic failure.

It appears in the ordinary movement of work. Decisions wait for someone whose judgment is no longer needed on every case. Teams bundle issues together because they know a senior review is coming. Executives spend time approving choices that the organization has already developed the capability to make elsewhere.

Important decisions can then wait behind routine approvals because both are competing for the same executive attention.

The delay then starts shaping how people work. Teams learn how long the approval takes and build that waiting time into their plans. Leaders see the work still moving and assume the process remains manageable, even though people are compensating for a constraint that no longer adds the same value.

That adaptation hides the cost. The organization doesn’t experience one obvious breakdown that forces the issue back onto the table. It experiences a little more waiting, a little more senior attention and a little less room for people closer to the work to act at the speed their roles now require.

At first, that looks like a capacity problem. The senior leader has too much on their plate. The team needs faster turnaround. Another meeting or a clearer escalation path starts looking like the answer.

But those fixes miss the original source of the delay. The business is still organizing work around a response designed for an earlier version of itself.

That pattern becomes harder to see as an organization grows. More capable people join, responsibilities move, and better information becomes available, yet an old control can remain untouched because its track record still looks stronger than the case for changing it.

A control that once protected a fragile launch process remains even after the capability, information and decision rights around that process have materially improved.

The old response keeps winning the argument because leaders are comparing today’s decision with yesterday’s failure instead of testing today’s response against today’s operating conditions.

A successful response still has to earn its place

Leaders are taught to learn from failure. The harder discipline is learning from success without turning it into permanence.

A response can be exactly right when it’s introduced and wrong later without anyone having made a bad decision. The organization around it has changed.

A successful control therefore needs two different tests. The first is whether it worked. The second is what still makes it necessary now.

The first looks backward and confirms that leadership solved a real problem. The second looks at the current business and asks whether the same response still fits the work, capability and risk that exist today.

When organizations confuse those two questions, yesterday’s protection becomes today’s delay.

The process may still be producing the result it was designed to produce. What has changed is whether the business still needs to pay the same price for it.

A response shouldn’t become permanent just because it succeeded. Success is the reason it needs to be questioned again.

A costly mistake on an important launch had created exactly the kind of reaction you’d expect. The company tightened one decision point and required senior approval before similar changes could move forward. The added control worked. The same mistake didn’t happen again.

Later, the business had changed. The team was more experienced, decision authority had moved closer to the work, and the original risk was being managed in other ways. Someone finally asked whether the senior approval was still necessary.

The answer was simple: The control was working, so there was no reason to change it.