Post-Merger Integration
The findings don't get re-typed. They get owned.
Most value leaks in the handover between diligence and integration. In Lens there is no handover: the same workstreams, observations and evidence become the integration plan.
Continuity
From observation to integration workstream
- 01
Carry over
Diligence observations and risks move into the integration plan with their workstream, materiality and source evidence intact.
- 02
Assign
Each carried finding gets an integration owner, a target milestone and a defined outcome — not a line in a slide.
- 03
Track
Tasks, workstream progress and milestone dates roll up into status reporting for the steering group.
- 04
Close
A finding is closed only when the evidence of resolution sits back in the system, next to the evidence that raised it.
Delivery
Integration tracked like a programme
Status reports, tasks by owner and status, workstream progress and milestones — with the day-100 plan sitting on the same structure as the diligence that shaped it.
RAID
Risks, assumptions, issues, dependencies
A living RAID log that started in diligence, plus an action log with owners and dates, and lessons learnt captured while the team still remembers them.
Risk register
Carried forward with original materiality and current mitigation state.
Assumptions
Explicit, owned and revisited when the facts change.
Issues
Escalation path and resolution evidence in the same record.
Dependencies
Cross-workstream links so sequencing failures surface early.
Reporting
One version of integration progress
Steering groups, sponsors and the corporate development team read the same status from the same source — generated from the plan, not assembled the night before.
See integration run on the diligence
A 30-minute walkthrough of diligence, integration and value creation in one system.