When Transformation Is Not the Answer

Why Adaptability Begins Before Change

Over the previous articles in this series, I have explored a recurring idea.

The new ways of working in projects are not simply about adopting new methodologies, introducing new technologies, or making teams more agile.

They increasingly depend on the ability of organizations to adapt their structures, decision mechanisms, operating models, governance, and allocation of resources as the conditions around them change.

But this raises an even more fundamental question.

What if transformation itself is not the right response?

A thoughtful comment from Aaron Porter on my previous article brought this question into sharp focus.

He asked two deceptively simple questions:

Is the organization solving the right problem?

Is transformation the appropriate response?

Those questions matter because much of the conversation about organizational transformation begins after a critical assumption has already been made:

That transformation is necessary.

From there, attention naturally turns to readiness, leadership, culture, capabilities, governance, technology, execution, and resistance to change.

But an organization can be highly prepared to transform and still be preparing to execute the wrong intervention.

That distinction changes where the conversation should begin.

Before Readiness Comes Diagnosis

When an organization underperforms, encounters disruption, or recognizes that existing ways of working are no longer producing the expected results, there is a natural pressure to act.

Sometimes that pressure is justified.

But recognizing that something is wrong is not the same as understanding what is wrong.

A process may be poorly executed.

A capability may remain appropriate but be insufficiently developed.

An operating mechanism may work as designed but have become misaligned with a changed environment.

A structure may have accumulated unnecessary complexity.

A technology or capability may have become obsolete.

Or assumptions that once justified existing arrangements may no longer hold.

These are not necessarily the same problem.

And they should not automatically produce the same response.

Before asking how to transform, organizations therefore need to ask a more fundamental question:

What problem are we actually trying to solve?

Without that diagnosis, transformation can become a response in search of a problem.

Transformation Is an Intervention Choice

Aaron Porter made another important observation.

Sometimes an organization does not need to transform.

It may need to repair something that is not working as designed.

It may need to optimize something that remains fundamentally sound.

It may need to adapt to a changed external condition.

It may need to simplify unnecessary complexity.

It may need to replace an obsolete capability.

It may need to stop doing something altogether.

And sometimes it may indeed need a deeper transformation.

This distinction matters because the language of transformation can unintentionally encourage organizations to treat scale of ambition as evidence of appropriateness.

But an intervention is not better because it is more transformational.

It is better when it is proportionate to the problem it is intended to address.

A large intervention applied to a poorly diagnosed problem does not become more effective because it is ambitious.

It may simply create more unnecessary change.

Transformation Appropriateness Is Not Transformation Readiness

This leads to a distinction that deserves greater attention.

Transformation appropriateness and transformation readiness are not the same question.

Transformation appropriateness asks:

Is transformation the right response to the problem we have diagnosed?

Transformation readiness asks:

Do we have, or can we create, the conditions required for that transformation to work?

The order matters.

An organization may possess strong leadership commitment, adequate funding, capable teams, effective governance, appropriate technology, sufficient decision authority, and a high degree of readiness for change.

None of those conditions demonstrates that transformation is the correct intervention.

They demonstrate only that the organization may be capable of executing it.

Execution capability cannot compensate for an incorrect diagnosis.

Nor can readiness turn an inappropriate intervention into an appropriate one.

The organization must first establish what kind of change, if any, the evidence actually justifies.

Only then does readiness become the right question.

Not Every Tension Is an Incoherence

Aaron Porter's comment also raised an important challenge to the argument I developed in the previous article.

I argued that transformation frequently encounters an Architectural Incoherence Gap between what the organization says it wants to achieve and the conditions it continues to preserve.

Organizations may ask for speed while maintaining slow approval mechanisms.

They may ask for autonomy while keeping decision authority centralized.

They may ask for innovation while penalizing reasonable experimentation.

They may ask for collaboration while rewarding local optimization.

But there is an important qualification.

Not every apparent contradiction is organizational incoherence.

Organizations operate under multiple legitimate requirements that can pull in different directions.

A bank may need greater experimentation while simultaneously requiring strong controls.

A manufacturer may need local autonomy while preserving process standardization.

