Change Management Communication: Getting the Timing Right

Time to action—and why managing the movement is an art.

Change management communication breaks down when announcements and action lose their connection. Leaders promise change that never reaches everyday work. Or they introduce change before people have time to understand it and prepare.

I see both patterns in the organisations I advise. An initiative launches with energy and then disappears into meetings. A new system goes live, and the people expected to use it find out almost at the last minute.

One leaves people waiting. The other leaves them catching up.

I call the interval between a stated commitment and its first meaningful consequence time to action. Managing that interval means making promises the organisation can deliver and giving people enough time to participate. It is a practical part of leading change that deserves more attention.

What is change management communication?

Change management communication helps people understand why a change is happening, what it means for their work, what they need to do and where they can get support. It also gives them a way to ask questions and influence how the change happens.

A clear message matters. So does the sequence around it: the decision, the conversation, the preparation and the action. A message can be perfectly understood and still arrive at the wrong moment.

That is the problem I want to explore here. When does your announcement become real for the people doing the work? And are they ready when it does?

Two ways change management communication breaks down

1. Announcements arrive before commitment

An initiative gets announced. There is a kickoff, a deck, a workshop and a standing meeting that appears in everyone’s calendar on a Tuesday. Some of my clients have a good word for the noise this generates: tam-tam. A great deal of sound, very little movement.

Then the weeks pass. The initiative stays technically alive. It appears in updates and quarterly reviews. But nothing has changed for the people doing the work.

What follows is often quiet. People recalibrate what leadership’s announcements are worth. They begin to treat them as intentions rather than commitments. They wait because experience has taught them to wait.

I saw this in an organisation preparing to launch a new programme. The conversations had happened. The people expected to run it had been briefed. The shape of the programme was clear. What was missing was senior management’s commitment.

The programme had been described before it had been authorised. When the moment came to start, there was no approved basis for doing so.

The people involved had already reorganised their work around it. They were embarrassed, then sceptical. That scepticism would follow the next announcement, long after the original programme had stopped being discussed.

The lesson is about the promise. People can contribute to an idea before it is approved, provided they understand that it is still an idea.

2. Change arrives before people are ready

The opposite pattern is just as familiar. A system goes live. A restructure happens. A decision made in a small room reaches everyone else as a completed fact.

The work behind the decision may be sound. But the people affected discover it while trying to do their jobs. They have to re-plan commitments, explain the change to their teams and answer questions they have had no time to consider.

In another organisation, I saw what everyone called a “big bang”: a new tool, a hard go-live date and very little preparation. People were invited to training and expected to work in the new system the following week, without a clear advance explanation of what was coming.

Training became the announcement, the preparation and the transition, all at once.

The immediate cost was disruption. The longer-term cost was a less predictable working environment. People had learned that important decisions could arrive without warning.

In the first pattern, people lose confidence that words will lead to action. In the second, they lose confidence that they will be prepared for the action. Both damage trust.

Time to action: connecting communication with delivery

Treating these situations as separate communication and execution problems can hide what connects them. In both, the relationship between the message and the movement has broken down.

A long interval can work when people see progress and understand the next milestone. A short interval can work when the change is familiar and preparation is already in place. The number of days alone tells you very little.

What matters is whether the interval matches the promise and the work people need to do.

This is why I think of managing the movement as an art. It requires judgement about the size of the change, the people it affects, the work it disrupts and the promises the organisation has already made.

A plan gives that judgement structure. Listening tells you when the plan needs to change.

When should you communicate organisational change?

Communicate the need for change early. Be precise about what is being explored, what has been decided and what you can commit to delivering.

You do not need every answer before starting a conversation. You do need to distinguish an invitation to contribute from an announcement of a decision.

For example, these messages create very different expectations:

• Exploration: “We are reviewing how we manage engineering changes. We want your input before deciding on the approach.”
• Decision: “We have approved a pilot with one team. The pilot owner will brief everyone involved before it starts.”
• Commitment: “The pilot begins on the agreed date. Here is what changes, how to prepare and where to get support.”

