How to Use This Playbook

This playbook is the operating manual for the Mission PMI™ Approach — a structured framework for leading, governing, managing, and executing complex mergers, acquisitions, carve-outs, divestitures, and transformation programmes. It is built for the senior integration leader who needs to move from signed deal to full value realisation with discipline, speed, and precision.

Harvard Business Review research indicates that between 70 and 90 per cent of M&A deals fail to deliver expected value. Bain reports that 60 per cent of all deals fail to meet internal expectations. PwC found that only 14 per cent of organisations reported comprehensive integration across strategic, operational, and financial dimensions. The same PwC research found that 88 per cent of successful M&A organisations fully integrated their IT function, compared to just 54 per cent of others. These are not planning failures. They are execution, leadership, and momentum failures — which is exactly what this playbook is designed to prevent.

Why Most Integrations Fail

Structure at a Glance

The MDEMT™ Leadership Philosophy

MDEMT™ is Mission Systems' proprietary PMI leadership operating philosophy. It is not a process checklist. It is a leadership discipline applied every day, at every level of the integration.

Before a single integration activity begins, the PMI Lead must convert the merger agreement into an executable integration control framework. No PMI plan should exist until every legal, commercial, and operational obligation has been extracted from the deal documents. Otherwise the integration team is flying blind.

The Deal Obligations Register is the single most important document in the integration. Every clause from every deal document is extracted and tracked here. This is the legal spine of the entire integration. No integration activity should be planned or executed without first understanding what the deal obligates the acquiring entity to do, avoid, preserve, or deliver.

Documents to Secure on Day 1

Once the DOR is built, translate every deal objective into a measurable integration objective assigned to a stream. The following categories must all be addressed:

The DOR is reviewed weekly by the PMI Lead, Legal Counsel, HR Lead, Finance Lead, and Commercial Lead. The Weekly Legal Control Meeting has a fixed agenda covering: new obligations identified, upcoming contractual deadlines in the next 30 days, potential breaches at AMBER or RED, regulatory approval status, employment law risks, IP transfer status, customer and supplier change of control clause status, TSA compliance, litigation exposure, and any decisions required from the Steering Committee.

Mobilisation must be fast, structured, and visible. The integration team, Steering Committee, and workstream leads must be established and operating within the first 10 working days. Every day without governance is a day where value leaks, momentum is lost, and confusion spreads.

Days 1–2: Establish Command Structure

Days 3–5: Confirm Integration Scope

Days 6–10: Build the Master Integration Plan

The Integration Lead is not a programme manager. The Integration Lead is a mission commander who fulfils six simultaneous leadership roles. Every interaction, every meeting, and every communication is an opportunity to perform one or more of these roles.

Build the PMI team within the first two weeks. Every open role has an interim owner until filled. When recruiting for PMI roles, prioritise people who are: comfortable with ambiguity, ruthless on follow-up, politically sharp but not political, calm under pressure, strong on documentation, able to challenge executives respectfully, commercially literate, and fast with plans, dashboards, and RAID registers. Avoid template PMOs who produce polished status reports while the integration burns.

A minimum of twelve workstreams should be established for any significant integration. Each workstream must have: a Sponsor, a Lead, a defined Scope, Deliverables, Milestones, Risks, Issues, Dependencies, a Budget, named Resources, a Weekly Status report, and a list of Decisions Required.

The integration plan is not a Gantt chart. It is a living decision-making framework built on ISOPOSED™ diagnostics and governed by the TORSEMI™ execution cadence. Before any plan is built, every stream applies ISOPOSED™ to validate its mission, confirm what it is solving, and align with the deal's value thesis.

Every stream produces a Scope Statement by end of Week 2. This is the MDEMT™ Execution discipline applied at the planning stage: everyone knows WHAT their stream is doing, WHY, WHEN it must be done, and WHAT success looks like.

Technology integration is one of the most common causes of PMI delay and value leakage. The Technology and Data workstream must follow a four-phase approach to rationalise the combined application landscape.

Execution is where integrations are won or lost. The plan is necessary but insufficient. What drives successful execution is the daily discipline of the MDEMT™ framework: mission clarity that keeps everyone aligned, disciplined communications that eliminate drift, relentless momentum management that surfaces and resolves issues before they become delays, execution rigour that ensures every task is owned and understood, and transparency that keeps everyone working from the same picture.

