Most digital transformations are not killed by bad technology. They are killed by conversations that did not happen and decisions that sat on someone’s desk until they became unmanageable.
BCG’s 2020 study of 825 senior executives found that 70 per cent of digital transformations fall short of their objectives, with only 30 per cent in its “win zone” (If Failure Is Not an Option, Why Is Success So Rare?). McKinsey’s own survey found that just 16 per cent of organisations both improved performance and sustained the change (Unlocking success in digital transformations). The pattern repeats across both studies: the technology rarely breaks the programme. The leadership and governance around it does.
A PMO operating inside a transformation works a contested space. The business wants to move faster than governance allows, technology teams hold constraints that executives would rather not hear, and competing interests across the organisation sit in genuine, structural tension with each other.
A PMO that understands this role becomes one of the most valuable functions in the transformation. A PMO that misreads it adds to the friction it was built to manage.
Three tensions, not three personality clashes
Speed sits against governance. Every programme carries pressure to deliver, and delivery needs decisions; governance exists to give those decisions the right information, sign-off and an accountability trail. The two pull against each other permanently: the same structure that blocks a bad decision slows down a good one too. A PMO’s task is to tell the two apart, building a framework that routes low-risk calls fast and sends high-stakes, irreversible ones through full governance.
IT sits against the business. Technology teams know what a system can and cannot do; business leaders know what the organisation needs to achieve. Left unmanaged, the divide gets settled by whichever group has more momentum that week, which has nothing to do with which group holds the right answer.
Central control sits against local agility. Large transformations need coherence; individual business units need room to respond to their own operating realities. Centralise everything and the programme slows to a crawl, disconnected from delivery. Localise everything and it loses the consistency that makes it one programme rather than twelve.
Where the PMO earns its place
The PMO’s most valuable function in a transformation is translation. It turns a technology team’s constraint language into business decision language, so executives choose rather than absorb data. It turns programme strategy into the operational detail a delivery team needs. It turns tension between competing leadership factions into a structured choice, with a named owner and a deadline, so friction becomes a decision rather than a stalemate.
Simard and Aubry’s six-year study of a PMO inside a Canadian bank’s digital transformation, published in Project Management Journal in 2025, traced exactly this kind of shifting role (The Project Management Office’s Active Participation in a Digital Transformation: A Trajectory Full of Twists and Turns). Its path moved through five phases, lost strategic standing at points, rebuilt it through governance layers it had built, and never settled into a fixed, administrative shape. A role this adaptive does not fit an operating model built for a stable programme.
When the PMO loses the room
There’s a recognisable failure pattern. Decisions start happening outside the steering committee. Status reports read clean while everyone in the room knows the programme is not. The real conversations about programme health move into corridors and side calls instead of the forums built for them.
By the time that pattern sets in, the PMO is the last function to know what is actually happening inside the programme it is meant to govern, and the tensions that should have surfaced months earlier have compounded into something the organisation now has to fight rather than manage.
Build the PMO that changes the outcome
A transformation needs a PMO that creates the conditions for leaders to make the decision they have been avoiding. Structured forums with the right people and the right information. Escalation routes that do not need a crisis to trigger them. Reporting that reflects programme health honestly rather than managing the politics of the steering committee. And leadership with enough standing to say that the current trajectory will not deliver what the programme set out to achieve.
Most transformations already contain the information needed to course-correct before it is too late. Whether the PMO sees it, names it and gets leadership to act on it depends on how seriously the organisation treats the function in the first place.