Transformation strategy rarely fails in the room where it's approved. The operating model looks sound, the business case checks out, and the roadmap gets sign-off. It fails three or six months later, in the handoff from the team that designed it to whoever is supposed to run it.
The handoff is the failure point
Most organizations separate strategy from delivery by design — a strategy team or external advisor produces the target model and roadmap, then hands it to a program or operations team to implement. Each handoff is a point where intent can be lost: priorities get reinterpreted, governance gets simplified under delivery pressure, and the people accountable for results weren't in the room when the trade-offs were made.
This isn't a people problem. It's a structural one. A team that didn't design the target operating model has to reconstruct its logic before it can defend decisions under pressure — and transformation programs are, by definition, under pressure from month one.
What a PMO can and can't fix
A well-run PMO can catch risk early, keep governance disciplined, and maintain a single view of portfolio health. What it typically cannot do is recover intent that was lost in a handoff it wasn't part of. This is why PMO effectiveness correlates less with the PMO's own maturity than with how early it was involved — ideally, during Design, not after.
The fix isn't more governance. It's less handoff.
The organizations that execute transformation reliably tend to share one structural trait: continuity between the team that designs the operating model and the team that runs the PMO delivering it. That doesn't require one firm to do everything — it requires the accountability to not change at the point where accountability matters most. SUSTnex is structured around that principle deliberately: the same team stays in the room from diagnosis through delivery, specifically to remove that failure point.