A change leadership communication plan should help people understand what changes in their work, why it matters and how uncertainty will be resolved. An announcement can distribute information without establishing that teams interpret it the same way. Communication is useful when it supports the next decision, not simply when a message is delivered.
This resource focuses on an authorized operating change, not a full change-management method. Required employee consultation, policy, technical training and other procedures remain separate responsibilities. Start with the approved decision and its boundaries before drafting persuasive language.
Write the decision before the message
State what was approved, what remains proposed and what has not been decided. Identify the outcome, effective point and owner of unresolved questions. When these are unclear, communication can spread a confident version of an unfinished decision.
A practical starting record contains the change, reason, scope, limits, implementation owner and review point. Explain what stays the same as well as what changes. A team should not have to infer that an existing safety or quality requirement was removed because an announcement celebrates speed.
Define audiences by the decisions they must make
Group people according to the work affected rather than sending every group the same detail. A supervisor may need to explain the new handoff. A receiving team may need to know its acceptance responsibility. A senior sponsor may need to resolve competing priorities.
Ask for each audience: What must they understand? What will they do differently? What input or authority do they need? Which questions are likely to remain? The middle-manager development guide examines how leaders translate direction into workable agreements across these boundaries.
Equip managers before asking them to explain
Give managers a concrete example, the relevant approved instructions and a route for unanswered questions. Allow them to examine how the change interacts with existing commitments. A manager should not have to choose between repeating a message they do not understand and inventing an explanation.
Prepare a brief with the decision, example, common misunderstandings and escalation owner. Avoid a script that prevents managers from acknowledging legitimate uncertainty. The message can be consistent without pretending every local implementation question has been answered.
Test understanding using an actual situation
Ask a receiving team to explain how it would act in a relevant example. Which person owns the next step? What record is used? What would cause them to consult or escalate? Compare those answers with the approved intent.
This is a clarity check, not a public quiz. If answers diverge, examine the wording, missing context or conflicting instructions. The execution guide describes the gap between direction and daily work; a read-back makes that gap observable before it becomes a missed commitment.
Plan two-way questions and responses
Choose an approved channel for questions and name who triages them. Separate requests for information, objections requiring examination and decisions outside the implementation team's authority. Set a response approach people can rely on, including what happens when an answer is not yet available.
Keep a modest question log with the work issue, responsible owner, status and response. Protect private information and use the appropriate route for confidential concerns. A public frequently asked questions list should not disclose individual personnel or sensitive customer situations.
Worked example: changing a cross-team handoff
Fictional manager brief (AI-assisted editorial): The audience is the receiving-team supervisors. The approved change requires a receiving owner to confirm acceptance before transferred work enters the queue, starting with Monday’s first handoff. The current approved change record is the instruction source; existing safety, quality and customer-approval requirements still apply. The sending team requests acceptance through that record. Supervisors will show the receiving team where acceptance is recorded and which role may accept a request. One question remains open: who covers acceptance when the usual receiver is unavailable? This is a coverage decision for the sponsor. The implementation owner will take it to the sponsor at Friday’s readiness review. These are invented details for this example, not a client account or a procedure for another organization.
At that review, the sponsor checks the missing coverage and decides within their authority whether the required condition is ready or the start needs reconsidering. Until the decision is made, the brief marks coverage unresolved and does not instruct employees to bypass acceptance. The supervisors give affected team members the authorized answer and current reference. To check understanding, a supervisor explains the action for an ordinary handoff and for one with no available authorized receiver. Confusion about a settled instruction calls for clarification; absent coverage still needs its owner’s decision and support. After a suitable work opportunity, the ongoing owner checks whether acceptance was recorded and whether unresolved requests received the agreed response. A delivered message alone is not evidence that the arrangement was adopted or improved business results.
How should you correct an outdated announcement?
Correction example (AI-assisted editorial; fictional): An approved handoff change was announced for Monday, then the authorized owner moves the start to Wednesday. A quiet edit to the original note may leave people acting on the version they already read. Identify what changed, what remains unchanged, the effective point and the current approved reference. Send the correction through the appropriate existing channels for the affected roles, and make the superseded instruction clearly identifiable without erasing the decision history.
Ask managers and receiving teams to explain which arrangement applies before and after the revised start. Track an unanswered question or conflicting instruction to its owner rather than treating delivery of a second message as proof of understanding. If the underlying decision is still pending, say so; clearer wording cannot approve it. Keep required consultation, training and operating processes intact. The useful result is that affected people can identify the current instruction and next action.
Review application after the announcement
Observe a suitable sample of work after people have had an opportunity to act. Are the expected decisions different? Are the same questions returning? Did a new uncertainty appear? Delivery and open rates can show reach, but they do not establish understanding or application.
Update the explanation and the operating agreement when evidence shows a gap. If conflicting priorities or authority remain unresolved, review the leadership engagement approach or discuss the situation with Shannon. Better communication begins with a decision people can understand and act on, not a louder launch.
About this resource: Prepared with AI-assisted drafting from published guidance. Examples are illustrative, not reported client results. Cover illustration: AI-generated.