Change rarely fails in the boardroom. It fails on a Tuesday morning, three weeks later, when a supervisor cannot answer a simple question. Which system do we use for returns now? Does my team still report to the same person? What happens to the restaurants we moved last week that cannot log in? The strategy was sound. The announcement was well written. Nobody planned for the hundred small questions that follow, or for the knowledge that walked out of the door with the old team.
Our change communications work covers transitions, restructures, platform migrations, integrations after an acquisition and any moment when the way people work is about to shift. We help you decide who needs to know what, in which order, and we write the material that lets managers, specialists and front-line teams carry on doing their jobs while the ground moves.
What change communications covers
Change communications is the planned communication around an organisational change: before it is announced, while it happens and after it settles. It differs from day-to-day internal communications in three ways. It has a fixed sequence, because the order in which people hear things matters as much as the content. It has to carry decisions that are still being made. And it has to protect operating knowledge, the know-how that exists only in people’s heads and in workarounds nobody wrote down.
Typical situations include moving from a local system to a parent group’s global platform, merging two teams after an acquisition, reorganising regions or functions, closing or relocating a site, and changing suppliers or partners that customers deal with every day.
Start with a stakeholder map, not a message
The first instinct is to write the announcement. We start one step earlier, with a map of every group the change touches. For a platform migration in a business that runs local operations under a global parent, a simplified map might include:
- Local operations teams, who know how the current process really works, including the exceptions.
- Global technology and product teams, who own the new platform and need local requirements stated precisely.
- Managers, who will be asked questions first and need answers before their teams do.
- Customer-facing teams, who must explain the change to customers and partners without improvising.
- Customers and partners themselves, whose daily routines may change.
For each group we record what changes for them, what they are likely to worry about, what they need to do and by when, and who at your company owns the conversation. That map becomes the backbone of the sequence plan.
Decision briefs: make open questions visible
Transitions stall when decisions sit in inboxes. A local team raises an issue, a global team half-answers it, and three weeks later nobody remembers who was meant to decide. We use a simple one-page decision brief to stop that drift. The structure below is an illustrative example; yours will carry your own content.
| Section | What it contains |
|---|---|
| Current process | How the task is done today, in plain steps, including the local exceptions |
| Issue | What the new platform or structure does differently, and who is affected |
| Decision required | The specific choice, the options and who has the authority to make it |
| Consequence | What happens to customers, teams or timelines if the decision is late or goes either way |
A short status list sits on top of the briefs: completed, unresolved, decision needed. Leaders see at a glance where the transition is waiting on them. It is a modest tool, and it saves weeks.
What knowledge could your business lose in its next transition?
Send us a briefRestructures and migrations: sequence is the message
When people hear about a change matters as much as what they hear. A team that learns about a restructure from a customer, or from a calendar invitation with an ominous title, will not trust the official version that follows. We plan the sequence day by day: leadership briefed first, then managers with their cascade kits, then affected teams in person or on video with their own manager, then everyone else, then customers and partners where relevant. Each step has its channel, its owner and its timing.
Restructures that affect roles involve your HR team and legal advisers from the start. They decide what can be said, when and to whom; we help you say it clearly and humanely. We do not give employment or legal advice. For announcements that also reach investors or the press, we coordinate with our corporate communications team so the external and internal versions match.
Manager cascades that actually cascade
Most employees hear about a change from their manager, and most managers are briefed a few hours before they are expected to explain it. A manager cascade kit closes that gap. Ours usually contains a one-page briefing note in plain language, the key messages in the manager’s own words rather than corporate ones, questions and answers including the uncomfortable questions, guidance on what not to promise, and a simple route for questions the manager cannot answer. We test the kit with two or three managers before it goes out. Their questions always improve it.
Senior leaders need their own material too: the talking points for a town hall, the email from the CEO, the honest answer to “will there be more of this?”. That is where our leadership communications work joins in.
Knowledge transfer before people move on
Every transition puts operating knowledge at risk. The person who knows why a particular partner’s orders are entered by hand, or which report the finance team quietly depends on, may be moving role or leaving. We run structured knowledge-transfer sessions and turn them into written material: the task, the steps, the exceptions, the owner and how the document will be maintained. Where the result needs to become proper documentation for daily use, our content and editorial team writes it as task-based guides people can follow under pressure.
Knowing whether the change has landed
An announcement that went out is not a change that landed. We keep a running log of the questions people ask, through managers, the intranet, the help desk and customer-facing teams, and review it every week. The log is the most honest measure there is. When the same question keeps arriving, the material has a gap, and we fix the material rather than repeating the message louder.
Alongside the log we agree a few simple checks with you: whether managers held their briefings on time, whether teams can say what changes for them in their own words, and whether the unresolved list on the decision briefs is getting shorter. We do not promise a score in advance; we report what we find, as described in how we measure.
How a change communications programme runs
Understand
Interviews with the leaders driving the change and the teams it affects, plus the stakeholder map.
Plan
The sequence plan, decision-brief format, channels and owners, agreed with leadership and HR.
Prepare
Announcements, cascade kits, questions and answers, and knowledge-transfer material.
Support
Weekly updates, new questions answered and the status list kept current until the change settles.
We work remotely with organisations worldwide, over video and shared documents. Local-language material is written by native-speaking colleagues and specialists. Fees are fixed before we start; see how we charge. The case notes below come from our team’s experience, work our founder led in earlier in-house and programme roles, written up to show the approach rather than to claim results for Quiamo.
