Internal communication during change: A guide to success

Change rarely starts with clarity. It starts with questions in the inbox, an executive team in a hurry, employees who hear different versions of the same thing, and a project team that believes a single update on the intranet is enough. In public and complex organisations, this quickly becomes expensive—not necessarily in money first, but in doubt, friction, and lost momentum.

That is why internal communication during change must be treated as a management discipline rather than mere publishing. Recent industry data indicates that 66% of communication departments lack a clear purpose and goals for internal communication (recent industry data on internal communication). This explains why so many change processes generate activity without establishing direction.

A useful playbook must be able to function in the real world. It must be able to handle frontline staff, middle managers, hybrid work, professional differences, and daily operations that do not stop just because a project goes live. This requires analysis, clear messaging, channel discipline, a phased plan, and behavioral measurement. Technology should not sit alongside communication. It should help make the strategy concrete in employees' everyday lives.

The Foundation of Effective Change Communication

When organisations fail with internal communication during change, it is rarely because they lack content. They lack an overview. Messages are broadcast widely, but the change impacts people differently. A manager needs arguments and answers. A caseworker needs to know what changes in their workflow. A frontline employee needs brief, precise messages at the time they can actually be used.

Segmentation before publishing

The first rule is simple. Segment by work situation, not just by the organisational chart.

This means employees should be divided by at least four factors:

1. Role in the change. Deciding, implementing, affected, or observing.

2. Access to information. Fixed screen access, shared PC, mobile access, or virtually no digital access.

3. Dependency on new workflows. High, medium, or low.

4. Attitude towards the change. Ambassador, wait-and-see, skeptical, or active opponent.

Practical rule: If everyone receives the same message at the same time in the same format, the communication is already too broad.

This is not academic work; it is the fastest way to avoid noise. Danish research on organisational change points to a step-by-step approach where target groups, existing channels, and leadership support are mapped out first, before messages and initiatives are tailored and subsequently evaluated on behavior (CBS thesis on internal communication in change processes).

A stakeholder analysis that can actually be used

A useful stakeholder analysis can be completed in just a few working days if the format is kept tight. Use a simple worksheet with five fields per group:

• What are they losing?
  Employees react faster to loss than to visions. Map this out honestly.

• What do they gain?
  Not in project terms, but in everyday improvements.

• What do they fear?
  Typically ambiguity regarding responsibility, competency requirements, or extra work.

• Who do they listen to?
  Formal leaders, super-users, union representatives, or colleagues.

• When should they hear what?
  Not everyone needs to hear everything at the same time.

Once this work is done, communication becomes more precise. Then leadership can talk about direction, middle managers about priorities, and professional groups can get answers about their specific changes.

For organisations working systematically with well-being and stable operations, it is also relevant to link change communication with efforts to achieve safety and well-being in the workplace. It is the same core logic. Insecurity arises when employees do not understand what is happening, who is deciding, and what is expected of them.

A final discipline should be introduced already at this stage. Decide which change model the project is working under. Not for the sake of theory, but to have a shared language between the project, HR, management, and communication. A practical guide on change management models can help you choose a model that fits the organisation's maturity and complexity.

Create a Clear Narrative and Targeted Messages

Many changes go off course because the organisation sends out information without a narrative. Employees receive updates, but they do not understand the context. Consequently, they begin to fill in the gaps themselves. That is where rumours, overinterpretation, and passive resistance gain momentum.

Build the narrative before the FAQ explodes

A strong narrative must be capable of being spoken aloud by both executive management and immediate supervisors without alteration. It should answer three questions:

• Why is the change happening now?

• What will be different?

• What is expected of the employees?

If any of these three are missing, the communication becomes either defensive or vague. Specialist literature points directly to a key pitfall. Internal communication must not be treated as a pure information project. When communication is not linked to organisation, management, and daily practice, the effect is often short-lived (textbook on internal communication during change).

A good core narrative does not just describe the decision. It explains the working reality in which the decision must function.

This also means that the tone of voice must be selected deliberately. During major structural changes, a combination of clear direction and objective empathy works best. For minor process changes, the tone can be more forward-looking and operational. What almost always fails is slick project rhetoric, where everything is described as an improvement before employees have even seen the consequences.

A message house that stands up to operations

A message house is useful if kept simple. The top is the "why" of the change. The middle consists of three to five key messages. At the bottom is the translation for specific target groups.

Here is a practical example:

The crucial part is the translation in the column "What does this mean for you?". This is where many plans collapse because the communication remains at a management level. Employees only truly listen when the message affects their priorities, collaboration, or workflow.

Organisations that want to strengthen the link between messages and behavior can find inspiration in work concerning employee engagement in a new working reality. The point is simple: engagement is not generated by more messages alone, but by relevant messages that make sense in each employee's daily life.

