Why the Crisis Killed Some PMOs and Made Others Essential — The Accidental Experiment in Programme Office Value
The PMOs that survived were not the ones that produced the best status reports — they were the ones whose leaders had made themselves indispensable to the decisions that actually mattered.
Executive Summary
The financial crisis of 2008–2009 produced an unintended experiment across the programme management profession. When organisations faced sudden, severe budget cuts, the Programme Management Office was frequently among the first functions scrutinised. What happened next was revealing: some PMOs were shut down with barely a protest, while others became more central to organisational decision-making than they had ever been. The difference was not size, seniority, or methodology. It was whether the PMO had built its existence around activities the organisation genuinely could not do without — or around activities that, under pressure, turned out to be optional.
This essay examines the patterns that distinguished the PMOs that survived and grew from those that were eliminated, and what those patterns reveal about a persistent confusion in the profession between the apparatus of programme management and its actual purpose.
The Cull
The speed with which some PMOs were dismantled during late 2008 and early 2009 was startling, even to those of us who have long argued that many programme offices were vulnerable to exactly this kind of challenge.
The pattern was consistent. When the instruction came down to reduce overhead by twenty or thirty per cent, the PMO appeared on the cut list alongside other functions classified as support or governance. In the worst cases, the decision was made in a single meeting: the PMO’s annual cost was identified, its output was characterised as reporting and process oversight, and the question was asked — if we stopped doing this tomorrow, what would actually break?
The honest answer, in too many organisations, was: not much. Projects would lose their weekly status report. Governance meetings would lose their secretariat. The programme plan would stop being updated in the central tool. RAG statuses would no longer be consolidated. And the programme board would have to find another way to get its information.
None of these were outcomes that anyone wanted. But in a crisis defined by the need to preserve cash and protect front-line delivery capability, they were outcomes the organisation could live with. The PMO’s work was real, but it was not essential. And that distinction, which had never needed to be tested before, proved fatal.
The Survival Pattern
The PMOs that not only survived the crisis but emerged from it with greater authority and resource shared a set of characteristics that, in retrospect, define a fundamentally different operating model from the one the profession has conventionally promoted.
They Owned the Portfolio View
The single most important differentiator was whether the PMO had positioned itself as the organisation’s primary source of portfolio intelligence. Not project status reporting — portfolio intelligence: the integrated, cross-programme view of where money was being spent, what was being delivered, what the dependencies were, and what the consequences of stopping or deferring any given initiative would be.
When the crisis hit and senior leaders needed to make rapid portfolio triage decisions, the organisations that had this capability in their PMO found that the PMO became indispensable overnight. It was the only function that could answer the questions the executive committee was asking: How much are we committed to spending in the next quarter? Which programmes can be paused without contractual penalty? If we stop Programme X, what happens to Programmes Y and Z?
The PMOs that had spent years building comprehensive, current portfolio data discovered that they had been accumulating the one asset the crisis made priceless: the ability to give senior leaders a credible basis for fast, high-stakes decisions.
The PMOs that had focused their data collection on project-level status reporting — the RAG statuses, the milestone trackers, the risk registers — could not answer these questions. Their data was granular but not integrated. They could tell you the status of each individual project but not the shape of the portfolio, the real cost of continuation, or the consequences of cancellation. They were producing information, but not the information that mattered when it mattered most.
They Provided Decision Support, Not Governance Oversight
The second characteristic was a distinction that sounds semantic but proved operationally decisive: the surviving PMOs had oriented themselves around decision support rather than governance compliance.
Governance compliance means ensuring that the right processes are followed: business cases are written, gate reviews are conducted, risks are logged, status reports are produced on time. It is necessary work, but it is process work — work that ensures the governance machine runs correctly. The PMO that defines itself primarily through governance compliance becomes, in effect, a process police function. It adds rigour, but its contribution is measured in adherence to standards rather than in the quality of the decisions those standards are meant to support.
Decision support is different. It means actively helping senior leaders make better decisions — by providing the analysis they need, by framing the options clearly, by identifying the implications and trade-offs that the raw data does not reveal, and by bringing a cross-programme perspective that no individual programme director can hold. The PMO oriented around decision support is not checking whether the process was followed. It is asking whether the right question is being asked and whether the available information is sufficient to answer it.
- Governance-oriented PMOs measured their value in process adherence: percentage of projects with current status reports, percentage of gate reviews conducted on schedule, compliance with the project management methodology
- Decision-support PMOs measured their value in the quality of the decisions they enabled: were the portfolio trade-offs clearly presented, did the executive committee have what it needed to decide, were the dependencies and second-order effects identified before they became problems
- In stable conditions, both models appeared to work. The crisis revealed that only one of them was doing anything the organisation could not do without
They Had Credibility with Senior Leaders
The third characteristic was personal rather than structural, but no less important: the PMOs that survived were led by individuals who had established genuine credibility with the executive team. Not the credibility that comes from running a smooth process, but the credibility that comes from consistently providing insight that senior leaders found useful and that they could not get elsewhere.
This credibility was built over years, through a pattern of behaviour that distinguished the best PMO leaders from the profession’s mainstream: they spoke the language of the business, not the language of project management methodology. They brought analysis, not just data. They were willing to deliver uncomfortable messages — to tell the executive committee that a programme was in trouble before the programme director admitted it, to challenge the optimism bias in a business case, to point out that the portfolio contained more work than the organisation had capacity to deliver.
“The PMO leaders who had spent years telling senior executives what they needed to hear — rather than what the process required them to report — found that when the crisis arrived, those executives turned to them first.”
The PMO leaders who had confined themselves to process stewardship — who had never stepped outside the governance role to offer strategic counsel — discovered that they had no relationship to protect them when the cost reduction exercise began. They were known as administrators, and administrators are dispensable.
The Profession’s Uncomfortable Truth
The pattern of crisis-era PMO survival and elimination points to an uncomfortable truth about the programme management profession as a whole: a significant proportion of what the profession considers its core activity — the methodology, the process, the governance machinery — turned out to be less valuable than the profession believed.
This is not an argument against rigour. Process and governance serve real purposes in complex programme environments. But the crisis forced a distinction between the activities that serve the decision-making process and the activities that constitute the decision-making process. The PMOs that had confused the two — that had come to believe that running the governance process was the contribution — found themselves exposed.
The deeper problem is that the profession’s literature, its qualifications, and its career structures have reinforced this confusion. The body of knowledge emphasises methodology, tools, and process. The certifications test knowledge of these frameworks. Career progression in the PMO world is typically measured by the scale and complexity of the governance machinery one manages, not by the quality of the decisions one enables.
- The profession trains its practitioners to build and operate governance machinery
- It does not, with any consistency, train them to provide the kind of strategic decision support that makes a PMO genuinely indispensable
- The crisis revealed the cost of this gap: PMOs staffed with competent process managers who had never been equipped or empowered to operate as strategic advisers
What the Surviving PMOs Did That Can Be Learned
The characteristics of the PMOs that thrived through the crisis are not mysterious, but they do require a deliberate departure from the profession’s default operating model.
They invested in data before they were asked for it. The portfolio intelligence that proved invaluable during the crisis was not built in response to the crisis. It was built over years of patient, often unglamorous work: standardising cost-to-complete estimates, maintaining dependency maps, tracking contractual commitments, building integrated views that no single programme owned. The PMOs that tried to assemble this data after the crisis hit found that it was too late — the data did not exist, or existed in incompatible forms across dozens of programme teams.
They defined their role around the consumer of their output, not the producer. The question that distinguished the surviving PMOs was not what should a PMO produce? but what does the executive committee need in order to make good decisions about this portfolio? This is a subtle but fundamental reorientation. It shifts the PMO from an inward-facing function — concerned with its own processes and standards — to an outward-facing one, concerned with the effectiveness of the decisions it supports.
They hired and developed differently. The skill profile of the surviving PMOs was noticeably different from the profession’s norm. They employed fewer pure process specialists and more individuals with analytical capability, business acumen, and the interpersonal skills to operate as trusted advisers to senior leaders. The best PMO teams I observed during the crisis included former management consultants, business analysts, and individuals with deep operational experience in the sectors they served. They were programme management professionals, certainly, but they were also strategists, analysts, and communicators.
They earned their seat at the table before they needed it. The relationship between the PMO leader and the executive team cannot be built during a crisis. It must be established in calm conditions, through a consistent pattern of useful, honest, and insightful contribution. The PMO leaders who had this relationship found that the crisis amplified it. Those who had not built it found that the crisis eliminated any opportunity to do so.
The Rebuilding Question
As the immediate intensity of the crisis recedes, many organisations are now rebuilding their programme management capability. Some are reinstating PMOs that were cut. Others are building new ones from the ground up. The question they face is whether they will rebuild the model that failed or build something different.
The temptation to revert to the familiar is strong. The governance model is well understood, well documented, and easy to justify. It produces visible, measurable output. It satisfies audit requirements. It looks professional. And in stable conditions, it works well enough that its limitations are never tested.
But the crisis has provided evidence that should not be ignored. The PMOs that mattered — the ones that earned their continued existence through genuine contribution rather than institutional inertia — were the ones that had moved beyond governance into decision support, beyond reporting into portfolio intelligence, and beyond process stewardship into strategic counsel.
The profession has a choice. It can treat the crisis as an aberration — an unusual period of stress that does not reflect normal operating conditions and therefore carries no lessons for standard practice. Or it can recognise that the crisis simply accelerated a test that was always coming: the test of whether what the PMO does is genuinely essential, or merely habitual.
The organisations and the practitioners that take the second view will build PMOs that are harder to set up, harder to staff, and harder to measure — but also harder to kill. And that, in the end, is the only test that matters.