Theme 2, Article 1: The Transformation Outcomes Value Chain - Moving the Dial

Local government invests significantly in transformation. Councils redesign services, implement new systems, restructure teams, and commission major change programmes, all in pursuit of better outcomes for residents, efficiency savings, and more sustainable ways of working.

The Local Government Association has identified benefits realisation as one of the sector's most persistent transformation challenges, a finding that will resonate with many leading transformation in local government today. I call this the the Value Realisation Gap. A more granular understanding of how value is formed and what determines its trajectory offers a practical route to stronger outcomes.

THE VALUE CHAIN

The transformation programme Value Chain is a realisation model focused on optimised and sustainable end-point benefit. It describes how declared Strategic Direction (intent) translates into Operational Outcomes through a series of managed conversions.

Intent converts to Enabling Capability architecture, which in turn converts to Enabling Outputs (Products). Product Integration subsequently forms Enabling Outcomes, the new or improved Capabilities: at this point value exists in Latent form, Contingent upon the successful deployment of those capabilities into live use. The point at which they become operational is the Value Exposure Point, where latent value meets the organisational conditions that will determine the Value Realisation trajectory.

At the point of Transition, into live use, enabling outcomes are Activated and leveraged to form Operational Outcomes, where Realised Value (Benefits) reside. Beyond transition, full realised value typically requires persistent Realisation Management to Optimise and Sustain it.

Figure 1: The Transformation Outcomes Value Chain

The value chain and the Delivery Lifecycle are complementary instruments: the former describes and tracks value formation across conversions; the latter describes and tracks delivery activity across lifecycle stages. Each conversion represents a distinct structural condition that shapes the extent to which intended benefit becomes realised value.

THE OUTCOMES VALUE DIAL

Outcome is a Duality of changed states: Latent (contingent) Value and Realised Value. Value, which itself is a duality of changing states.

A convenient way to think of value chain action is through the image of a dual-faced Value Dial, one face tracking latent value, the other face tracking realised value, each governed by different conditions and moving, or stabilising, at different times and different rates.

Figure 2: The Transformation Outcomes Value Dials

Latent value begins to form when enabling capability architecture starts to be expressed in design. Realised operational value starts to emerge only post-transition.

The latent value dial begins to move with architecture design but remains contingent on the deployment of enabling outcomes and, following operational acceptance, successfully transitioning the capabilities into live use. The realised operational value dial cannot begin to move until that point.

THE DUALITY OF OUTCOMES

Enabling outcomes describe what the organisation is now capable of doing differently. Operational outcomes describe what the organisation is actually achieving and sustaining in practice. This distinction is important.

Classical programme discourse places primary focus on outcomes. The value chain refocuses on benefits. It clarifies that enabling outcomes are not the end point and that operational value realisation lies beyond.

Managed transition, consistent operational use and persistence must follow if intended benefit is to be fully realised, or exceeded, and sustained. Operational outcomes typically won't be optimised until the new capabilities are embedded in day-to-day activity, with performance actively managed and monitored, and the configuration adjusted either to address under-performance or incorporate over-performance.

INTERACTION DETERMINES REALISATON

Each element of the value chain can function in isolation. Direction can be clear, with capability architecture that is strong, or weak. Capabilities can be well defined, with products that converge, or diverge. Products can be delivered, with integration that is full, or partial. Integration can appear complete, with operational embedding that is strong, or fragile.

Isolated conversion success does not guarantee realised benefit. At the design and delivery levels, weak interaction may show as loose architectural definition, poor data quality, or insufficient integration testing. At the deployment and realisation levels, it may show as weak transition planning, inadequate early life support, or failure to monitor, optimise, and sustain operational performance under live conditions.

It is the interaction between strategic intent, enabling architecture, programme outputs, product integration, enabling outcomes, and operational outcomes that determines if, and the extent to which, end-point value will be realised and sustained.