The Steering Committee is the single most critical governance mechanism in a post-merger integration. It must be constituted and operating within Day 3 of deal close.

The Steering Committee agenda is fixed, pre-published one week in advance via the Forward Agenda, and strictly timed. No surprise agenda items. Total meeting time: 100 minutes.

Momentum is the most precious and fragile resource in a post-merger integration. The MDEMT™ Momentum Formula must be applied every day, not just in weekly meetings.

Control is the Transparency pillar of MDEMT™ in operation. Every number, every resource, every risk, and every issue is visible, current, and owned. The IMO is the control centre. The Steering Committee is the control authority.

The Financial Tracker is maintained by the Finance and Synergy Lead, reviewed by the CFO, and presented at every Steering Committee meeting. Every budget line has: an approved budget, actuals to date, a forecast to completion, a variance, a named owner, and a corrective action if variance is above threshold.

The Synergy Tracker is the financial spine of the integration's value case. No synergy is counted unless Finance signs off the baseline, the calculation method, and the evidence of delivery.

The Resource Heatmap tracks whether every workstream has the people it needs to deliver its plan. Over-scheduling SMEs is one of the most common and most damaging causes of integration failure. The IMO reviews the Resource Heatmap weekly.

The Dashboard is the Transparency instrument of the integration. It is updated weekly by the IMO and distributed before 09:00 every Monday to all Steering Committee members and stream leads.

Post-merger integrations are inherently conflict-generating environments. Two organisations with different cultures, power structures, reward systems, and leadership styles are being forced together at pace. Conflict must be anticipated, surfaced early, and resolved systematically. The Momentum and Mission pillars of MDEMT™ are the leadership response.

Where the deal or integration plan results in workforce reduction, the following nine-step process must be followed with absolute precision. Deviation from the legal process exposes the organisation to employment tribunal risk, regulatory action, and reputational damage.

The integration is not complete until the deal's value is captured, all obligations are discharged, and the combined business is operating as a unified entity. Closing is not a date on the plan. It is a set of conditions that must all be met and evidenced.

The Value Realisation Report is presented to the Board at integration close. It is the ultimate Transparency deliverable of the Mission PMI™ Approach.

Post-merger integrations do not fail because of inadequate plans or insufficient governance. They fail because of leadership. Unclear direction. Insufficient courage to surface difficult truths. Accountability cultures that collapse under pressure. Teams that lose trust in the people leading them. The Mission PMI™ approach addresses this directly — not by hoping for good leadership, but by building it deliberately into the programme from Day 1.

Mission Leadership is built on a single, liberating insight: Leadership is a Practice, not a Title. It is a set of specific, learnable behaviours that any person at any level can apply, improve, and make their own. In a PMI context, this means that leadership is not the exclusive concern of the IMO Lead and the Steering Committee. It is the concern of every workstream lead, every team manager, and every contributor who has a responsibility to deliver.

Why Leadership Matters in PMI — More Than Anywhere Else

A post-merger integration compresses every leadership challenge into a single programme. Leaders must provide direction when the destination is genuinely unclear. They must act with sincerity when their own position is uncertain. They must build clarity when two organisations are working from entirely different assumptions. They must demonstrate courage when politically uncomfortable decisions are the only ones that will protect the deal's value. They must drive ownership and accountability across teams that do not yet trust each other. They must execute relentlessly while managing people who are anxious, overloaded, and resistant to change. And they must do all of this with compassion for human beings navigating one of the most disruptive professional events of their careers.

The 7 Practices in the PMI Context

The Leadership Anchor — What Am I Doing to Position Success?

The Leadership Anchor is the practice every PMI leader should apply every day. It is a simple self-assessment question — not a performance review, but a habitual act of honest leadership self-reflection. Applied consistently, it is one of the most powerful leadership tools in a complex integration.

Developing Leadership During the Integration

Leadership Self-Assessment Checklist — PMI Edition

The MDEMT™ Execution pillar defines what disciplined execution looks like at programme level. The 7-Step Execution Cycle makes that discipline operational at every level — from a workstream lead managing a complex 90-day plan to an individual contributor executing a single integration task. It is the common execution language of Mission PMI™.

