The Difference You Feel: What Transformation Designed to Last Actually Requires

The moment when transformation has genuinely entered an organisation's behaviour is rarely the one anyone planned for. It does not tend to happen at the end-of-programme review, though those have their place. It tends to happen earlier and more quietly: a decision that would previously have required escalation gets made at the right level; a disagreement that would previously have been managed around gets surfaced and resolved; a governance meeting produces a genuinely difficult decision rather than a technically defensible deferral. The change becomes visible in how people behave before it appears in any measurement.

This distinction between transformation that has entered behaviour and transformation that has produced outputs is one the water sector is currently being asked to make in specific and observable terms. Ofwat's PR24 final determinations require water companies to demonstrate collaborative delivery capability that is genuinely embedded in how they work with supply chains and alliance partners, not just reflected in their governance documentation. The organisations doing this well are doing so differently from those that implemented structures and called it transformation, and the gap between them is becoming apparent not in how they describe their approach but in how they respond when the regulatory assessors look at behaviour under pressure rather than at what the programme documentation describes.

What separates transformation that produces lasting behaviour change from transformation that delivers a plan? Looking across major programmes where the change did stick, certain conditions tend to appear together rather than independently.

The starting point is an honest diagnostic picture rather than a comfortable one. Transformation built on a sanitised account of the organisation's situation tends to address the symptoms that are visible rather than the dynamics causing them, and the improvement is correspondingly limited. Getting to the honest starting point is not a technical challenge; it is a conditions challenge, requiring the same kind of psychological safety that was explored last week in the context of diagnostic work.

The second condition is that the programme is designed, from the start, for the client to own the progress rather than the consultant to own the delivery. The practical implications of this design choice run deep: the measures of success become the client's growing ability to tackle the challenge independently, not the consultant's record of completion; capability transfers explicitly as the programme proceeds rather than residing in the consultant's tools and frameworks; the relationship is structured as a genuine partnership in the work rather than a provision of expertise at the work.

The third condition is that the programme works across systems, structure, and culture simultaneously. Systems and structure changed without corresponding cultural conditions produce compliance rather than genuine capability. Culture worked on without changes to the systems and structures that currently reward different behaviour produces willingness that evaporates when people return to incentives pointing in the old direction. The integration is not a design preference; it is what makes change durable.

What holds these conditions together is a specific approach to the relationship between consultant and client throughout the programme. Transformation designed to last requires the consultant to challenge honestly what is not working - including things the client would prefer not to examine - whilst genuinely supporting the people going through the discomfort of changing it. Not challenge first and then support, and not support that softens challenge, but both simultaneously, sustained through the evolution that follows. This is harder than delivering a plan, and it requires a different kind of presence than most transformation programmes are structured around.

The PR24 context makes this visible in a useful way. Organisations under genuine regulatory scrutiny of their collaborative capability cannot perform collaboration convincingly across a period of years when assessors are examining behaviour rather than documentation. The transformation either happened or it did not, and the evidence is in how people work when the organisation is under pressure rather than how the governance framework reads.

Whether transformation lasts is visible six months after it ends. The question is whether you would recognise what you are looking for.

References

Ofwat (2024) PR24 Final Determinations. Collaborative delivery requirements across the water sector. Available at: https://www.ofwat.gov.uk/
Major Projects Association (2025) Mobilisation Perspectives Report, February 2025. Available from project files: Mobilisation_PerspectivesReport_Final_26Feb25.pdf