Theme 3, Article 5: Value Realisation, Ownership and Accountability

My series of articles exploring Moving the Dial in Transformation Delivery introduced the Transformation Programme Value Chain as a realisation pathway from strategic intent to persistent, realised value.

Those articles established the value chain as a design artefact: integrated rather than method-bound, coherent across governance tiers, and held together through deliberate decision flows.

This article examines how ownership and accountability for value realisation are maintained as delivered capabilities become operational and the value they were intended to produce is realised.

The Nature of Value

Capital-based investment schemes can generate returns through both the value of the asset itself and the operational value derived from its use. A new building, for example, has an asset value, but also generates operational value through occupation and operation.

Revenue-based transformation programmes, particularly those targeting savings, cost avoidance or income generation, work differently. They typically deliver new or enhanced capabilities rather than disposable assets. A new operating model or integrated service may possess substantial latent value, but that value remains contingent on the capability being put to effective operational use.

For a capital scheme, some value may accrue as soon as the asset is completed. For a service transformation, the intended return depends on changed operational activity, adoption and sustained performance. Some benefits may not be fully realised until well after the programme that delivered the capability has closed.

Delivering the capability and realising its value are connected outcomes, but they are not the same outcome. The delivery system must account for both.

Where Realisation Bites

The point at which delivered capability first encounters live operational conditions is the Value Exposure Point. Its potential value begins to be tested against operational reality, and the operational Value Dial can begin to move.

From there, capabilities need to be activated, adopted and embedded in operational use. The resulting operational outcomes must be developed and sustained towards the intended realisation value.

Responsibility for this work belongs principally to the receiving operational area, but the transition from delivery to operations is not a single handover event. Acceptance typically has two stages.

Stage 1: Acceptance into operational use. The receiving operation agrees to accept the changes and put the delivered capability into operational use.

Stage 2: Evidence based acceptance of the realisation trajectory. Progress is agreed to be sufficiently along the planned trajectory to support the transfer of accountability for ongoing realisation and optimisation.

Between these points, delivery programmes typically provide close operational support while the capability becomes established and the conditions for realisation are demonstrated. The programme would normally close following Stage 2 handover.

The interval should allow sufficient time to demonstrate that realisation is progressing as intended, without becoming an indefinite period of shared responsibility.

Full realisation is rarely immediate. The expected realisation trajectory must therefore be established in advance, providing a reference against which actual progress against planned trajectory can be measured.

Realisation management must be active and proactive. Emerging divergence from the planned trajectory must be identified and brought to the attention of the appropriate owners as soon as it becomes apparent that realisation is struggling. Early intervention provides an opportunity to investigate the causes, agree corrective action and determine whether the intended value remains achievable.

Programmes enable; operations realise, optimise and sustain. Realisation management connects the two, maintaining visibility of progress and prompting intervention until the conditions for handover have been met.

Designing for Value Realisation

Maximising value realisation is neither mysterious nor a matter of chance. It depends on conditions that can be identified and incorporated into solution design. Five are particularly important.

1. Well-founded programme design: The capabilities selected must be able to produce the intended value. Design must rest on tested assumptions about how those capabilities will change operational activity and generate the expected outcomes.

   
   

2. An engaged and prepared receiving operation: The receiving operation must be ready, willing and equipped to use the delivered capability. Its involvement in design, preparation and transition is essential to achieving the necessary readiness.

   
   

3. Validated realisation expectations: The assumptions underpinning intended value must be validated, including those concerning operational adoption, the timing and pattern of benefits, and the conditions that need to persist after programme closure.

   The expected realisation trajectory provides the reference against which progress can be assessed, emerging problems identified and corrective action initiated.

   
   

4. Sustained operational drive: The receiving operation must maintain the effort required to embed the capability and achieve the intended outcomes. Implementation and programme closure do not, by themselves, establish that the intended value has been realised.

   
   

5. Deliberate optimisation: Initial operational use is not necessarily the point at which the intended value has been achieved. Performance must be monitored and strengthened towards target, with realised benefits verified and recognised appropriately.

These conditions are design considerations, not activities to be left until the end of delivery. Each is within the organisation's capacity to influence and should be addressed deliberately.

Accountability and Responsibility

The conditions for value realisation need clear ownership. Two distinct forms of accountability operate across the transition from delivery to operations.

The sponsor is accountable for establishing the conditions for value realisation. That accountability persists beyond the initial acceptance of changes into operational use. It is discharged only when the agreed conditions have been demonstrated and progress has been accepted as sufficiently on the planned trajectory.

Operational management is accountable thereafter for ongoing realisation and optimisation. It must prepare to receive the capability, make it operational and work with the programme to monitor and review progress towards intended operational outcomes.

Programme management typically continues to provide close operational support until Stage 2 handover. The acceptance criteria, evidence required, responsibilities during the transition and authority to approve the handover should be designed into the delivery arrangements.

The realisation trajectory provides the basis for monitoring progress, determining when intervention is necessary and establishing whether the conditions for Stage 2 acceptance have been met.

Accountability must follow the agreed conditions for its transfer, not the administrative timetable for programme closure.

Maintaining Ownership

Maintaining this distinction across a portfolio presents a wider challenge. Individual programmes may close while their intended benefits remain in development, and operational areas may be managing outcomes arising from several programmes simultaneously.

The organisation therefore needs a structure that maintains visibility of intended value, identifies who is accountable for its realisation, preserves ownership across handovers and highlights where intervention is required.

It must monitor realisation trajectories across the portfolio, distinguish expected progress from emerging under- or over-performance, and ensure that exceptions receive appropriate attention. This requires a connection between programme-level arrangements and corporate oversight, without displacing the responsibilities of operational management or the accountability of sponsors.

The final article in this series will examine the Corporate Programme Management Office, Transformation Office, or hybrids, as the nerve centre of transformation delivery.