Choose the Right Channels to Reach All Employees

Channels are not neutral. They shape the pace, understanding, and trust. An email can be effective for personal information. A management meeting can handle resistance. A mobile message can reach the frontline quickly. However, without a clear center, the channel strategy becomes parallel communication.

Use a hub-and-spoke model

A solid model is the hub-and-spoke. One channel serves as the single source of truth, and other channels distribute and amplify the messages.

In practice, this means:

• Hub
  A single central location with current information, FAQs, timelines, materials for managers, and updated decisions.

• Spoke for managers
  Briefings, talking points, and Q&As, so local managers do not improvise.

• Spoke for employees
  Emails, apps, information screens, meetings, and team-specific notices.

• Spoke for feedback
  Question forms, feedback tools, local meetings, or digital forums.

The model works because it separates the storage of truth from the distribution of attention. Many organisations do the opposite. They scatter information across many channels without having a single place where employees can reliably check what actually applies.

When employees ask colleagues before checking the official channel, it is a signal that the channel design is not credible enough.

How the organisation also reaches the frontline

The difficult part is almost always employees without fixed screen access. Danish literature says very little about which channels work in those environments. Therefore, the question of how to reach the frontline without increasing noise is a real challenge (AAU overview on internal communication during change).

Consequently, channel selection should be based on the work situation, not on what headquarters usually uses.

A simple decision model looks like this:

If the frontline makes up a large part of the organisation, it is obvious to take a closer look at mobile internal communication for frontline employees. Not as extra channel noise, but as a way to make central information accessible where the work actually takes place.

What does not work is assuming that everyone reads long articles, logs in from a PC, or remembers a message after a single broadcast. Channel strategy must be designed around the workday. Otherwise, even good communication becomes invisible.

Structure Your Plan with Timeline and Launch Phases

Communication breaks down when it follows the internal logic of the project instead of the employees' readiness to receive it. The project group thinks in terms of milestones and deliverables. Employees think in terms of when something changes, who decides, and how long the uncertainty will last. Therefore, the timeline must build a bridge between project and operations.

Three rhythms instead of one campaign

The most useful plan does not consist of one big launch, but of three rhythms:

• The preparation rhythm
  Builds understanding and gets managers ready.

• The launch rhythm
  Creates visibility and provides clear next steps.

• The anchoring rhythm
  Maintains momentum, answers new questions, and adjusts along the way.

The last point is often underestimated. Many organisations spend most of their energy on go-live and too little on the weeks that follow. Yet, this is when questions become concrete. Only then do employees discover where old habits collide with new requirements.

A simple phase plan that works

A phase plan can be kept simple if each phase is linked to project milestones and a single main objective.

Before launch

Here, management must agree on the narrative, decisions, and boundaries of what is not yet clarified. Middle managers must have materials before employees do, not after. Otherwise, communication starts with a trust problem.

At launch

Now there must be high visibility and low doubt. Employees must be able to find the same core information in multiple places. Not because content should be duplicated uncritically, but because people orient themselves differently. Some read, some ask, some wait and see.

Plan for silence as well. Employees need periods where they can test new workflows without being hit with new messages every day.

After launch

Here, the communication team must monitor where understanding is lagging. Which teams are still asking the same things. Which managers are getting the toughest questions. Which local workflows are sabotaging adoption. It is in this phase that adjustments have the greatest impact.

A practical minimum is to have a weekly plan for the first few weeks specifying responsibilities, channels, key messages, target groups, and expected reactions. No more, but no less. This discipline makes the plan's quality visible to the project manager, HR, and the executive team alike.

Establish Feedback and Measure the Effect of Your Efforts

Monday morning, a major change goes live. Wednesday, executive management says the communication has been sent out. Friday, support can see that the same mistakes are being repeated, and middle managers' time is consumed explaining something that should have been clear from the start. Here, the difference between broadcast information and real anchoring becomes visible.

In practice, many measurements fail because they stop at publication. Page views, opens, and clicks show activity. They do not show if employees have understood, accepted, and converted the message into action. In public and complex organisations, this is a costly blind spot, because misinterpretations quickly embed themselves in local workflows.

Measure what changes behavior

A useful measurement framework has three levels. It makes it possible to distinguish between distribution errors, comprehension problems, and lack of anchoring.

I usually put it simply: if communication is only measured on visibility, the team ends up optimising for publication rather than effect.

Therefore, each major change track must have a few concrete success measures. This could be fewer repetitive questions, higher adoption of a new workflow, faster manager clarifications, or fewer local detours. This type of target is closer to reality than general engagement figures.

Build feedback into operations

Feedback only works when it changes something. This requires a stable rhythm and clear ownership. Otherwise, input just becomes another pile that no one responds to.

A simple loop looks like this:

1. Collect signals
   Use pulse surveys, questions from managers, search data, support requests, and comments in the channels employees already use.

