M&A & re-org: the operating model that survives the integration

A target operating model built as a slide deck doesn’t survive the integration — because it’s a one-off project that has to be maintained by hand. The way out is a versioned model that ProcessForge pulls from the real as-is of both sides and that grows with every re-org step — re-pulled in days instead of re-commissioned in quarters.

A merger or re-org almost always starts the same way: consultants and the internal team spend weeks building a target operating model — roles, responsibilities, processes, interfaces. Clean, complete, signed off. Then the integration begins, and on the very first day the model is already not quite right. Two re-orgs later it describes a state that never actually existed.

The target model is outdated before the integration runs

This isn’t a planning failure. An operating model from a workshop is a one-off project: built once, maintained by hand from then on. But during an integration something changes every day — a department is merged, an interface is cut differently, a role is reassigned. Each of those moves creates maintenance debt on the deck, and against the day-to-day of the integration, maintenance almost always loses.

A target operating model that has to be kept current by hand describes most accurately the day no one had time to update it anymore.

How do I build an operating model that survives the integration?

Forge flips this around. Instead of painting a target picture and hoping the organization follows it, the process engine builds a versioned model from the real as-is of both sides — process docs, workshop material, internal systems, Miro. From that come the transitions an integration actually needs:

• As-is → scenario A/B → target: Several transition scenarios from the same context, comparable side by side, instead of a single target slide.
• Versions, not a one-off: Each re-org step becomes a new state — what applied when stays traceable, without archive archaeology.
• Comparisons that show what changed — not just that something changed. Exactly what the steering committee and auditors ask during an integration.

The model grows with the integration

This shifts what the asset is. Not the one perfect day-one deck — but the ability to pull the current state at any time, from the living context of both houses. The model stops being a document that doesn’t survive the integration and becomes a living artifact that runs alongside it: re-pulled in days instead of re-commissioned in quarters. Transformation never stops — and the model keeps up.