Transformation PMOs and the 18-month problem.
Why most ERP, M&A, and digital-transformation portfolios miss their year-two milestones — and the operating-model changes that fix it.
PulsePMO IQ · Solution brief for transformation & change PMOs
The pattern
Transformation programs — ERP replacements, post-merger integrations, digital-operating-model rebuilds — tend to hit their first six months roughly on plan. The gap opens in the second year, once the initial wave of workstreams starts interacting: a data-migration delay on one workstream quietly pushes a go-live date on another, a shared integration vendor gets stretched thinner than any single workstream lead can see, and scope that was deferred early to hit a milestone resurfaces as a much more expensive fix later.
None of this is a failure of any one workstream. It is a failure of the portfolio-level visibility that would have made the interaction visible before it became a missed milestone.
Four points of failure
Cross-workstream dependencies tracked only within each workstream.
A dependency that spans two workstreams is invisible to whichever one didn't log it, so it surfaces as a surprise on the workstream that inherits the delay.
Shared vendors booked without a portfolio-level view of their total commitment.
The same systems integrator or data-migration partner is frequently over-committed across workstreams that each believe they have dedicated capacity.
Deferred scope with no visible re-entry point.
Scope cut to hit an early milestone often needs to come back later — if it isn't tracked as a live, scored item, it re-enters the plan as an unplanned addition rather than a known, budgeted one.
Governance built for the kickoff, not for month fourteen.
Steering committees convened weekly in month one often meet monthly by month twelve, at exactly the point where cross-workstream risk is highest and needs more attention, not less.
Programs that hold their year-two milestones typically share one structural trait: dependencies and vendor commitments are tracked at the portfolio level from day one, not stitched together workstream-by-workstream once something has already slipped.
How PulsePMO IQ addresses this
| Failure point | What changes |
|---|---|
| Hidden cross-workstream dependencies | A RAID register linked to the specific activities it affects, rolled up at the portfolio level — a dependency logged on one workstream is visible on every workstream it touches. |
| Vendor over-commitment | Procurement linked to project work, so a vendor's total commitment across every active workstream is visible in one place, not reconstructed from separate contracts. |
| Deferred scope disappearing | Demand intake and scoring apply to re-entering scope the same way they apply to new requests — deferred work stays visible and staged, not forgotten. |
| Governance cadence that fades | A live command center means the steering committee is reviewing current portfolio posture every time it meets, not a status deck assembled the week before — which keeps the meeting worth holding at month fourteen as much as month one. |
Where to start
For a program already underway, the highest-value first step is consolidating every active workstream's dependencies and vendor commitments into one view before changing any governance process — that alone typically surfaces the interactions that would otherwise show up as a missed milestone. Governance cadence and re-scoring of deferred work follow once that baseline is trustworthy.
Command center, demand pipeline, and the decision queue — in the product tour.
This brief describes general capability fit and illustrative scenarios; it is not specific to any named customer.