ZBTOS by ETEGY
Ten questions · 5 minutesTransformation Lens Check →

PMO vs. Transformation Office

Who actually owns the outcome?

ForExecutive sponsorsPMO and transformation office leads
Leaders working through who owns a cross-functional outcome
The PMO.
Governs delivery.
The transformation office.
Governs operating change.
The outcome.
Needs a decision owner at every seam.
EXHIBIT 1 · TWO OFFICES, TWO JOBS
PMO
Scope, schedule and budget
Status by project
Risk and issue logs
Delivery method compliance
Transformation office
What the portfolio must change
Decision authority at each handoff
Evidence of operating change
Which initiatives trace to the strategy
Many enterprises have the first and call it the second.
Why it is no longer optional
Every workstream reports green. Who owns the outcome?

Delivery control keeps projects on schedule and budget. The outcome crosses every team, and the decision about whether it arrived sits at the handoffs, where no one is named.Only 30% of companies fully meet their timeline, budget and scope expectations in large-scale tech programs.BCG Platinion, Why 70% of Transformations Miss the Mark (2024 BCG study)

The distinction

Two offices, two jobs

A project management office keeps projects on scope, schedule and budget. It is good at that, and it was never scoped to decide what the change has to be. A transformation office exists for the second job: making sure the portfolio changes how the business runs, and holding the decisions that no single project owns.

The two are often one team with one name. That is workable, as long as both jobs are chartered. The common failure is a PMO renamed a transformation office, still measuring delivery while the outcome crosses every team without a decision owner.

A PMO governs delivery. A transformation office governs operating change.

The PMO tracks who owns the work. The transformation office decides whether it arrived.

What the PMO tracks
Who owns each workstream, and whether it hit its milestone. A RACI records it.
What the transformation office decides
Whether the outcome arrived where one team’s finished work became the next team’s intake. No RACI names that decision.
Day one

What your team can do after training.

Foundation teaches the method on the Meridian case, with each area applying it to its own work. Practitioner Intensive applies it to one live transformation.

01Foundation
Distinguish the two jobs.
Separate delivery control from operating-change authority, and the decisions each office should hold, on the Meridian case.
02Foundation
Find the unowned seams.
Identify the handoffs an outcome crosses and where no one holds the decision.
03Intensive
Name the decision owners.
On one live transformation, name who decides whether the outcome arrived at each seam.
04Intensive
Bring evidence to the steering committee.
For that transformation, report what changed in the operating model, and the evidence for it, alongside schedule and budget.
A new way to use the training
Put the PMO and the transformation office in the same cohort.

Both offices learn to read one case the same way, each applies it to its own part of the portfolio, and they split the work by job instead of competing for it.

Outcome: Know which decisions belong to which office before the next steering meeting. Learned through the Meridian case in Foundation; applied to one live transformation in the Practitioner Intensive.

The gap a PMO cannot see
Delivery methods manage the teams. Transformation fails between them.

A PMO sees each workstream. A transformation office has to see the seams, where one team’s output becomes another team’s intake.

Questions

Do we need both?

Usually. Delivery control and operating-change authority are different jobs. One office can hold both if it is chartered and staffed for both.

Why does the outcome end up with no owner?

Because it crosses teams. Each workstream owns its piece, and the decision about whether the outcome arrived sits at the handoffs, where no one is named.

Where does ZBTOS teach this?

The Practitioner Intensive sets decision authority at each handoff of one of your live transformations. The Foundation Course introduces the layer on a shared case.

Sponsor memo · one page
Put the ownership question in front of your sponsor.
Get the sponsor memo →Train the transformation office: Foundation Course ›

Not ready for a course? Get the ZBTOS Briefing › New reads for the people running the transformation office.

ZBTOS by ETEGY

Training, assessment and support for transformation capability.

Carrying an external mandate? ETEGY →
Zero-Based Transformation™, ZBTOS™, GSDPI™, Voice of the System™ and Traceability Ratio™ are trademarks of ETEGY. Get. Sort. Do. Prove. Improve.® is a registered trademark of ETEGY. Privacy · © 2026 ETEGY