How Legacy Systems Create Heavy Dependence on a Few Key People in Travel Companies

Introduction: The hidden concentration of knowledge

In many UK travel companies a small number of people hold critical understanding of how legacy systems actually work. These individuals know the workarounds, the undocumented rules and the steps required when something goes wrong. The rest of the organisation depends on them.

This concentration of knowledge is rarely planned. It develops over years as systems grow more complex and documentation lags behind. When one of these key people is on leave, changes role or leaves the company, the operational impact can be immediate and severe. This article looks at why the problem is so common and what practical steps reduce the risk.

Why legacy systems concentrate knowledge in a few people

Legacy booking, inventory and integration platforms often contain years of custom changes, special rules and temporary fixes that were never fully documented. The people who made or managed those changes become the only ones who understand how the system behaves in real conditions.

Newer staff can learn the standard processes, yet the edge cases and recovery steps remain with the original experts. Training new team members takes longer because so much of the knowledge is informal. Over time the organisation becomes structurally dependent on a small group of individuals.

Here is a view of the most common sources of this dependence.

The operational risk when key people leave or are unavailable

When a key person is absent, even routine tasks can stall. A pricing change, a supplier connection issue or an end of day reconciliation may wait until that individual returns. During peak periods the pressure intensifies.

If the person leaves permanently, the company faces a knowledge gap that can take months to close. Recruitment is harder because the required expertise is rare and specific to the organisation’s particular system configuration. The risk is both operational and financial.

How this dependence affects day to day decisions

Managers become reluctant to make system changes because only a few people can assess the impact. Innovation slows. Projects that would improve efficiency are postponed because the key experts are already overloaded with keep the lights on work.

Teams also develop informal hierarchies around access to knowledge. Decisions that should be straightforward require consultation with the same small group. Over time the organisation becomes less agile and more vulnerable to individual absence.

Here is a practical view of the business impact.

What reduces this operational risk

Reducing dependence starts with making knowledge explicit. Documenting the most critical processes, rules and recovery steps moves understanding from individual memory into shared resources. Improving system transparency so that behaviour is more predictable also helps.

Selective modernisation of the highest risk components can further reduce reliance on specialised knowledge. When systems are clearer and better documented, more people can support them safely. The goal is not to eliminate expertise but to ensure the organisation is not vulnerable to the absence of any single person.

Practical steps to reduce dependence on key individuals

Begin by identifying the processes and system areas that currently rely on one or two people. Prioritise those that would cause the greatest disruption if the knowledge were lost. Create clear, practical documentation for the most critical workflows and recovery steps.

Pair key experts with other team members so knowledge is transferred through real work rather than formal training alone. Review the most opaque parts of the system and consider targeted improvements that make behaviour more transparent. Measure progress by tracking how many critical tasks can be completed without the original expert.

Here is a practical checklist used by several UK travel companies.

Frequently Asked Questions

Why do legacy systems create such strong dependence on individuals?

Years of custom changes and undocumented rules mean that only the people who lived through those changes fully understand how the system behaves.

Is documentation enough to solve the problem?

Documentation is essential but not sufficient on its own. Pairing experts with other staff and improving system clarity are also required for lasting reduction in risk.

How long does it take to reduce key person dependence?

Focused work on the highest risk processes can show progress within a few months. Wider reduction across the organisation usually takes longer and benefits from staged effort.

Do we need to replace legacy systems completely?

Not always. Many operators reduce risk through better documentation, knowledge transfer and selective modernisation of the most opaque components.

What is the biggest risk if we do nothing?

Operational disruption when key people are unavailable or leave, plus slower innovation because change depends on the same overloaded individuals.

How do we know when dependence has been reduced?

When critical tasks can be completed reliably by more than one or two people, and when absence of any single individual no longer causes immediate operational delay.

Conclusion: Build resilience by spreading knowledge

Legacy systems create heavy dependence on a few key people in many UK travel companies. The knowledge that keeps operations running sits with individuals rather than in shared processes or transparent tools. When those people leave or are unavailable, the organisation feels the impact quickly.

Reducing this risk starts with identifying the most critical knowledge areas and making that knowledge explicit. Documentation, structured knowledge transfer and selective improvements in system clarity all help. Over time the company becomes less vulnerable to individual absence and more able to evolve its technology with confidence.

Sources

• Phocuswright UK Travel Market Essentials 2025 — phocuswright.com
• Travelport Digital Travel Insights and Trends Report 2025 to 2026 — travelport.com