If a date remains uncertain, say so. Give people the next decision point or update date instead of implying that the full rollout is ready.

This is consistent with Prosci’s guidance on change communication: start early, address why the change is happening, prepare the people delivering the message and create opportunities for dialogue.

When communicating change to employees, work backwards from what each group needs to be ready. Someone whose daily tasks will change needs more than the information shared with a stakeholder who only needs awareness.

A practical change management communication plan

I would put the communication plan and delivery plan side by side. Every significant message should connect to a decision, a preparation step or an observable change.

Use these five questions to build that connection.

1. What can we honestly commit to?

Check the approval, ownership, resources and dependencies behind the announcement. If only a pilot is funded, announce the pilot. If the next step is consultation, explain what people can influence.

2. Who needs to know, and what changes for them?

Map the people affected by the work, including those downstream. In a PLM rollout, that may include engineering, manufacturing, procurement and service. Describe the practical impact for each group.

Equip managers to discuss those impacts before their teams are expected to act. They need time to understand the decision and raise questions themselves.

3. What preparation must happen before the change?

Identify the conversations, demonstrations, practice, access and support people need. Put these activities into the delivery schedule. A training invitation should not be the first indication that someone’s work is about to change.

The same principle applies to AI adoption: licensing a tool does not prepare people to use it well. My AI adoption framework connects direction, foundations and skills with changes to everyday workflows.

4. What will people see next?

Give the announcement a credible next step: a decision, a working pilot, a tested process or a change people can use. Assign an owner and a delivery window.

Harvard Business School’s guidance on communicating organisational change similarly connects a clear description of the change needed with ownership, a timeline and a measurable target.

5. How will we listen and close the loop?

Choose a way for people to raise concerns and report barriers. Explain who will respond. Then show what happened to the feedback.

When a milestone slips, update the people who depend on it. Explain what changed, what it means for their plans and when they will hear from you again. Silence leaves them to invent the explanation.

Here is a simple structure you can copy into your own plan:

Stage	What to communicate	What should follow
Exploration	Why change is being considered, what remains open and how people can contribute.	Consultation and a stated next update.
Approved decision	What has been agreed, who owns it and the first credible milestone.	Visible progress against that milestone.
Preparation	What changes in daily work, what people need to do and where support is available.	Time to practise, ask questions and resolve barriers.
Implementation	What happens now, known issues and support arrangements.	Support and progress updates.
Follow-through	What has changed, what has slipped and what happens next.	Evidence of delivery and responses to feedback.

How to measure whether communication leads to action

To make time to action useful, define the promised change before measuring the interval.

Time to action = elapsed time between a stated commitment and the first observable change promised by that commitment.

This is a working measure I propose for leadership conversations. It is not a universal benchmark. If the promise was that teams would use a new approval workflow, another project meeting does not count as delivering it.

Track the interval alongside three checks:

• Delivery reliability: Did the promised milestone happen within the stated window?
• People readiness: Can affected employees explain the change, carry out the required task and find support?
• Adoption: Is the new way of working being used in practice?

A shorter time to action is not automatically better. A rushed rollout can improve that number while leaving people unprepared. The aim is a reliable connection between the promise, the preparation and the result.

Predictable leadership builds trust

The leaders I have seen manage this well are the ones people can plan around. When they announce something, the next step happens within the window they described. When they move, the people affected have had a chance to prepare.

A smaller promise delivered on time teaches people that your words are predictive. Over time, that gives you room to ask more of the organisation.

Before the next announcement, ask yourself:

• How long will this take to become real, honestly?
• When it becomes real, who might still be surprised?

The answers tell you where the work is. You may need a more credible commitment, earlier involvement or more preparation. Often, you need all three.

That is the art of managing the movement: keeping your words, your decisions and people’s experience connected.

Speed is not the skill. The distance is.