An office that can track a blocked decision and cannot make it will report the same blocker every month.
Why it matters when the plan changes
Large programmes need somewhere that holds the whole picture, and no line function does. The office supplies that: the dependencies between workstreams, the sequencing, and where the plan is exposed. Its limit is structural. It can see that a decision between two functions is blocking a workstream, and it cannot settle the decision, because neither function reports to it. Research on strategy execution found that only nine percent of managers can rely on colleagues in other functions and units all the time, the reliability an office is asked to manufacture without authority over either side.
The tension is between coordination and authority. Giving the office real decision rights over line matters makes it effective and creates a parallel hierarchy the line resents. Leaving it purely coordinating makes it a reporting layer with a good view and no levers. Most organisations choose the second by default, without deciding to, and then treat recurring escalations as a reporting problem rather than as evidence that specific decisions have no owner.
In practice
A transformation office reports the same three blockers for four consecutive months. Each one is a decision between two functions. The office has escalated each time and has no authority to resolve any of them, and the steering committee treats the recurrence as a reporting problem rather than as evidence that nobody owns those three decisions.
Evidence
Cross-unit commitments are the least reliable part of execution, and they are what a coordinating office is asked to manage without authority over either side.
Donald Sull, Rebecca Homkes and Charles Sull, Why Strategy Execution Unravels and What to Do About It, Harvard Business Review (2015)A programme office is an established structure for coordinating projects centrally.
Project management office, Wikipedia (2026)
What it cannot tell you
A transformation office cannot tell you whether a blocked decision has an owner. It tracks and reports dependencies but has no visibility into why a decision sits unresolved, whether it lacks a mandate, evidence or a person willing to take it. A clean status report is compatible with a programme that is stalled everywhere that matters.
Questions
Hold the whole picture that no line function holds: the dependencies between workstreams, the sequence, and where the plan is exposed. Its most valuable output is naming the decisions that are blocking progress and who would have to make them, rather than tracking task completion.
Because escalating a decision does not assign it to anyone. Harvard Business Review's 2015 research on strategy execution found only nine percent of managers can rely on colleagues in other functions and units all the time, which is why the same blocker often reappears rather than getting resolved.
Enough to settle sequencing and dependency conflicts within the programme, which is where it has the best information. Giving it authority over line decisions creates a parallel hierarchy. The workable middle is a named executive owner for each decision class the office cannot settle.
When its output is status rather than decisions. The project management office entry on Wikipedia, dated 2026, describes it as a structure for coordinating projects centrally, not for deciding on their behalf. A report that repeats what a steering committee already knows, without naming what must be decided and by whom, produces record rather than progress.
Until the coordination it provides is being done by the line itself, which is a condition rather than a date in a plan. Offices that outlive that point become a permanent layer, and the organisation gradually loses the ability to coordinate anything without one.