Observation 05·November 11, 2026·4 min

When Does a Convenience Become a Dependency?

A useful tool can become part of how an organisation works. Years later, doing without it may be harder than anyone expected.

Topic: Platforms and suppliers

It usually starts with something quite ordinary.

Someone finds a better way of doing a job. Perhaps it's a piece of software that saves an hour every Friday, a shared spreadsheet that makes information easier to find, or an online service that removes a task nobody particularly enjoyed doing.

People start using it because it works.

A few months later, somebody else begins relying on it. Another team adopts it. A process changes because the information is now available in one place.

Eventually, nobody thinks much about the original decision.

It's simply how things are done.

There's nothing particularly wrong with this. Most improvements in working life happen in much the same way. Someone finds a practical solution, other people recognise its value, and gradually it becomes part of the routine.

The interesting part comes later.

The point nobody remembers

Imagine a small organisation that begins using an online service to manage its appointments.

Initially, it's just a convenient replacement for a diary and a few telephone calls. Staff can see bookings, customers receive reminders, and fewer appointments are missed.

Over time, the organisation changes around it.

Opening hours are planned using the booking information. Staff rotas depend on it. Customer records are maintained there. Perhaps payments and reporting are eventually connected as well.

Five years later, replacing that service would be a substantial undertaking.

Nobody necessarily made a bad decision. In fact, each decision along the way may have been entirely sensible.

But the organisation is no longer simply using an appointment system.

It has organised part of its business around one.

The change happened gradually enough that there may never have been a reason to stop and consider it.

Why familiarity matters

People become comfortable with systems they use every day.

They learn where things are, how to work around small problems and whom to ask when something goes wrong.

That knowledge is valuable. It helps work get done.

It can also make alternatives seem less attractive than they really are.

A replacement might offer better features, lower costs or greater flexibility. But it would require people to change routines they have spent years developing.

There may be information to transfer, other software to reconnect and staff to retrain.

Some of those difficulties are unavoidable. Others exist because the organisation has gradually adapted itself to the original system.

This is one reason technology decisions can become difficult to reverse without anyone having deliberately made them permanent.

The system doesn't have to be especially sophisticated or expensive.

Sometimes the hardest thing to replace is an ordinary spreadsheet that everybody has used for years.

The people who keep things working

There is another kind of dependency that receives less attention.

Often, a system continues working because one or two people understand its peculiarities.

They know why a particular report has to be run in a certain order, why an old setting mustn't be changed, or why information needs to be copied between two systems every Tuesday.

These details rarely appear in formal descriptions of how an organisation operates.

They are simply things people have learned through experience.

When those people leave, the system may still be available. The software hasn't failed. The subscription is still being paid.

But something important has gone missing.

The organisation has lost part of its understanding of how the work actually gets done.

That is a dependency too, although it is much harder to see on a list of software suppliers.

Convenience isn't the problem

It would be rather strange to argue that organisations should avoid useful technology because they might eventually depend on it.

We depend on things precisely because they are useful.

Electricity, communications, transport and countless ordinary services have become essential through the benefits they provide.

The same is true on a smaller scale inside workplaces.

A reliable system can free people from repetitive tasks and allow them to concentrate on work that matters more.

Dependence isn't necessarily evidence that something has gone wrong.

What changes is the consequence of losing access.

A tool that once saved a little time may eventually become something without which an entire department struggles to operate.

That change deserves to be understood, even when there is no immediate reason for concern.

Looking back

One difficulty with gradual change is that it can be almost impossible to identify the moment it became significant.

The original decision may have been made by someone who no longer works there. The reasons for choosing a particular system might have been forgotten. What began as a temporary arrangement may have outlasted several reorganisations.

By then, people aren't necessarily choosing to remain with the system.

They're continuing to use what the organisation has grown accustomed to.

Sometimes that's still the best option.

Sometimes it isn't.

The trouble is that the distinction becomes harder to recognise when nobody remembers what the alternatives were.

And perhaps that's the most interesting thing about convenience.

We notice it when something first becomes easier.

We don't always notice when doing without it becomes difficult.