A simple guide that demystifies execution and enables a common way of working. The focus is relentlessly on what's right — not whose right. When everyone in the programme applies the same seven questions to their work, a fundamental shift occurs: the conversation moves from opinion, position, and politics to clarity, evidence, and accountability. That shift is the foundation of a genuinely high-performance integration.

The 7 Steps — Quick Reference

What's Right vs Whose Right — The Execution Principle

This principle is not a cultural preference — it is a performance requirement. In a post-merger integration, the organisations being combined have different histories, different habits, different politics, and different versions of the truth. 'That's not how we do it here' and 'We've always done it this way' are the enemies of integration value. The 7-Step Cycle creates a common, evidence-based framework that depoliticises execution.

The 7 Steps in Full — PMI Application

In a PMI context, execution without clarity of purpose is the most expensive form of activity. The integration has hundreds of concurrent tasks across twelve workstreams. Every task must have a precise statement of what it is, a clear Definition of Success, and Milestones and Checkpoints that confirm it is on track before it reaches completion. Without these, tasks drift, quality is inconsistent, and the Steering Committee is perpetually working with incomplete information.

In a PMI, the connection between individual tasks and deal value must never be lost. People who understand why they are doing something — what integration objective it serves, what synergy it enables, what risk it mitigates — are more committed, more resourceful when obstacles arise, and more resilient when the programme demands more than they expected to give. The WHY also provides a continuous alignment test: if the action being taken does not contribute to the deal's value thesis, it should be questioned before it continues.

In a complex integration with interdependent workstreams, the HOW is not just a personal discipline — it is a programme governance requirement. When every person can articulate how they are going to accomplish their task with a clear sequence and rationale, two things happen: they surface the integration dependencies and risks themselves before others find them, and the IMO can coach, support, and intervene precisely — rather than guessing what help is needed.

In a post-merger integration, every deadline is connected to something else. A missed legal obligation creates regulatory exposure. A missed technology milestone delays the entire system migration. A missed people consultation deadline creates employment law risk. The consequences of failure in a PMI are rarely contained to the task that missed — they cascade. When people understand why their timeline matters to the broader integration, they protect it differently.

This is the alignment check — the mechanism that prevents integration drift. In a PMI, where priorities shift, new information emerges daily, and workstreams interact in complex ways, it is easy for execution to drift from its original purpose without anyone noticing. The ALIGNED? step is the course-correction mechanism that ensures what is being executed is still the most direct route to the outcome agreed. Applied as a regular leadership check-in tool, it is one of the most powerful drift-prevention disciplines in the programme.

No workstream in a PMI executes in isolation. Every task has upstream inputs from other streams and downstream outputs that other streams depend on. Failing to manage these dependencies — and to communicate changes when they occur — is one of the most common causes of PMI delays. In a complex integration, a change in one workstream can cascade through three others in 48 hours if not communicated. The person executing owns the communication of their dependencies in both directions, and owns the communication of any change that affects others.

Execution in a post-merger integration does not manage itself. The seventh step closes the loop between action and outcome — it is the discipline that surfaces, at the earliest possible moment, whether what is being executed is actually working. In a PMI context, this is not optional: the Steering Committee, the MDEMT™ Dashboard, and the Synergy Tracker all require live, accurate progress data. The tracking cadence must be proportional to the timeline and stakes of each workstream.

Using the 7-Step Cycle as a PMI Q&A Tool

The most powerful application of the 7-Step Cycle for PMI leaders is as a structured coaching and review tool. Used in stream reviews, 1-to-1s, and Steering Committee preparation, it replaces vague performance pressure with specific, constructive dialogue — surfacing what someone is working on, where they are, what is blocking them, and what they need.

Appendix A — Quick Reference Checklists

Day 1 Checklist — First 24 Hours Post-Close

Week 1 Checklist

30-Day Checklist

Appendix B — Mission Systems Framework Reference

Mission PMI™ — The Approach

ISOPOSED™ — From Idea to Execution

TORSEMI™ — From Strategy to Delivery

Appendix C — Client Proposition

A Deal-to-Value PMI Office

Mission Systems positions the PMI Office as a structured operating model that converts merger terms into an executable integration plan, protects all legal obligations, drives synergies, controls risk, manages people impacts, and keeps executive decisions moving at pace from Day 1 to value sign-off.

What Makes Mission PMI™ Different

Appendix D — Document Control