Mergers & Acquisitions

 View Only
  • 1.  CM during a merger

    Posted yesterday

    My organization is currently going through a merger, and I've been tasked with building a combined change management process to scope, track, and monitor organizational changes (technology, process, structural...etc) as they move through implementation.

    In this role, I'm acting as both Project Manager and the sole Change Manager, and leadership has asked for a practical change intake and tracking system that aligns with change management principles but remains relatively straightforward to implement.

    Most merger-related change management resources I've found focus heavily on culture and adoption, which will be addressed separately later in our integration process. My immediate focus is on structuring how changes are identified, scoped, and governed across the organization during implementation.

    I'm currently struggling with where to start in designing a clean, structured process that blends project management discipline with change management principles.

    For those who have built something similar:

    • What intake or change scoping frameworks have worked well for you?

    • Are there templates, tools, or governance models you've used to track organizational change during large transitions like mergers?

    • How do you keep the process simple enough to be adopted, but structured enough to provide visibility and control?

    Any examples, templates, or resources would be greatly appreciated.



    ------------------------------
    Sneha Upadhyay
    ------------------------------


  • 2.  RE: CM during a merger

    Posted 4 hours ago

    Hi Sneha - my suggestion:

    1.Define the future integrated operating model (at a high level):Before capturing individual change requests, it helps to define what the combined organisation is aiming to look like. This usually covers areas such as:

    • Organisation structure and roles
    • Core business processes
    • Technology platforms
    • Governance and decision rights
    • Customer journeys / service model

    2.Conduct a current vs future gap assessment
    Each business area then performs a light gap analysis comparing the current state of both organisations against the intended future operating model.

    Typical questions include:

    . Which processes need to be harmonised?
    • Which systems will be consolidated or retired?
    • Where will roles or structures change?
    • What policies or governance models need alignment?

    Each gap essentially becomes a candidate change initiative.  

    3.Convert gaps into a structured change intake pipeline
    Once the gaps are identified, they can be logged into a change register or intake pipeline with basic scoping information:

    • Change description
    • Business capability / function impacted
    • Type of change (process, technology, structural, policy)
    • Impact level (low/medium/high)
    • Dependency on other initiatives
    • Proposed owner

    From there you can triage and track them through implementation. Your delivery approach ie traditional/agile/hybrid will determine your project tracking system which will again determine the artefacts for this....Above activities mainly sits with business analysis discipline but if you are doing everything you will need to wear different hats to cover the end-to-end lifecycle of the post acquisition integration effort..



    ------------------------------
    Ama Yeboah
    ------------------------------