Programme Management: How organisations turn strategy into measurable impact

When transformations stall, it is rarely because too little is happening. In most cases, too much is happening at the same time — well intentioned, but without overarching coordination. Organisations embarking on major transformations typically have plenty of initiatives. Digital services, platform modernisations, regulatory compliance programmes, AI-driven process improvements. Each initiative makes sense on its own, with its own team, its own budget and clearly defined objectives. And precisely here, a major challenge arises: these initiatives do not stand alone. Programme Management consolidates them. And it addresses a fundamentally different problem than traditional project management.

Projects deliver outputs. Programmes deliver outcomes.

This distinction may sound subtle. It is not. A project delivers a clearly defined result within a fixed scope: an ePA interface goes live, a regulatory requirement is met, a process is automated. The project is considered a success. And yet the organisation is often barely better off than before. In many cases, nobody is responsible for how a project interacts with parallel initiatives or what actually happens after going live. What’s the impact? Which dependencies come into play? What’s the long-term value‑?

This pattern is consistent across industries and organisations. Audit and oversight authorities in multiple countries, including the European Court of Auditors, have repeatedly concluded that organisations put significantly more effort into justifying investments and defining budgets and timelines than in systematically tracking the actual benefits Benefits management often ends with the project.

Programme Management addresses this weakness by embedding benefits realisation from the outset. It does not treat related initiatives as independent efforts but as a coherent system of change with a shared goal hierarchy, explicit dependencies and a common understanding of success. It is not “more project management”, but a different success logic altogether. The difference lies in a single word: impact. It’s not about what was delivered, but about what changed as a result — for the organisation, the market and the people who ultimately use the service.

The hidden cost of missing programme steering

One aspect is routinely overlooked: the financial impact of missing coordination. When many parallel initiatives run without steering on programme level, duplication, conflicting objectives and invisible double efforts emerge. In its analyses of centralised versus decentralised IT implementation, the European Court of Auditors found that more centralised approaches enable substantial economies of scale. Model-‑based scenarios show that every euro invested centrally can generate savings of up to four euros at a decentralised level. This is not abstract theory. It is the kind of value that systematically remains untapped if nobody thinks at programme‑level.

Without a programme layer, investments are optimised locally, but not in terms of how they work together. This is where most value erosion occurs.

The dynamic is the same across industries. Without programme steering, value does not disappear because teams perform poorly. It disappears because the overall system is not optimised for impact. Architectural decisions, reusable components and common standards are largely invisible within individual projects. At programme level, they become core steering levers.

Risk is another critical factor. A widely cited analysis of more than 1,400 IT projects by Bent Flyvbjerg and Alexander Budzier came to a sobering conclusion: the greatest risk in complex IT initiatives is not average overruns, but extreme outliers. One in six projects turns into a “black swan”, with massive cost and schedule overruns. Programme Management establishes the governance needed to identify such risks early on and intervene before they undermine the value of all initiatives.

Silos are not a failure. They are a design feature.

Fragmented initiatives are not a sign of poor leadership. They are the logical consequence of how complex organisations are structured.

Functions are optimised for their specific responsibilities; systems are designed around local requirements and teams are organised along historically grown structures. Finance aligns its reporting with regulatory requirements. IT units make platform decisions based on technical criteria. Each of these decisions makes sense on its own. Taken together, however, they create a system that is difficult to coordinate.

There is also a cultural dimension. In organisations where knowledge and access to information translate into influence, teams develop a protective stance towards “their” data and processes. This is not self-interest. It is a rational response to organisation‑al incentives. Mergers and acquisitions amplify this effect. The result is not dysfunction, but a structural reality. The question is not whether silos exist, but who takes responsibility for bridging and actively steering them towards a shared objective. That responsibility sits at programme level.

Why the healthcare sector serves as a prime example

Few industries illustrate the complexity of transformation as clearly as healthcare and insurance. Consider what is currently happening in the German health insurance landscape all at once: the rollout of the electronic patient record (ePA), the European Digital Identity Wallet (eIDAS / EUDI), secure communication infrastructures such as TIM (TI messenger), platform modernisations and AI-supported claims processing — all while economic pressure increases due to regulatory interventions and political cost containment measures.

Each initiative is complex in its own right. Taken together, they form a transformation that no single project manager can steer. According to the GKV umbrella organisation, around 70.5 million electronic patient records had been created by February 2025. This figure does not represent a completed IT project. It represents a programme level change. Its real value depends on how well technology, operations, security, communication‑ and adoption interact.

This is how Programme Management operates: rather than delivering individual components, it deliberately aligns all elements that need to work together so that the interplay of parts produces the intended outcome.

A practical example: during BARMER’s digital repositioning, the rebranding programme encompassed more than 100 product teams, numerous external partners and a system landscape that had evolved over decades. The decisive success factor was a dedicated programme layer with clear governance, active risk management and transparent dependency coordination. The result was a stable go live without disrupting live services —  and a solid foundation for further transformations.

What Programme Management actually delivers

Programme Management creates the structural conditions that make complex transformations steerable. Not through additional bureaucracy, but through a clear decision logic and transparency across dependencies.

Imagine a health insurer simultaneously managing the ePA rollout, the introduction of TIM and a platform modernisation. Without a programme layer, each initiative follows its own logic — until all three of them suddenly require the same IT capacity, the same subject matter experts or the same test environments. Who decides what takes priority? Who notices that a delay in initiative A blocks acceptance in initiative B? Who ensures that an architectural decision made by the platform team today does not complicate TIM operations in six months’ time? Without a programme layer, the answer is simple: no one.

In practice, Programme Management means a clear decision logic that prioritises actions based on their contribution to the overall programme objectives, not on project-internal convenience. It means making dependencies between workstreams, teams and external partners visible and actively managing them. Strategic direction is set from the top down. Leadership priorities are embedded in every initiative, while risks, blockers and escalations are fed from the bottom up before they turn into crises. It also means flexible resource management across the entire programme‑: people and budgets can be shifted between initiatives as circumstances change, instead of remaining locked into project structures that no longer reflect reality.

The Project Management Institute (PMI) summarises what distinguishes this approach from classic project management in its M.O.R.E. framework. Successful programme steering is not measured by procedural compliance, but by four practices: actively shaping stakeholder perceptions rather than assuming them, taking responsibility for real value rather than just scope, budget and schedule, continuously reassessing objectives and success criteria as reality evolves and broadening the view beyond the immediate programme to organisational, strategic and, sometimes, societal impact.

Research by the Project Management Institute supports this view. Organisations with a mature benefits management complete 45 percent more projects successfully in terms of their original business objectives. The same study shows that poorly managed project portfolios lose an average of 11.4 percent of total investment. Structured programme steering directly reduces this loss. Not through better project management, but by ensuring that the right initiatives contribute to the right objectives in the right sequence.

The difference that truly matters

Project management asks: are we delivering correctly? Programme Management asks: are we delivering the right things, in the right order, in a way that creates sustainable value for the organisation?

In a world of constant transformation, this distinction is crucial. Organisations that take Programme Management as a discipline seriously do not simply complete more projects. They change in a more focused, efficient and sustainable way.

Programme Management is not a universal remedy, and it does not prescribe a methodology. But in complex transformations, it is the prerequisite for achieving systematic impact in the first place. It adapts to context: to the complexity of the initiative, the maturity of the organisation, regulatory constraints and the people driving the transformation. It always ensures that the effort organisations invest in transformation actually translates into impact, not just delivery.

Share