Theme 3, Article 2: From Methods to Delivery System: What integrated delivery means.
Updated: Sep 30
Investment in transformation methods is substantial. Most organisations involved in transformation will have adopted recognised approaches across programme management, project management, risk, benefits, change, service, and value management.
Many will also have invested significantly in training, accreditation, and supporting tools.
The question is not whether these methods are valuable. They are. The more fundamental question is what connects them.
Methods have a purpose
A methodology provides structure, discipline, and repeatability within a particular area of practice.
Project management provides a framework for controlling the development of outputs.
Programme management provides a framework for coordinating related projects and managing change towards outcomes.
Risk management provides a structured approach to identifying and treating uncertainty.
Benefits management provides a framework for establishing and tracking the value expected from change.
The same principle applies across the other disciplines involved in transformation.
Each has its own language, processes, accountabilities, and information requirements. That is not a weakness. It is what allows practitioners to develop expertise and apply appropriate discipline to a particular problem.
The difficulty begins when those boundaries become organisational boundaries.
A transformation does not experience its work as separate methodologies. A decision about project scope may affect programme outcomes. A programme risk may require portfolio intervention. A change in delivery design may alter the benefits case. A transition into operational service may determine whether an intended benefit is actually realised.
The methods remain separate disciplines. The transformation does not.
The space between the methods
This is where the delivery system earns its place. It is not another methodology competing with those already in use. It is the architecture that connects them.
It establishes how information moves between disciplines, how decisions cross organisational and governance boundaries, where accountability sits, and how the consequences of decisions in one part of the system are recognised elsewhere.
Consider a risk identified within a project.
The project method can establish how that risk is recorded, assessed, and treated. But the project method alone does not determine whether the risk has implications for a programme outcome, a portfolio priority, a benefit, a service transition, or a strategic commitment.
Those are system questions.
Similarly, a benefits framework can establish ownership and measurement. But it cannot, by itself, ensure that a change in programme design triggers a corresponding review of the benefit assumptions, or that ownership survives the transition from delivery into operational service.
Again, those are system questions.
The important design space is therefore often between the methods rather than within them.
Integration is a design discipline
An integrated delivery system provides the connections through which the individual disciplines can operate as part of a coherent whole.
At its simplest, that means designing five things deliberately:
Information flows: what information needs to move, between whom, and when.
Decision rights: which decisions belong at which level, and when they need to move upwards or across.
Accountability: who remains accountable when responsibility moves between teams, phases, or organisational boundaries.
Governance: how the different parts of the transformation are brought together for coherent oversight and decision-making.
Interfaces: where one discipline, delivery tier or lifecycle stage hands information, decisions, or responsibility to another.
These are not replacements for the underlying methods. They are the connections that allow the methods to work together.
Without them, an organisation can have competent practitioners applying credible methodologies while still experiencing gaps at the interfaces between them.
From compliance to coherence
This creates an important distinction between having methods and having a delivery system.
An organisation can demonstrate methodological compliance. Projects may follow their required processes. Programmes may operate their governance arrangements. Risks may be reported. Benefits may have owners. Change activity may have its own structure.
All of those things can be individually sound. The question is whether they form a coherent system.
Does information arrive where it is needed to support a decision?
Does a decision made at one level trigger the consequences that need to be considered elsewhere?
Does accountability survive the movement from concept through design, planning, delivery, and transition into operational use?
Does the governance structure reflect how the transformation actually works, rather than simply reproducing the boundaries of the methodologies?
These are indicators of system design rather than methodological compliance.
The delivery system does not replace the methods
This distinction is important.
The answer to fragmented delivery is not to create another universal methodology and ask the organisation to adopt yet another set of processes. Nor is it to discard established methods in favour of a single overarching framework.
The more practical proposition is to connect what already works.
An integrated delivery system should allow an organisation to retain the specialist disciplines and methodologies it has chosen, while providing the architecture within which they collectively operate.
The result is not one method replacing many. It is many methods operating as one delivery system.
That requires deliberate design. The connections cannot be left to individual practitioners to discover for themselves, nor can they be assumed to emerge from methodological compliance.
Organisations need to decide how their delivery disciplines fit together, where their interfaces sit, how information and decisions flow across them, and how accountability is maintained across the whole transformation lifecycle.
That is the difference between an organisation that has a collection of methods and one that has designed a transformation delivery system for applying them collectively.
The objective is not to compete with the methods. It is to connect them.
Comments