GuardTools Perspectives: The Problem with Problems

Topic: Why Organizations Don’t Change When Problems Appear

Problems rarely trigger change immediately. First, they trigger adaptation. And successful adaptation is often what delays change the longest.

Imagine a security organization that has been operating successfully for years. Let’s call the security manager Anna.

From the outside, everything appears to be working. Customers are satisfied, incidents are handled professionally, patrols are completed, and management receives the reports it needs. The operation may not be perfect, but then again, whose operation is?

If you asked Anna whether there were challenges, she would probably have no trouble naming a few. Reporting takes longer than it should. Some information gets lost between different stages of the operation. Certain sites work slightly differently from others. New employees take time to learn how things are done. None of these observations would be surprising to her. What is more interesting is that none of them feel urgent.

Because when organizations encounter problems, they rarely respond by changing the way they work. Instead, they adapt. A spreadsheet is created to bridge a gap. An extra meeting is added to improve coordination. An experienced colleague steps in whenever a process becomes unclear. The workaround works, and because it works, the organization moves on.

Each adaptation solves a problem. At least for the moment. Over time, however, the collection of adaptations can become a problem of its own.

The Problem Is Rarely Invisible

When people discuss digitalization or operational improvement, there is often an assumption that organizations struggle because they lack visibility. Our experience is usually the opposite.

Most organizations already know where the friction exists. They know which reports require manual effort. They know where information tends to get stuck. They know which routines differ between teams and departments. They know which tasks depend on specific individuals.

The challenge is not a lack of awareness. The challenge is that these shortcomings have become familiar.

After a few years, people stop seeing them as problems and start seeing them as part of the way the organization works. The workaround becomes the process. The exception becomes the norm. And because the operation continues to deliver results, there is little incentive to question it.

How Adaptation Creates Dependency

As organizations continue to adapt, another pattern often emerges: control gradually shifts from processes to people.

Everyone knows who understands the reporting structure. Everyone knows who can navigate the system when something behaves unexpectedly. Everyone knows who remembers why a particular routine was introduced years ago.

In Anna’s organization, perhaps there is a Maria who knows every customer site by heart. Perhaps there is a Johan who somehow always knows where to find the information others cannot locate. Perhaps there is a Peter who remembers every operational decision made over the last five years.

These people are enormously valuable. In fact, they are often one of the reasons the organization performs as well as it does.

The difficulty is that successful organizations can become so skilled at compensating through experience that they fail to notice the weaknesses underneath. What appears to be a strong process is sometimes a talented employee quietly holding the process together.

As long as those employees stay, everything continues to work.

That is why the risk remains largely invisible.

Where Value Begins to Leak

This matters because security work creates value through more than execution alone.

A patrol only creates its full value when observations are captured, shared and acted upon. An incident report becomes valuable when it contributes to learning. A risk assessment becomes valuable when it influences future decisions.

In other words, value is created through a chain.

Planning → Execution → Follow-up → Analysis → Decision → Improvement

Most organizations spend considerable energy improving the individual parts of that chain. The greater challenge is often what happens between them.

Information is recorded but not analyzed. Insights remain within operational teams instead of reaching management. Decisions are made but never fully translated back into daily practice. Nothing dramatic happens. There is rarely a major failure.

Instead, value leaks away slowly through dozens of small handovers and minor inefficiencies that nobody regards as serious enough to fix. At first the cost is barely noticeable. Over time it becomes significant.

The Irony of Successful Organizations

This is where things become interesting.

By now, Anna’s organization has accumulated a collection of workarounds, manual routines and dependencies that would probably surprise an outsider. Yet the organization still performs.

Customers remain satisfied. Targets are met. Audits may even look reasonably good. From a distance, success appears to be evidence that no major change is required.

In reality, the opposite may be true. The organization’s ability to adapt has become the very thing delaying improvement. Every time a weakness appears, capable people compensate for it. Every time information fails to flow naturally, someone creates a workaround. Every time a process falls short, experience closes the gap.

The system survives because people are good. And because people are good, the system never has to change.

Then Someone Looks at It Differently

The turning point rarely arrives because the underlying problem suddenly becomes worse.

More often, something changes around the organization.

• A new manager joins.
• An acquisition must be integrated.
• A customer asks for greater transparency.
• An audit raises questions.
• An aging platform approaches the end of its lifecycle.

What is striking about these events is that they rarely create the problem. They simply expose it.

The new manager does not share the historical context. The newly acquired business does not know the unwritten rules. The auditor does not understand why a spreadsheet has become critical infrastructure. The customer does not care that information has always been gathered in three separate systems.

For the first time, somebody sees the operation without the assumptions that have accumulated around it over the years.

And suddenly questions start to emerge.

• Why does this require so much manual effort?
• Why does so much knowledge sit with a handful of people?
• Why are there so many points where information can be lost?
• Why are we working this hard to compensate for things that should work by design?

That is often the moment transformation begins.

Not when the problem first appeared, but when the accumulated cost of adaptation becomes impossible to ignore.

A Thought to Take Into Consideration

Not: Do we need a new system?

But rather: What parts of our operation are functioning today only because experienced people compensate for weaknesses in processes, information flows or system support?

The answer to that question is often where tomorrow’s transformation projects start.

• Long before requirements documents are written.
• Long before procurement begins.
• Long before anyone books a demo.

Because change is rarely triggered by the problem itself.

More often, it begins with a simple realization:

“We’ve become very good at living with this.”

And shortly thereafter comes a second one:

“Maybe we don’t have to.”

Based on conversations and observations from the GuardTools team.