The Programme Management Vacuum
A programme is not a bigger project; it is a different kind of governance altogether, and organisations that treat it as mere scale keep discovering the difference the hard way.
Executive Summary
Through the second half of 2000 and into this year, I have watched a familiar scene repeat itself across organisations of very different shape and sector. A portfolio of change initiatives is underway – sometimes a dozen, sometimes forty – each with a competent project manager, a plan, a budget line, and a sponsor somewhere in the executive layer. What is missing, almost invariably, is the layer above: the programme. No one is asking whether these projects, taken together, still add up to the benefit case that justified them individually. No one owns the interdependencies. No one is empowered to stop a project that has drifted from strategic purpose even while it remains, by its own narrow measures, on time and on budget.
This essay is an attempt to understand why. Not to catalogue the symptom – the vacuum is easy enough to observe – but to ask what structural forces in organisational life sustain it, and what its persistence through the dot-com collapse and its aftermath tells us about the maturity of change delivery as a profession. My conclusion, stated plainly at the outset, is that the vacuum is not an oversight. It is the predictable output of incentive structures, funding mechanisms, and professional identities that were built for projects and have not yet been rebuilt for programmes.
The Shape of the Vacuum
The pattern is consistent enough that it is worth describing in some detail, because the detail is where the explanation lives.
An organisation – a bank integrating systems after a merger, a retailer building an e-commerce capability, a utility responding to deregulation – finds itself running many change initiatives simultaneously. Each was commissioned separately, often at different points in the budget cycle, each with its own business case built to satisfy the capital approval process. Each has a project manager trained, if trained at all, against the PMBOK Guide’s disciplines of scope, time, cost and quality. Each project manager is measured, quite reasonably, against the delivery of their own project.
What none of them is measured against – what none of them could reasonably be measured against, given their mandate – is whether the collection of projects still serves the strategic intent that justified the spending in the first place. That is a programme question, and in the majority of organisations I have observed this year, there is no one whose job it is to ask it.
The symptoms of this absence are recognisable everywhere:
- Two projects independently procure overlapping capability, discovered only when both go live
- Neither project manager was wrong to proceed; neither had visibility of the other’s scope
- Benefits realisation plans exist on paper but no one is accountable for tracking them once the project closes
- A change in market conditions – and there have been many since the market correction began in March 2000 – renders part of the portfolio obsolete, but the projects continue because stopping them requires an authority that does not exist
- Resource conflicts are resolved by whichever project manager shouts loudest or whose sponsor sits closest to the board, not by reference to strategic priority
None of this is new to programme practitioners. What is striking is how persistent it has proven even as the theoretical remedy has been available and, in the United Kingdom at least, formally published. The Office of Government Commerce issued Managing Successful Programmes in 1999, building on earlier work, with a clear articulation of programme management as a distinct discipline from project management – concerned with benefits, with blueprint, with the management of a portfolio of projects toward a defined future state. Two years on, its adoption remains patchy, its language unfamiliar to most project sponsors, and its disciplines – benefits realisation planning, blueprint design, tranche-based governance – applied, where applied at all, as documentation exercises rather than as genuine changes to how decisions get made.
Why the Collapse Made This Worse, Not Better
One might have expected the market correction that began in the spring of last year to sharpen organisational discipline around programme governance. Money became scarcer. Boards became more exacting about return on investment. Surely this is precisely the environment in which the programme layer – the layer that asks whether spending still serves strategy – becomes indispensable.
In practice I have observed close to the opposite effect, and it is worth being precise about the mechanism.
When budgets tighten, the instinctive organisational response is to scrutinise individual projects more closely – to ask each project manager to justify their spend, to demand tighter business cases, to impose stage gates. This is not wrong in itself. But it reinforces exactly the wrong level of analysis. It asks “is this project delivering what it promised” project by project, when the more urgent question – given genuinely scarce capital – is “does this portfolio of projects, taken as a whole, still represent the best use of the money we have left.” The first question can be answered without a programme function. The second cannot.
There is a related effect, less often discussed. Organisations that expanded change capability rapidly during 1998 and 1999 – responding to Year 2000 remediation, to the early wave of e-commerce investment, to internal systems consolidation – built that capability almost entirely at project level. Programme offices, where they existed, were frequently thin: a reporting function, a status-aggregation exercise, rarely a genuine governance body with authority to reprioritise or terminate. When the correction arrived and cost pressure demanded cuts, it was these thin, poorly embedded programme functions that were cut first, precisely because their value had never been demonstrated in terms the organisation recognised. The project layer, by contrast, was protected, because projects have visible deliverables and named sponsors who defend their own budget lines. The vacuum, in other words, did not appear despite the collapse. In a number of cases it was created by the collapse, as the thin programme layer was the first casualty of cost reduction.
The programme layer is often the first casualty of cost-cutting precisely because it was the last capability built and the least understood by the executives approving the cuts.
The Structural Forces That Sustain It
If the vacuum were simply a matter of organisations not yet having read the MSP guidance, it would be a temporary and rapidly correctable state. I do not believe that is what we are looking at. The vacuum persists because several structural forces converge to sustain it, and each deserves separate examination.
Funding mechanisms built for projects
Capital approval processes in most organisations are built around discrete business cases with discrete owners. A project requests funding, demonstrates a return, and is approved or rejected on that basis. This process has no natural mechanism for asking whether a proposed project duplicates, conflicts with, or should be sequenced against another project already underway, because the approval body sees business cases one at a time, often months apart, frequently through different sponsoring divisions. A programme function exists precisely to sit across this fragmented view – but if the funding process itself is not redesigned to route requests through that function, the programme office becomes an observer of decisions rather than a participant in them.
Professional identity and career structure
Project management has, by 2001, a reasonably well-established professional identity. The Project Management Institute’s body of knowledge provides a common vocabulary; certification exists; career paths run from coordinator to project manager to senior project manager in a legible progression. Programme management has none of this maturity yet. There is no widely recognised certification distinct from project management credentials. Job titles are inconsistent – the same role might be called programme director, portfolio manager, or simply “head of change” in different organisations. Without a legible professional identity, it is difficult for an individual to build a career as a programme manager, difficult for an organisation to recruit confidently against the role, and difficult for a board to know what competence to expect from the person they have appointed. The discipline cannot embed structurally while its practitioners have nowhere professionally to stand.
The comfort of measurable delivery
There is a psychological dimension worth naming honestly. Project management offers a comfort that programme management does not: a project either delivers on time and to specification, or it does not, and that fact is knowable within a defined and usually fairly short horizon. Programme management deals in benefits that may not be realised for years, in strategic alignment that is inherently more contestable, in the discipline of saying no to individually defensible projects for the sake of a collective good that is harder to point to. Executives under pressure – and pressure has been the dominant condition of 2000 and 2001 – gravitate toward what is measurable and toward what can be defended in a single sentence to a nervous board. “The project delivered on time” is such a sentence. “We killed a project because it no longer served the blueprint” is a much harder sentence to say with confidence, and a much easier one to be second-guessed on.
Governance that mistakes aggregation for integration
Where programme structures do exist, they are frequently mis-designed – not absent but hollow. The commonest failure mode I have observed is the programme office that aggregates status reports from constituent projects into a single dashboard for the steering board, and calls this programme management. It is not. Aggregation tells the board what is happening. Integration – the genuine article – requires the authority to change what is happening: to re-sequence, to reallocate resource across project boundaries, to retire a project whose benefit case has been overtaken by events. A great many organisations have built the former and believe they have built the latter, and the distinction only becomes visible at the moment a hard decision is required and no one can be found with the mandate to make it.
| Function | Project Layer | Genuine Programme Layer |
|---|---|---|
| Primary question | Is this project on time, on budget, to scope? | Does this portfolio still serve the strategic outcome? |
| Authority | Within project boundary | Across project boundaries, including to stop or re-sequence |
| Time horizon | Duration of the project | Duration of the benefit realisation period |
| Failure mode observed | Scope creep, schedule slip | Silent duplication, benefit drift, no one able to say no |
What the Persistence Tells Us
It would be too easy to end this essay with a call for organisations to “implement MSP properly” and leave the matter there. The guidance exists; the argument for its value is not, in my experience, seriously disputed by anyone who has sat through a steering board meeting where three project managers each present green status while the strategic case for the combined spend has quietly evaporated. The interesting question is not whether programme management is worth doing. It is why a profession that broadly agrees on its value has been so slow to build the structures that would make it real.
I think the honest answer is that change delivery, as a profession, is still young, and younger still at the programme level than at the project level. Project management has had the benefit of decades of engineering and construction discipline behind it, transplanted into information technology and business change with reasonable success. Programme management as a distinct discipline is barely two years old in its codified form, and organisations are being asked to build governance muscle, funding discipline, and career structures for it at precisely the moment – the aftermath of a financial shock – when appetite for building new organisational capability is at its lowest.
“A programme is not a bigger project; it is a different kind of governance altogether, and organisations that treat it as mere scale keep discovering the difference the hard way.”
There is also, I think, a more uncomfortable truth about accountability. The programme vacuum survives in many organisations because it is, for certain people, convenient. A steering board that never has to make a hard sequencing decision between two sponsors’ pet projects is a steering board that avoids a difficult political conversation. An executive who can point to a project delivered on time, on budget, is protected regardless of whether that project ever produced the benefit it was funded to produce, because no one is tracking the benefit once the project closes. The vacuum is not merely a capability gap. In places, it is a structure that certain interests are content to leave unfilled.
What Filling the Vacuum Actually Requires
If the diagnosis above is right, then the remedy is not simply publishing an MSP-aligned process document and appointing someone with the words “programme manager” in their title. It requires structural change that touches funding, career paths, and the willingness of a board to be told no.
- Route capital approval through a single portfolio view, so that overlapping or conflicting business cases are visible before approval, not after implementation
- Give the programme function genuine authority to stop or re-sequence constituent projects, and test that authority early, on a case that matters, so its credibility is established rather than assumed
- Build a benefits realisation tracking mechanism that survives project closure, with ownership that does not evaporate when the project team disbands
- Invest in the professional development of programme managers as a distinct discipline from project management, even while the market for that discipline remains immature and its certification landscape unsettled
- Accept, at board level, that a well-functioning programme layer will sometimes say no to individually attractive projects, and resist the temptation to weaken that authority the first time it becomes politically inconvenient
None of this is quick, and none of it survives a single budget cycle if treated as a project itself rather than as a change to how the organisation is governed. That, perhaps, is the deepest irony the vacuum reveals: building the programme management capability that would prevent projects running without strategic oversight is itself a change effort that is highly susceptible to being run as an isolated project, measured on its own narrow terms, disconnected from the wider question of whether the organisation’s capacity for change is actually improving.
A Closing Observation
I am conscious that an essay diagnosing a structural gap risks sounding like a case for more process, more governance, more layers between decision and delivery – precisely the kind of bureaucratic weight that organisations under cost pressure are, rightly, suspicious of. That is not my argument. The programme layer, properly built, should reduce waste, not add to it: it exists to stop money being spent on projects that no longer serve their purpose, and to catch the duplication and drift that a project-only view cannot see. The vacuum persists not because organisations have rejected this logic, but because building the layer that would realise it asks something harder than approving a business case. It asks an organisation to change how it makes decisions, not merely what decisions it makes. Two years after the guidance was written, most organisations I have observed are still project-shaped, and the events of the past eighteen months, far from correcting that, have in several cases made it worse. Whether that changes will depend less on the quality of the methodology available – which is already adequate – than on whether boards are willing to build, fund, and defend an authority that will occasionally tell them no.