5 signs your PMO is already behind schedule
Most middle-market PMOs aren't under-resourced — they're under-designed. The team stands up a tracker, assigns workstream leads, and runs a kickoff. Then, somewhere around week six, the operating model starts to drift from the plan on the slide. The symptoms are rarely dramatic. No one workstream fails outright. Instead, small cracks appear — a status update that doesn't quite match what finance is seeing, a decision that sits unresolved for two weeks longer than it should — and by the time leadership notices, the PMO is already behind the pace the deal thesis assumed.
Below are the five most common early warning signs, in the order we typically see them appear.
1. No single source of truth for status
Finance has one version of synergy capture, ops has another, and the deal team is reconciling both in a side spreadsheet before every steering committee. Once status has more than one owner, it stops being status — it becomes a negotiation. Meetings that should take fifteen minutes turn into forty-five minutes of "whose numbers are right," and the actual decisions that need to get made get pushed to the next cadence.
2. Governance cadence was never actually defined
A steering committee exists on the org chart, but no one wrote down who has decision rights on scope changes, who breaks ties between functions, or what actually needs to be escalated versus resolved at the workstream level. Without that clarity, small decisions stall waiting for a meeting that's two weeks out, and workstream leads start making judgment calls that may or may not align with what sponsors actually intended.
3. Synergy tracking lives in a spreadsheet no one owns
Targets were set at deal close with real conviction. Six months in, the tracking file has three tabs, two versions in circulation, and no single accountable owner reconciling run-rate assumptions against what's actually landing on the P&L. The number everyone quotes in the board deck and the number actually being tracked week to week quietly stop matching.
4. Change management was bolted on, not designed in
Communications get drafted reactively, after a workstream has already surprised the frontline with a system cutover or reporting-line change. Adoption risk gets treated as a Day 90 problem instead of a Day 1 design constraint — and by the time anyone notices resistance building, it's already showing up in productivity or attrition, not just sentiment.
5. The PMO was built for the deal, not for what comes after
It stood up fast to hit close, ran hard through Day 100, then quietly disbanded — taking the tracking discipline, the governance rhythm, and the institutional memory of what was actually decided along with it. Six months later, someone asks why a synergy target hasn't moved, and no one left in the building can fully explain how it was supposed to get there.
None of these five signs shows up in isolation, and none of them shows up on day one. They tend to compound — a missing source of truth makes governance harder, undefined governance makes synergy tracking drift, and by the time change management becomes reactive, the PMO has usually already lost the thread on why it was stood up in the first place. Catching one or two of these early is usually enough to reset the whole model before it costs real ground on the deal thesis.
Stonehill builds operating models that outlast the deal team — PMOs and governance structures for PE-backed and founder-led middle-market companies, designed to run past Day 100, not just to it.
