This article expands on comment we gave to South East Business Insider for its October feature on digital restructuring. You can read how the invitation came about, or carry on for the full answer.

What digital restructuring actually means

For me, digital restructuring is much broader than simply replacing old software.

It is about looking at how a business actually operates: how information moves between people and departments, where decisions are made, and then restructuring those processes using technology to make the business leaner, more efficient and ultimately easier to scale.

That distinction matters, because it changes where you start. If you treat it as a software replacement exercise, you begin with a shortlist of products. If you treat it as an operating question, you begin with how the work currently flows — which is why we usually start with designing the operating model first and only then decide what technology supports it.

The clearest warning sign: people as glue

One of the clearest warning signs is when a business has people acting as the glue between different systems.

If somebody is routinely taking information from an email, putting it into a spreadsheet, then entering it into another system and notifying somebody else manually, there is almost certainly an opportunity to improve that process.

That person is doing a job the systems should be doing. They are also a single point of failure, and the work is invisible — it rarely appears in any process document, so nobody has costed it.

Other signs are more familiar:

  • Duplicated data and multiple versions of the same information
  • Excessive spreadsheets sitting alongside the real systems
  • Systems that do not communicate with each other
  • Poor visibility for management, where producing a number means asking three people
  • Processes that depend too heavily on an individual’s knowledge

None of these is a technology fault on its own. Together they describe a business that has grown faster than the systems supporting it.

How to decide what to modernise first

We normally start with the process rather than the technology.

I want to understand where the business is losing the most time, where mistakes occur, what causes frustration internally and, importantly, what is affecting the customer or preventing the business from growing.

There is sometimes a temptation to start with the system that looks most dated. That is not necessarily where the greatest return will be achieved. The ugly system in the corner may be doing its job perfectly well while the real cost sits somewhere nobody is looking.

You can usually identify some fairly obvious bottlenecks quite quickly:

  • Sales opportunities not being followed up consistently
  • Operations manually rekeying information between systems
  • Finance chasing information from other departments
  • Management spending hours producing reports that should be instant

Once you understand those problems, you can prioritise according to business impact rather than replacing technology for the sake of it.

Replace, integrate, or fix the process?

I don’t think legacy automatically means bad.

There are plenty of older systems that perform a particular function extremely well. If the core system is reliable and contains valuable business logic, integration may be considerably less disruptive and more cost-effective than replacing it. Often the right answer is to leave it alone and connect it to the systems around it.

The real question is whether the system is creating a genuine constraint. Replacement starts to make sense when:

  • It cannot integrate with other technology
  • The cost of maintaining it is increasing
  • The knowledge required to support it sits with one or two people
  • Employees are building increasingly complicated workarounds

That last one is the most telling. Workarounds are a measurement. When people invent their own process to get around the system, they are showing you precisely where it fails.

The trap worth avoiding

Businesses need to be careful not to blame technology for a poor process.

Digitising an inefficient process normally just gives you an inefficient digital process. It runs faster and it is harder to see, which is arguably worse. Sometimes the process itself needs redesigning before any decision about software is made.

This is also where the choice of platform gets less important than people assume. We work across every major CRM — our independent view on CRM selection is that the right answer depends on how you sell, not which name you recognise. And where no product genuinely fits the process, a purpose-built application is often cheaper than bending the business around software that nearly works.

What this looks like in practice

A restructuring programme done properly tends to produce a short, unglamorous list:

  1. Two or three processes redesigned, not digitised as-is
  2. One or two systems connected so data stops being rekeyed
  3. One legacy system deliberately left in place
  4. A clear statement of what each change was supposed to improve

That last point is the one most often skipped, and it is the one that determines whether anybody can tell afterwards if the investment worked.

What Digital Scientists® does

We map how a business actually runs before recommending anything, then restructure the processes that are costing the most — in time, errors, or lost opportunities. Sometimes that means new systems. Often it means connecting what you already have and removing the manual steps between.

If you recognise the warning signs above, book a free discovery call and we will give you an honest view of where the friction actually is. You can also read how we structure engagements before committing to anything.