Transformation frameworks often look coherent in theory.

The harder question is what happens when they meet a real organisation.

This case reflects a large-scale product creation renewal programme in a global enterprise. The ambition was clear: reduce R&D costs, shorten development cycles, improve time-to-market, and create a more effective product creation system across the company.

The intent was strong. The business case was real. The top-level targets made sense.

And yet the transformation struggled.

This case became important to me for one reason in particular:

It made visible many of the human and organisational dynamics that formal change models tend to underestimate. In that sense, it also became one of the foundations for the "Human-Based Change Leadership model".

This Case Study is documented in my Thesis (Ekdahl, 2009). This article presents high-level summary of it. Qualitative methods were used such as documentation review and semi-structured interviews. Grounded theory principles were used in the model (Human-Based Change Leadership) creation.

1. The Transformation Logic Was Rational — but Incomplete 

The programme was launched in response to a genuine performance problem:

• product development costs were too high

• cycle times were too long

• competitive pressure was increasing

External experts were brought in. Benchmarking was carried out. A company-wide programme was launched. A recognised change model was chosen as the reference point.

On paper, this looked like a rational and well-founded transformation effort.

But the design logic remained heavily process-driven.

The programme focused strongly on target architecture, process renewal and high-level objectives. What it did not build early enough was:

• shared ownership across the organisation

• a jointly created current-state understanding

• sufficiently concrete targets for different parts of the business

• or broad commitment from the managers expected to carry the change into practice.

The transformation had a logic. But it did not yet have enough organisational traction.

2. What Failed First Was Not Implementation — but Alignment

One of the most revealing findings in the case was that failure did not begin at the point of rollout.

It began much earlier.

The organisation never developed a sufficiently shared understanding of:

• why the change was necessary

• what exactly it meant in practice

• and what different parts of the organisation were expected to do differently. 

The overall vision was generally seen as valid.

But the translation from vision into concrete, owned, measurable action was weak.

This created a familiar gap:

• top management endorsed the programme

• but middle management did not truly commit to it

• and operative organisations did not see enough of their own reality reflected in it

As a result, what looked like a company-wide transformation increasingly became perceived as an initiative designed elsewhere and imposed from above.

Once that perception takes hold, resistance no longer needs to be loud to be effective.

4. Resistance Was Not the Root Cause — It Was a Signal

Resistance in this case was substantial, but it should not be misunderstood.

It was not simply irrational opposition.

It reflected several deeper issues:

• lack of shared understanding

• weak involvement in shaping the change

• perceived threat to existing power relations

• lack of trust in the programme's practicality

• and the sense that the initiative did not sufficiently reflect operational reality. 

In some parts of the organisation, resistance became active sabotage. In others, it took the more typical form of passive non-cooperation, delay, or symbolic compliance.

What is striking is that much of this resistance was visible early.

But it was not addressed with enough force, clarity or consistency.

This is one of the strongest practical lessons from the case:

When leaders treat resistance only as opposition, they miss the information embedded within it.

6. A Practical Insight (30 Years in the Field) 

What makes this case so valuable is not that it was uniquely dysfunctional.

It was not.

Its patterns are familiar.

I have seen similar dynamics repeatedly in large transformations:

• strong logic at the top

• weak ownership in the middle

• insufficient translation into operational reality

• underestimated politics

• and overestimation of what process design alone can accomplish. 

This case also reinforced something I have learned over time:

Transformation success is rarely decided by the quality of the framework alone.
It is decided by whether the organisation is actually able and willing to move with it.

That is a different question.

And a far harder one.

8. Toward More Predictable Transformation Outcomes

This case did not only show what failed.

It also showed what improved outcomes:

• stronger and more credible leadership

• clearer engagement with operative organisations

• more direct confrontation of conflict and resistance

• better alignment between business targets and transformation targets

• and more concrete implementation structures where ownership was real. 

One business unit, for example, linked its own business targets directly to the transformation, resourced the implementation seriously, created a dedicated virtual implementation organisation, and succeeded.

That is important.

Because it shows that transformation did not fail everywhere for the same reason.

It succeeded where the human and organisational conditions for success were created.

That insight matters far more than whether a formal programme was labelled a success or failure.

Transformation becomes more predictable when we stop evaluating only the programme — and start evaluating the conditions under which the organisation is being asked to change.