2. Sort the cause
   Distinguish between lack of information, professional disagreement, technical barriers, and unclear decision-making power.

3. Assign responsibility
   Communication does not own the whole field. Some answers belong to HR, project management, IT, or business heads.

4. Give a visible response
   Explain what the organisation has heard, what is being changed, and what is still awaiting a decision.

The last point is often forgotten. When employees submit input without seeing a reaction, the willingness to answer drops rapidly.

A modern platform makes this work easier because feedback, segmentation, and follow-up can be gathered in one place. With an intranet like Colibo, the communication team can see which target groups lack information, which questions recur, and where content needs to be adapted more precisely. AI can help find patterns in searches, questions, and reading behavior, so adjustments are made based on real signals rather than gut feelings. In the public sector, this bridge between strategy and daily operations is particularly valuable because employee groups work under different conditions, with different systems, and often with limited time to seek out information.

Look for friction, not just answers

Quiet target groups are not necessarily clarified target groups. Silence can mask busyness, resignation, or uncertainty. Therefore, measurement should also include indirect signs. Repeated mistakes. Local workarounds. Many searches for the same terms. Managers requesting the same clarifications multiple times.

This pattern is repeated in research on digital internal communication and employee voice, where employees' opportunity to provide input is closely linked to the experience of relevance and involvement (overview of research on employee voice and internal communication at CIPD).

The strongest sign of a well-functioning feedback system is simple: the same questions occur less frequently, and the answers become more precise out in the line.

Make middle managers accountable, not just responsible

Middle managers remain the most important translators in a change process. But they must not only have responsibility. They must have materials, mandate, and a clear path for escalation. Otherwise, the organisation measures the impact of communication while the manager level lacks the necessary basis to succeed.

A brief answer sheet, standard questions for team meetings, and a visible channel for follow-up are often enough to raise quality significantly. The practical trade-off is clear: more local adaptation provides better relevance but also increases the risk of variation in the message. Therefore, the core message must be tight, while examples and explanations can be adapted locally.

This is how measurement becomes useful—not as backward-looking reporting, but as a management tool that continuously improves communication, managers' dialogue, and employees' ability to act correctly.

Frequently Asked Questions on Change Communication

How is resistance handled without getting defensive?

A department reacts sharply to a new initiative. The comments sound like resistance, but behind them often lies something more concrete. Employees do not understand why the change is coming now, or what they are losing in exchange.

The solution is not to dial up the slogans. The solution is to translate the resistance into categories. Is it disagreement on direction, fear of poorer quality, ambiguity about roles, or pure overload? Only then can management answer precisely. A good deal of resistance disappears when someone shows that they have understood the problem correctly.

How is communication kept alive after the launch?

The classic pattern is well known. First comes high attention. Then the pace drops while employees still lack answers. This is where many organisations lose the anchoring.

It works better to plan follow-up as part of daily operations. Use a fixed cadence of short status updates, manager briefings, and visible answers to recurring questions. Not because there is always something new to say, but because silence is quickly interpreted as uncertainty or lack of direction.

How do you make middle managers partners in the process?

A middle manager gets questions from their team but has only seen the same general update as everyone else. Then the manager becomes a bottleneck rather than a translator.

This is prevented with a simple manager kit. One memo with key messages. One sheet with anticipated questions. One place to escalate questions the manager cannot answer themselves. Middle managers should not write the organisation's narrative; they must be able to translate it to the team's reality.

How can AI be used without creating new uncertainty?

An organisation introduces an AI assistant for searching and assistance in the internal knowledge space. Employees become curious, but also cautious. Who wrote the answers? What data is used? Can the results be trusted?

This is a real question. Danish coverage points out that there is often a lack of answers regarding how employees find and evaluate information when AI assistants are introduced in a Danish and EU-regulated context. The question is not just how to increase engagement, but also when AI creates more uncertainty than value (Danish perspective on AI in internal communication).

The practical solution is governance before launch. Employees need to know which sources the AI is allowed to use, when an answer is advisory, and when official policy or manager instructions apply. AI works best as an access layer to existing, quality-assured knowledge. It works poorly as a substitute for unresolved decisions.

What does the organisation do when different professional groups hear different things?

This often happens in municipalities, hospitals, and other complex settings. The same change is interpreted through local needs, and suddenly several versions of reality run in parallel.

Here, central communication must be brief and consistent, while local managers are given clear frameworks for what they may adapt. Freedom without a shared core creates variation. A shared core without local translation creates distance. Both harm the impact.

When internal communication during change is to work in practice, it requires more than publishing. It requires a platform where employees can find valid information, managers can translate messages, the frontline can be reached via mobile and screen, and the organisation can work with feedback, search, and AI on a secure foundation. Colibo is built for exactly that reality in complex organisations.