An organization may need greater speed while maintaining governance mechanisms necessary to protect safety, regulatory compliance, financial integrity, or stakeholder interests.

These are not necessarily design failures.

They may be legitimate organizational tensions.

The challenge is not to eliminate one side of every tension.
It is to determine whether the organization has deliberately designed the conditions through which competing requirements can coexist.

Where should autonomy apply?

Where is standardization necessary?

Which decisions can be decentralized, and which require independent oversight?

Which risks can be accepted locally, and which must be escalated?

What should remain stable while other parts of the organization adapt?

Incoherence does not arise merely because legitimate requirements coexist.

It arises when the organization's architecture persistently undermines, or makes materially more difficult, the reconciliation of the outcomes it expects the system to produce.

That distinction matters.

Adaptability Is Not Permanent Transformation

There is a broader implication.

Organizations are increasingly encouraged to become more adaptive.
But adaptability can easily be misunderstood as an obligation to change continuously.

It is not.

As I argued earlier in this series, the most adaptive organizations are not necessarily those that change most frequently.
They are those capable of distinguishing when stability continues to create value and when change becomes necessary.

Sometimes the adaptive response is to transform.

Sometimes it is to modify or strengthen a limited part of the system.

Sometimes it is to remove something that no longer serves its purpose.

And sometimes the most intelligent response is deliberately to preserve stability.

The capacity to change is only one part of adaptability.

The capacity not to change unnecessarily matters as well.

The Cost of Solving the Wrong Problem

Organizations rarely have unlimited transformation capacity.

Every significant intervention consumes leadership attention, management capacity, financial resources, organizational energy, employee attention, trust, time, and opportunity.

Transformation also introduces uncertainty into systems that often need to continue operating while they are being changed.

Unnecessary transformation therefore has a cost even when it is competently executed.

There is also a less visible cost.

When organizations repeatedly launch transformations that fail to address the underlying problem, people learn from that experience.

Future initiatives may encounter skepticism that is subsequently described as resistance to change.

But what appears to be resistance may partly reflect organizational memory.

People may have experienced previous programs that changed terminology, structures, roles, technologies, or reporting lines without resolving the conditions that originally created the problem.

In such circumstances, the more useful question may not be:

Why are people resisting transformation?

It may be:

What has the organization taught them to expect from transformation?

Diagnosis therefore matters not only for selecting the right intervention.

It also affects the credibility of future change.

From Transformation Reflex to Intervention Discipline

A more adaptive organization should therefore avoid two opposite errors.

The first is structural inertia: continuing existing arrangements after the conditions that justified them have materially changed.

The second is transformation reflex: assuming that significant problems necessarily require large-scale transformation.

Both can disconnect organizational action from reality.

A more disciplined sequence begins differently:

What is happening?

What evidence supports that diagnosis?

Which assumptions have changed?

What should remain stable, and what actually needs to change?

What type and scale of intervention does the problem justify?

Is transformation necessary?

And only then:

What must already be true for that transformation to work?

This sequence changes transformation from an organizational aspiration into a decision that must itself be justified.

Aaron Porter ended his comment with that final question:

What must already be true for this transformation to work?

I would retain it, but place another immediately before it:

What must be true for transformation to be the right response in the first place?

The first tests readiness.

The second tests appropriateness.

Both are necessary.

Neither can substitute for the other.

A Different Understanding of New Ways of Working

This brings us back to the broader argument of this series.

New ways of working are often associated with greater speed, agility, experimentation, technology, distributed decision-making, and continuous adaptation.

All of these can matter.

But perhaps organizational maturity is demonstrated not by the amount of change an organization can generate, but by the quality of the choices it makes about change.

Can it distinguish symptoms from causes?

Can it determine what should remain stable and what should change?

Can it select an intervention proportionate to the problem?

And can it reconsider those judgments when the evidence changes?

If it can, adaptation becomes something more than responsiveness.

It becomes disciplined organizational judgment.

The next evolution in how organizations work may therefore not be about becoming better at transformation.

It may be about becoming better at determining what should change, what should remain, and whether transformation is the right response at all.

Because before an organization asks whether it is ready to transform, there is a more fundamental question it should be able to answer:

Why transformation?