Beyond Transformation: Choosing the Right Level of Change

The problem with the word

Few terms have been overused as much as transformation.

Everything becomes a transformation: a reorganisation, a tooling change, a process adjustment, a cost reduction plan. The word carries weight, signals ambition, and attracts attention. It gives the impression that something meaningful is about to happen.

But it also creates confusion.

Because not every problem requires a transformation. In fact, most do not. When everything is framed as one, organisations lose the ability to choose the right level of change, and more importantly, the ability to respond proportionally.

When the diagnosis is wrong

Most large-scale initiatives fail before they start for a simple reason: the diagnosis is off.

A local inefficiency is treated as a structural issue. A coordination problem is treated as a cultural gap. A bottleneck is treated as a need for reorganisation. What could have been addressed precisely becomes inflated into something systemic.

The response escalates too quickly.

Instead of adjusting the system, organisations attempt to redesign it. And when the diagnosis is wrong, scale amplifies the mistake.

Complexity grows faster than value. Existing dynamics are disrupted. New problems appear while the original one remains, often harder to isolate than before.

The cost of over-scaling change

Transformation is expensive.

Not only in budget or time, but in attention, trust, and stability. It creates uncertainty, shifts priorities, and redistributes ownership across the organisation. Even when well-intentioned, it introduces a level of disruption that must be justified.

When used appropriately, this cost can be absorbed and even beneficial. When misapplied, it becomes destructive.

Teams lose continuity. Initiatives compete. Leadership attention fragments. Side effects appear: churn increases, friction rises, and recovery becomes harder than the original problem.

And the original issue often remains, now buried under additional layers of change.

History offers clear examples of this pattern.

General Electric attempted to accelerate its digital transformation beyond its structural readiness, creating complexity faster than value.

HP went through repeated large-scale reorganisations, fragmenting focus and diluting ownership instead of addressing underlying issues.

In both cases, the intent was sound. And the scale amplified the mistake.

Levels of change

Not all change is equal.

There are three practical levels, each with its own purpose and cost.

• Adjustment: local fixes that remove friction, clarify ownership, and restore flow where it is blocked
• Evolution: structural improvements that refine interfaces, strengthen feedback loops, and improve coordination over time
• Transformation: a redefinition of the system itself, often introducing new constraints, new models, and new ways of operating

The mistake is not choosing transformation. The mistake is choosing it by default, without exhausting the lower, more precise levels first.

What experienced leaders do differently

Senior leaders spend more time diagnosing than acting.

They understand that the quality of the intervention depends on the clarity of the problem.

They ask:

• Where is the constraint?
• Is the issue local or systemic?
• What is the smallest change that would improve flow?

They resist the urge to escalate prematurely, even under pressure. Because they know that the scale of change must match the scale of the problem. Anything beyond that introduces noise rather than progress.

A practical example

Consider a delivery organisation struggling with delays.

A common reaction is to reorganise teams, redefine roles, or introduce a new operating model. These actions create visibility and give the impression that something decisive is happening.

Yet in many cases, the issue sits elsewhere.

Priorities are unclear. Work in progress is overloaded. Decision cycles are slow or fragmented. None of these require a transformation.

They require discipline and targeted adjustments. Remove friction. Limit work in progress. Clarify ownership. Open decision paths. When these are ignored, transformation becomes a substitute for diagnosis rather than a response to it.

The spectrum of effective action

Before changing the system, strengthen it.

A wide spectrum of actions often resolves the issue without escalation:

• removing bottlenecks and unnecessary approvals
• reopening closed or ineffective communication channels
• clarifying intent and decision boundaries
• onboarding or repositioning key talent where it matters most
• stabilising interfaces and reducing competing priorities

These moves are less visible than transformation. They do not create headlines or narratives.

They create results.

Flow and predictability

Predictability does not come from more control. It emerges from stable flow.

When work moves without unnecessary interruption, when decisions happen close to the context, and when feedback loops are short, outcomes become more reliable over time.

Over-scaled change disrupts that flow. Each additional layer introduces waiting time, resets momentum, and increases variability.

What was meant to create certainty ends up reducing it.

Why the word persists

Transformation is attractive because it promises a reset.

It creates momentum. It signals leadership intent. It offers a narrative of change that is easy to communicate and easy to support.

But narratives do not fix systems. Precision does.

Choosing the right move

The real challenge is not deciding whether to transform.

It is deciding how much change is actually required, and where it should be applied. Too little, and problems persist. Too much, and the system destabilises.

Finding the right level requires clarity, restraint, and experience. It requires resisting both inertia and overreaction.

In Summary

Not every problem deserves a transformation.

Some require adjustment. Others require evolution. Very few require reinvention.

Knowing the difference is what separates leadership from theatre.