Executive judgement is strengthened when performance at any given stage, is assessed in relation to its contribution to the value chain as a whole. Activity completion within the lifecycle does not typically equate to operational value. Operational value depends on how successive conversions meaningfully advance the formation, initial realisation, optimisation, and sustainability of intended benefit.

DESIGN AS THE FOUNDATION

Programme design begins with benefits, which define value. If benefits are unclear, the enabling architecture may lack focus. Benefits must be explicit enough to guide architectural decisions: what must change, for whom, to what effect, and how realisation and sustained value will be evidenced.

Benefits profiling - baseline performance, target performance, predicted trajectory, measurement frequency, data requirements, data quality, and ownership - are design stage choices and decisions. Programme delivery and proactive operational management make it work in practice.

SHARED RESPONSIBILITY

Programmes have an ongoing but shared responsibility through deployment, activation, and early life support, until an agreed point of operational stability is reached. Value optimisation then becomes an operational responsibility, delivered through proactive management, performance monitoring, and necessary adjustment beyond programme involvement.

Activity progression without value realisation does not meaningfully move the dial. Value realisation without proactive management may not be sustained. What moves the dial in transformation delivery is not simply what is done, but how strategic intent converts through design, capability building, integration, and operational embedding, to optimised operational value that holds over time.

he value chain does not replace the delivery lifecycle. It complements it, explaining how work progresses, and providing a practical lens through which value formation and realisation can be tracked in real-time.

Without a shared understanding of how value forms and what governs its realisation, transformation risks being measured by the wrong things, and the most consequential conversion, from contingent value to realised value, may not receive the ongoing governance attention it requires.

The programme value chain makes that risk visible. The value dial makes it measurable. Closing the gap is not a technical problem. It is a leadership and governance challenge.

The leadership dimension of that challenge, why capable and well-informed leaders still allow the realisation gap to persist, cause, effect, and what needs to change, will be explored in a later article.

=================================================================

VALUE CHAIN DEFINITIONS

Strategic Direction (Intent): The declared organisational purpose that a transformation programme exists to serve; the starting point from which all value chain conversions flow.

Architecture Design: The process through which strategic direction is translated into a structured design of the capabilities the programme must build; the first conversion in the value chain.

Enabling Capability Architecture: The structured design of the capabilities, people, process, technology, and information, that the programme must build to convert strategic intent into operational outcomes.

Product Design: The process through which enabling capability architecture is translated into discrete, deliverable products; defining what must be built to realise each capability.

Enabling Products: The discrete deliverables produced by the programme that, when integrated, form the enabling capabilities that transition then activates to underpin operational outcomes.

Product Integration: The process through which enabling products are combined and configured to form coherent enabling outcomes; the stage at which individual deliverables become collective capability.

Enabling Outcomes: The new or improved capabilities that the programme makes available to deploy into live operational use; what the organisation can now do differently, not yet what may be achieved.

Operational Outcomes: The measurable changes in organisational performance that result from the deployment, activation, and use of enabling outcomes in live operation; what the organisation is actually achieving and sustaining in practice.

Latent (Contingent) Value: The value that begins to form during architecture design and accumulates throughout delivery but remains contingent on successful transition into live operational use; value that exists in potential but is not yet realised.

Capability Activation: The point during transition at which enabling outcomes are fully deployed into live operational use; the moment at which the operational value dial can begin to move.

Value Exposure Point: The point at which latent value created by programme delivery is exposed to the operational conditions that will determine whether it is realised, optimised, or eroded.

Realisation Management: The deliberate and sustained management activity required post-activation of enabling capabilities to drive realised value toward its intended trajectory; it does not happen automatically and must be proactively owned beyond programme closure.

Realised Value: The measurable operational benefit actually achieved and sustained in practice following transition; the endpoint of the value chain.

Optimise: The proactive management of realised value beyond initial transition to strengthen performance toward its intended target, or exceed target, once an initial baseline has been established.

Sustain: The ongoing operational discipline through which optimised value is held around a steady state, through embedded performance management beyond programme involvement.