Process Compliance as Delivery Substitute — Why Doing the Process Is Not the Same as Doing the Work
The programme was fully compliant with every mandated process, and it delivered nothing of value — these two facts were not considered contradictory by anyone in the governance chain.
The Compliance Illusion
There is a particular kind of programme failure that does not look like failure at all — at least not from the outside. The highlight reports are green. The stage gate reviews are passed. The management products are complete, filed, and cross-referenced. The risk register is maintained, the issue log is current, and the lessons learned are dutifully recorded at the end of each tranche.
And yet, months or years later, the organisation finds that nothing has materially changed. The business case benefits have not been realised. The operational teams are no better equipped. The customers — if anyone remembers to ask them — have noticed no difference. The programme delivered its process outputs with commendable discipline and its actual outcomes with none.
This is not an edge case. In my experience, it is the central failure mode of programme delivery in the current environment. And it persists not because people are incompetent or negligent, but because the structures we have built actively reward the wrong things.
The Architecture of Misdirection
To understand how process compliance became a substitute for delivery, it helps to trace the sequence of decisions that created the current environment.
The starting point was reasonable. In the late 1990s and early 2000s, too many programmes were run with no discernible method at all. Budgets overran, scope drifted, and nobody could explain why because nobody had documented anything. The response — the adoption of structured methods like PRINCE2, the introduction of formal governance frameworks, the creation of PMOs tasked with enforcing standards — was a rational correction.
The problem was that the correction overshot. What began as a sensible insistence on rigour became an elaborate bureaucracy of compliance. And the bureaucracy, once established, developed its own logic, its own incentives, and its own definition of success.
The moment an organisation defines programme success as the completion of management products rather than the achievement of business outcomes, it has built a machine that will reliably produce the former and neglect the latter.
Consider the incentive structure that now operates in most large programme environments. A programme manager is assessed, formally and informally, on whether the mandated processes have been followed. Are the highlight reports submitted on time? Are the stage gates properly constituted? Are the risk and issue logs maintained to the prescribed standard? These are the questions that governance bodies ask, because they are the questions that can be answered with a yes or no.
The harder questions — is this programme actually going to deliver its intended benefits? Are we solving the right problem? Has the operating context changed enough to invalidate our original assumptions? — are asked less often, because the answers are uncomfortable, ambiguous, and resistant to RAG status.
The Process as Performance
What has emerged is something that might be called process as performance: the enactment of method as a visible demonstration that the programme is under control, regardless of whether it actually is.
The pattern is recognisable to anyone who has spent time inside a large programme. A highlight report is not written to communicate the genuine state of the work; it is written to satisfy the reporting template. A risk register is not maintained to support decision-making; it is maintained because the PMO will flag its absence. A lessons-learned exercise is not conducted to improve future delivery; it is conducted because the method says there should be one at this point in the lifecycle.
None of this is dishonest, exactly. The people involved believe they are doing their jobs properly. They are following the method. The method says to produce these things at these points. They produce them. The tragedy is that the connection between these ritual outputs and the actual health of the programme has become so attenuated that neither the producers nor the consumers of these artefacts can tell the difference between a programme that is genuinely on track and one that is merely well-documented.
Three Structural Forces
Three forces sustain this pattern, and they operate largely below the level of conscious decision-making.
The first is the accountability gap. In most governance structures, accountability for process compliance sits with the programme manager, but accountability for benefit realisation sits with a business owner who is often only loosely connected to the programme’s day-to-day reality. This split means that the person who can be held accountable — the programme manager — is held accountable for the wrong things, while the person who should be accountable for outcomes — the business owner — is rarely held to account at all.
The second is the measurement problem. Process compliance is binary and immediate: either the highlight report was submitted on time or it was not. Outcome delivery is gradual, contested, and often only measurable long after the programme has closed. Governance structures gravitate toward what they can measure, and what they can measure is compliance.
The third is institutional risk aversion. Challenging a programme’s process compliance is safe — it is a procedural observation. Challenging whether the programme should continue at all is dangerous — it threatens budgets, careers, and political capital. The governance framework, in practice, enables the former and discourages the latter.
The PMO as Compliance Engine
The Programme Management Office — in its current incarnation — is both a symptom and a cause of this dynamic. Most PMOs define their value in terms of standards enforcement: template adherence, reporting cadence, methodology compliance. This is understandable; it is measurable, defensible, and keeps people busy.
But it produces a perverse outcome. The PMO becomes the organisation’s most visible mechanism of programme oversight, and its entire apparatus is oriented toward process rather than outcomes. When a programme board asks the PMO for an assessment of programme health, what it receives is an assessment of process compliance — and the two are silently treated as equivalent.
The PMOs that have resisted this drift — the ones that focus their energy on asking whether the programme is actually going to deliver what the organisation needs — are conspicuously rare. They exist, but they tend to be led by individuals who have enough credibility and political capital to push back against the compliance orthodoxy. They are the exception, not the model.
What the Method Actually Says
The irony is that the methods themselves do not advocate for this kind of compliance-first thinking. PRINCE2’s continued business justification principle is, at its core, an instruction to keep asking whether the programme is still worth doing. MSP’s benefit realisation management framework is an explicit attempt to keep outcomes at the centre of programme governance.
But methods are interpreted by organisations, and organisations interpret them through the lens of their existing culture and incentive structures. An organisation that is risk-averse, hierarchical, and uncomfortable with ambiguity will read PRINCE2 as a compliance framework, because that is what it needs it to be. The method’s more challenging demands — tailor to context, challenge the business case, escalate honestly — are the first things to be quietly dropped.
The method is not the problem. The problem is that organisations adopt the parts of the method that reinforce their existing behaviours and discard the parts that would challenge them.
The Cost of the Substitution
The cost of treating process compliance as a proxy for delivery is not abstract. It is measured in programmes that run for years past their useful life because no governance mechanism exists to stop them — only to check whether their documentation is in order. It is measured in benefits that are claimed on paper but never materialise in the operating business. It is measured in the progressive erosion of credibility that programme management suffers as a discipline, because the programmes it governs so carefully keep failing to deliver.
Most corrosively, it is measured in the disengagement of the people who do the actual work. Delivery teams — the developers, the business analysts, the change managers — learn very quickly that the organisation cares more about whether their timesheets are filed correctly than whether their work is making a difference. The effect on morale, and on the quality of the work itself, is predictable and severe.
Recovering the Connection
Reconnecting process to purpose is not a methodological problem; it is a cultural one. It requires governance bodies to ask different questions — not is this programme compliant? but is this programme delivering? It requires PMOs to redefine their role from compliance enforcement to outcome assurance. It requires programme managers to accept that a well-documented failure is still a failure.
Most of all, it requires organisations to tolerate the discomfort that comes with honest assessment. A highlight report that says this programme is in serious trouble and here is why is infinitely more valuable than one that says all deliverables are on track when they are not. But producing that honest report — and receiving it without punishing the messenger — demands a maturity that most programme governance structures have not yet developed.
The process was supposed to be the servant of the outcome. Somewhere along the way, the relationship inverted. Reversing that inversion is the single most important challenge facing programme delivery today.