Change Management: the people side, on the same plan as the systems work
AtlanticM&A5 min read
Change Management is the part of AtlanticM&A that runs the people side of a programme: who is affected and how badly, what they are told and when, how ready they are, which sponsors are doing their part and where the resistance is. It sits inside the project, on the same work plan, owners and dates as the systems work, and it is included on every plan.
The tracker that gets dropped
Every integration plan has a line for change management. Most programmes start one properly: a stakeholder map, a comms plan, a culture survey. By the third month the comms plan is a document nobody has opened since Day 1, and the survey results sit in a spreadsheet that never made it into a steering pack.
It is rarely that people stop caring. It is that the people side arrives as one more tracker to feed, separate from the plan everyone is working to, and something has to give. On a smaller project there is often nobody whose job it is, so it depends on how much the project lead can carry.
Start from what the project already knows
The module starts from the project rather than from a blank template.
- Impacted populations. One click asks the AI for the groups the change will land on, segmented by function, location and level. It reads the project's own context to do it: the workstreams, the charters, the governance and recent meeting notes. It drafts the list, and you edit it from there.
- Impact by population. For each workstream's change, the team records how hard it lands on each group, from a minor process adjustment to a fundamental change in how work is done. A group carrying several heavy changes at once shows up before it turns into fatigue.
- A change workstream in the plan. "Generate CM Work Plan" adds a Change Management workstream to the project's work plan, in three phases: assess and strategise, orchestrate and enable, embed and sustain. The change work then has owners and dates in the same plan as everything else, so the Day 1 communications and the cutover they depend on are not reconciled by hand across two documents.
Communications that are drafted, reviewed and tracked
Communications are organised as kits against the programme's milestones: deal announcement, Day 1, welcome week, Day 30, 60 and 90, go-live. A Day 1 kit starts with twelve pieces already scaffolded, among them the CEO email, manager talking points, internal and customer FAQs and the press release. Other milestones start with a leadership email and an FAQ.
Each piece moves from draft to review to approved to sent, and the kit shows how many of its pieces are at each stage. The platform does not send them for you. You copy the approved text into your own email client, or mark it as sent, so the words that go out to a workforce stay under a person's name.
Listening without turning people into numbers
Pulse surveys run anonymously by default, and can be imported from a tool you already use. Their scaled answers feed the readiness view, population by population and stage by stage, from understanding why the change is happening through to it becoming how work is done.
The free text is where the useful answers usually are, and it is the part nobody reads when there are a hundred responses. The module groups it into themes and shows the verbatim quotes behind each one. It stops there. A theme says what people said; it does not say what to do about it. That judgement belongs to whoever is running the change.
The same line runs through the rest of it. Readiness is recorded by population, not by person. Resistance is logged with its root cause and worked through to resolution. Sponsor activities are tracked against the programme phase, so a sponsor who has gone quiet shows up as overdue work rather than a feeling. None of it produces a go or no-go. The platform presents; people decide.
What it is not
It is not an HR system. It does not hold compensation, performance reviews or personnel records. It does not replace your change methodology either: bring the framework you already use, or your own playbook, and run it here. The software keeps track of the moves. The methodology decides which moves to make.
Where it fits
On an integration it runs alongside the operational plan from the deal announcement to adoption. On a divestiture, knowledge transfer is tracked with a named recipient and a target date, and each transfer can be tied to the TSA service whose exit depends on it. On a transformation it is the workstream that decides whether the new way of working sticks.
Because it is in the project, it connects to the rest of the platform. A change sponsor is also a stakeholder, so the sponsor page can show the engagement strategies already tried with that person in Stakeholder Co-Pilot, and how they went.
Change Management is part of every plan, with nothing extra to buy. Plans and project counts are on the pricing page.
About AtlanticM&A
AtlanticM&A is the Agentic Transformation OS. Its agents work inside the programme, both augmenting and automating the work of the transformation team: work plans, governance, stakeholders and reporting in one place, with a live value bridge that moves as the work does. It is a system of work rather than only being a system of record: the charter is written in it and the plan is built in it. Meeting notes come back as proposed updates to the plan and the RAID log, the team decides what stands, and every change the AI makes carries an audit trail. The platform does the slide-building, status reporting and stakeholder briefings that usually keep a consulting pyramid busy, so a small senior team can run the programme more nimbly and for less.