Business Transformation vs Business Improvement: Which Do You Actually Need?

The two terms get used interchangeably, including by people who should know better. They describe genuinely different pieces of work, with different costs, different timescales and different risks.

Picking the wrong one is expensive.

Improvement makes an existing way of working better. Transformation changes how an organisation operates and delivers its objectives.

Business improvement: making the current model work better

Improvement work takes the business as it is and looks for ways to make it perform better.

The organisation keeps its existing operating model. The focus shifts to making the work more efficient, consistent and effective.

That means removing waste from processes, reducing errors and rework, shortening lead times, improving quality and getting better information into the hands of the people making decisions.

The characteristics are worth noting:

• Lower risk, because you’re improving an existing way of working
• Faster payback, often within a quarter
• More contained disruption, affecting specific processes or areas
• Measurable in familiar terms, time, cost, quality and performance

Most businesses that think they need transformation may actually have an improvement problem. The underlying model can work, but the way it operates day to day is holding it back.

Business transformation: changing how the organisation operates

Transformation is a different level of change. It involves a fundamental shift in how an organisation operates and delivers its objectives.

That could mean redesigning the operating model, restructuring how teams work together, introducing new systems and technology, changing how services are delivered, or fundamentally redesigning processes across the organisation.

Importantly, transformation does not necessarily mean changing what the organisation sells, who it serves or which markets it operates in. An organisation can transform how it works while continuing to deliver the same products or services to the same customers.

The characteristics are different:

• Greater complexity, because multiple parts of the organisation may need to change
• Longer timescales, particularly where new systems, capabilities or ways of working form part of the change
• Wider organisational impact, rather than change being contained to one process
• A need to manage both the change itself and how it becomes embedded across the organisation

Many things can drive transformation: the need to improve performance at scale, new technology, changing customer expectations, regulatory requirements, operational challenges or recognition that the current way of working is no longer fit for purpose.

The important question is not whether the organisation needs to change what it does. It is whether the way it currently operates is capable of delivering what it needs to achieve.

The two side by side

The failure modes are worth dwelling on, because they are what each type of work actually risks.

Improvement fails quietly. The business redesigns the process, it works for a quarter, then the old approach returns.

Nobody records it as a failure because nothing dramatic happened, the business simply carries on as it did before, slightly poorer.

Transformation can fail loudly and expensively. The programme runs long, the benefits case shrinks, and at some point somebody decides the original scope was unrealistic. Or the new way of working is introduced but never properly embedded, leaving the organisation with more complexity without the expected improvement in performance.

How to tell which one you need

Three questions usually help clarify the scale of change required.

One: can the existing way of working deliver what you need?

When the underlying approach is sound but performance could be better, improvement may be enough. A need to change how the organisation currently operates points towards transformation.

Two: how much of the organisation needs to change?

Improvement work often focuses on specific processes, teams or areas of performance. Transformation usually involves multiple parts of the organisation and changes to how they work together.

Three: are you improving the existing model or redesigning how it works?

Look at the outcome you want. Making existing processes more efficient, consistent or effective points towards improvement. A fundamental rethink of how the organisation structures, delivers or supports work points towards transformation.

The order matters more than the label

Here’s the part that gets missed.

Transforming an organisation without understanding how it operates today is building on sand.

We see this fairly regularly. An organisation decides it needs to transform, invests heavily in a new system, operating model or way of working, and finds the same operational problems reproduced in the new environment.

The problems were never necessarily in the technology or the future-state design. They were in the disciplines underneath it — measurement, ownership, handovers, follow-through and the way work actually happens day to day.

Improvement work can help establish those disciplines. Transformation then has something solid to build on.

That doesn’t mean improvement always precedes transformation. Sometimes the organisation needs to make fundamental changes while also addressing operational issues. But it does mean the current way of working needs to be properly understood before major changes are made, and it is considerably easier to address weak foundations before a transformation programme is underway than during one.

What it costs to choose wrongly

Both errors are expensive, in different ways.

Calling it improvement when it is transformation means spending time optimising an approach that needs fundamental change. The work may be competent and the results may be real, but the organisation is still being held back because the underlying way of operating is no longer capable of delivering what it needs to achieve.

This is the more dangerous mistake because improvement work can produce visible wins that mask the bigger issue.

Calling it transformation when it is improvement means committing to a large, disruptive programme to solve a problem that a focused piece of process work could have fixed for a fraction of the cost.

The organisation gets there, eventually, having spent considerably more than it needed to and having exhausted its appetite for change in the process.

That second point matters more than it sounds. Organisational patience for change is finite. Spending it on an unnecessarily large programme leaves less capacity for the changes that genuinely matter later.

Where most organisations actually sit

In our experience, the honest answer for many mid-sized UK organisations is: improvement, with one or two areas that may require more transformational change.

The underlying organisation can be sound. Performance may be inconsistent. Processes may not work as well as they should. And there may be one system, capability or way of working that genuinely needs redesigning rather than simply refining.

Treating the whole organisation as a transformation programme can overspend and over-disrupt. Treating everything as improvement can leave genuinely fundamental issues untouched.

Good diagnostic work at the start helps separate the two, so it’s worth doing properly before committing to either.

Two things that are true of both

Whichever you’re doing, two disciplines apply and are routinely skipped.

You need a baseline.

Improvement without a before-measurement is an assertion. Transformation without one is an expensive assertion. In either case, taking a measurement before anything changes gives you a clear baseline for judging whether it worked, and it is almost impossible to reconstruct after the fact.

You need someone who owns it afterwards.

Both kinds of work create something new that the organisation needs to maintain alongside its day-to-day work. Improvement drifts back when nobody is watching. Transformation stalls when the sponsor moves on. Much of the value comes from successfully moving the work from the project into business-as-usual.

A practical first step

Before you engage anybody, write down the three problems costing you the most money, time or performance.

Then, against each one, ask whether the answer is to improve something you already do, or fundamentally change how the organisation operates to achieve its objectives.

If most are in the first category, you may need improvement. If most require fundamental changes to how the organisation operates, you’re looking at transformation. If they’re split, you need someone to help you understand and sequence the work – which is where a business transformation consultancy can add real value.

See how we approach [business improvement] , or [get in touch] for a conversation about where your organisation sits.