Skip to main content

How to Write a Change Email That Reinforces the Right Behaviors and Drives Adoption

Use a change email to reinforce adoption, not just share updates. Tailor the message to the change phase, audience, and desired behavior; use the right sender, plain language, manager support, and a clear call to action.

Introduction: why this action matters for adoption

A change email is not just an announcement. Used well, it is a small change-management intervention that helps people understand the change, interpret what it means for their work, and take the next useful action. Prosci’s ADKAR model describes successful individual change through Awareness, Desire, Knowledge, Ability, and Reinforcement; a reinforcing email is most valuable when it deliberately supports one or more of those outcomes rather than simply “sending an update” [Prosci, 2025]. Gallup’s workplace research also shows that during disruptive change, trust and effective leadership communication are strongly associated with engagement and lower burnout, and that manager conversations help employees personalize what the change means for them [Gallup, 2024].

What this action is and when to use it

This action is a targeted written communication, usually sent through email or a mass-mail channel, to reinforce the right behavior and response during a change. It belongs in the change communication and engagement category because its purpose is to build awareness, confidence, readiness, and adoption.

Use it when an impacted group needs a clear prompt: a decision has been made, a milestone is approaching, training is required, a new behavior must start, confusion needs correcting, or a positive behavior should be reinforced after go-live. Do not use email as the only intervention when the change is sensitive, resisted, or high impact. SHRM notes that change communication channels are not one-size-fits-all and should be intentional, predictable, and clear [SHRM, 2026]. CIPD similarly emphasizes planning, tailoring, line manager roles, and multi-directional dialogue in employee communication [CIPD, 2025].

Preparation: inputs, stakeholders, materials, timing, and decisions needed

Before drafting, confirm the change impact, audience, project phase, desired behavior, sender, approval route, and follow-up channel. Decide what the audience should know, feel, and do after reading. For example, in early awareness the email may explain why the change is happening; before go-live it may direct people to complete training; after go-live it may reinforce correct use and point to support.

The sender matters. Sponsors are best for the strategic “why” and visible commitment, while people managers are best for local meaning and team-level expectations. PMI identifies communication, leadership, sponsor engagement, ownership, milestones, metrics, and benefits communication as important change enablers [PMI, 2014]. Practical guidance: prepare manager talking points before the email lands so managers can answer questions consistently.

Step-by-step facilitation guide

  1. Define the behavior to reinforce. Write one sentence that names the behavior: “Use the new intake form for all customer requests from Monday,” or “Complete the readiness checklist before system access is enabled.” This keeps the message adoption-focused rather than information-heavy.

  2. Match the message to the phase. In discovery, reinforce listening and participation. In design, reinforce input and readiness activities. Before go-live, reinforce training and cutover actions. After go-live, reinforce use of the new process and discourage workarounds. This aligns with the ADKAR idea that different barriers require different interventions [Prosci, 2025].

  3. Choose the sender and supporting voices. Use a senior sponsor when authority and priority are needed. Use a direct manager when the audience needs local interpretation. Gallup describes manager conversations as the “last mile” of change communication because managers help employees answer, “What does this mean for me?” [Gallup, 2024].

  4. Draft for clarity and action. Put the main point first, use active voice, keep paragraphs short, and remove unnecessary words, following plain-language principles [NARA, 2025]. Include the why, what is changing, what is not changing, what the reader should do, where to get help, and when they will hear more.

  5. Acknowledge the human response. If the change creates workload, uncertainty, or loss, say so plainly. Schulz-Knappe, Koch, and Beckert found that change communication factors such as involvement, participation, and appreciation explain a large share of variance in attitudes and support for change [Schulz-Knappe et al., 2019].

  6. Pre-test the email. Ask a manager, impacted employee, and project lead to read it. Check whether they can identify the action, deadline, reason, and support path in under one minute.

  7. Send, equip, and listen. Send the email at a time that matches the project rhythm, then activate manager huddles, Q&A channels, or office hours. Close the loop by answering recurring questions in the next communication.

Example: how this could be applied in a real change initiative

A sales organization is implementing a new CRM workflow. Two weeks before go-live, the change manager drafts an email from the sales sponsor. The message says why the workflow is changing, confirms that account ownership rules are unchanged, asks every seller to complete a 20-minute simulation by Friday, and explains where to raise blockers. Because early feedback shows concern about slower deal entry, the email acknowledges the learning curve and links to a manager-led practice session. After go-live, a follow-up email reinforces the right behavior by recognizing teams using the new workflow correctly and reminding employees not to maintain offline spreadsheets.

Roles and responsibilities

Role

Responsibility

Change manager

Defines objective, audience, timing, message structure, feedback loop, and adoption measures.

Sponsor

Sends or endorses messages about priority, purpose, and expected behavior.

People managers

Translate the message locally, answer questions, observe resistance, and reinforce behavior.

Project lead

Confirms technical accuracy, dates, dependencies, and risks.

Communications/HR partner

Reviews tone, accessibility, channel fit, and alignment with other communications.

Adoption leads/champions

Test the message, surface audience concerns, and model the desired response.

Common mistakes to avoid

  • Sending a broad announcement when different groups need different actions.

  • Explaining the solution but not the reason for the change.

  • Omitting the specific behavior, deadline, or support path.

  • Treating resistance as a communication failure only; resistance may reflect workload, incentives, identity, trust, or capability.

  • Sending email without preparing managers.

  • Measuring success only by opens or clicks instead of readiness and behavior.

Measures of success or adoption indicators

Use three levels of measurement. First, delivery indicators: sent, delivered, opened, clicked, and bounced. Second, understanding indicators: pulse-check responses, manager questions, Q&A themes, and whether employees can explain what is changing. Third, adoption indicators: training completion, correct system or process use, reduction in workarounds, support-ticket patterns, manager observations, and readiness or ADKAR barrier checks. PMI’s change guidance emphasizes milestones, metrics, communication execution, and benefits communication, so measurement should connect the email to adoption outcomes rather than communication activity alone [PMI, 2014].

Checklist for the change manager

  • The audience and impact group are specific.

  • The desired behavior is stated in one sentence.

  • The message matches the project phase and adoption barrier.

  • The sender is credible for this audience.

  • The email explains why, what, when, action required, support, and feedback route.

  • Managers have talking points before or at the same time as the email.

  • The tone acknowledges real concerns without overpromising.

  • Success measures include behavior or readiness indicators, not just email metrics.

  • Follow-up communication is scheduled.

Reusable message outline

Subject: Action needed: [specific change/action] by [date]

Opening: Here is what you need to know and do: [one-sentence summary].

Why this matters: [Brief reason linked to customer, employee, risk, strategy, or performance outcome.]

What is changing: [Concrete change.]
What is not changing: [Stability or continuity, if relevant.]

What you need to do: [One to three actions, with deadlines.]

Support available: [Manager, training, office hours, job aid, help channel.]

How we will listen: [Feedback route and when questions will be answered.]

Close: Thank you for helping make this change work in daily practice.

References

Did this answer your question?