How an IMO differs from a PMO
A corporate PMO exists to run projects to a standard. An IMO exists to deliver a deal thesis against a clock, which changes its character in two ways. First, decision velocity matters more than process compliance: the IMO's job is to get the right question in front of the right person this week, not to perfect the template. Second, it is accountable to a number. Somewhere in the deal model is a synergy figure and an integration cost envelope, and the IMO is the function that knows, at any moment, whether both are on track.
When you need one
The honest threshold is lower than most organisations assume. If the integration has more than two or three workstreams with dependencies between them, or a synergy number the board will ask about, something has to play the IMO role, even if it is one person with a plan and a weekly meeting. What scales with deal size is the weight of the function, not its existence. A £20m bolt-on needs a lean version of exactly the same machinery a £500m deal needs.
What the IMO actually runs
The plan of record. One integration plan, owned by the IMO, updated weekly by workstream leads.
The moment two versions of the plan exist, the IMO has already failed.
The cadence. In the first two weeks after close, a short daily stand-up, because problems in that window compound by the day. Then a weekly integration meeting per workstream and a weekly cross-workstream IMO meeting, focused on movement and dependencies rather than status recitals. A monthly steering committee against a one-page dashboard. Phase-gate reviews at Day 30, 60 and 100 where the plan is formally allowed to change.
Risks and issues with escalation rules. Not a register that grows, a register that triggers. Each risk carries a threshold at which it escalates to the SteerCo, agreed in advance, so escalation is mechanical rather than political.
The dependency map. Cross-workstream dependencies are the IMO's most valuable single artefact, because no workstream can see them alone. Most integration surprises are a dependency someone knew about and nobody connected.
The decision log. Integrations generate decisions at a rate normal governance cannot absorb, and six months later nobody agrees on what was decided. A dated log of decisions, decision-makers and rationale is dull and it settles arguments permanently.
Synergy tracking with finance sign-off. The IMO tracks initiative progress; finance certifies the value hitting the P&L. Both in one place, reviewed together, so the SteerCo never hears two versions of the same number.
Staffing it leanly
An integration lead who has operating credibility with both organisations, plus workstream leads who remain in their day jobs and give the integration a defined slice of their week. The trap is staffing the IMO with people who can only observe: the role needs people who can walk into a workstream, see that a milestone is fiction, and say so. On smaller deals the IMO is genuinely one person; what cannot be compressed is the cadence and the artefacts, only the headcount.
The anti-patterns
Three recur. The reporting factory, where the IMO's output is decks about the integration rather than movement in it, and workstream leads spend Fridays feeding it. The doing-IMO, which starts executing workstream tasks itself, at which point workstream accountability quietly dies. And the immortal IMO, still holding meetings in month nine because nobody defined what finished looks like.
Standing it down
The IMO should have an end state agreed at the start: typically around Day 100 or shortly after, when deal-critical milestones are delivered or consciously re-planned, synergies are tracked in the business's own forecasting rather than a side file, remaining risks live in business-as-usual registers, and open actions have owners in the line. Standing down is a formal act with a lessons-learned review attached, because the review is the one artefact that makes the next acquisition cheaper.
The templates that implement this
The toolkit's 100-Day Integration Plan, Day 1 Readiness Checklist, Risk Log and Board Dashboard follow the structure described here, pre-populated with a worked example. One-time purchase from £199.
See what is inside ›Related guides: building the 100-day plan and the Day One readiness checklist.