How to Write a Change Message People Actually Read

In September 2024, Amazon CEO Andy Jassy sent a memo to roughly 350,000 corporate employees.

Five-day return to office. Effective January 2025.

The memo was long. Carefully worded. It invoked culture, collaboration, Amazon's identity as the world's largest startup.

Internally, employees gave it a satisfaction rating of 1.4 out of 5. According to Work From Anywhere, more than 91% were unhappy. Nearly three quarters said they were considering leaving.

One employee described finding out through the news before hearing from her manager: "Which, to be honest, is a pretty horrible way to find out about something that's going to impact your life in a huge way."

The decision itself is a separate debate.

But the communication failed.

Not because it was dishonest.

Because it was written for the organization's comfort rather than the employee's understanding.

And that distinction is everything.

Most change messages are written to update, not to align.

There's a real difference between those two things.

An update tells people what is happening.

Alignment helps people understand what it means for them, why it matters now, and what they're supposed to do next.

Amazon's memo did the first.

It didn't do the second.

Employees cited frustration with a lack of clear reasoning. Many anticipated a drop in productivity with no flexibility or real explanation offered.

The message described a future without connecting people to it.

It explained the what without answering the question employees were actually asking:

What does this mean for me and why should I trust this decision?

That gap is where most change communication breaks down.

Not a writing problem.

A sequencing problem.

Most change messages open with logistics.

Dates. Timelines. System names. Phases.

That's not where humans start when they're processing change.

They start with meaning.

Why does this exist? Why now? What does it mean for me — not for the business?

If those questions aren't answered first, the logistics become noise.

The test I use before I write anything:

Can I write one sentence that answers "why should I care" — from the employee's perspective?

Not "this supports our strategic priorities."

But "this changes something real about how you work, and here's what that means."

If I can't find that sentence, the message isn't ready.

Amazon opened with culture and collaboration. Organizational rationale, not human rationale.

The gap between those two things is exactly where the resistance formed.

Once the why is clear, the structure has to do its job.

This is the architecture I use for every change message I write.

Not because it's a formula.

Because it mirrors how humans actually process change.

Anchor the context. What's happening and why it matters now. One or two sentences. No more.

State the impact. What changes for people. Behavior, tools, expectations, day-to-day reality. This is the section most communicators rush past. Don't.

Guide the action. What people need to do, know, or pay attention to right now. Specific. Not vague. Not "stay tuned."

Offer reassurance. What support exists. Who they can go to. What the organization is doing to help them through it. This comes last, not first. Because reassurance without context doesn't land. It just sounds hollow.

Amazon's memo reversed this sequence.

It opened with reassurance and culture language before people understood what was actually changing for them. By the time the practical implications appeared, the defensive reading had already started.

Structure isn't just organization.

It's emotional pacing.

When the pyramid holds, people feel oriented before they feel anxious.

Change communication fails when it's written for everyone at once.

The instinct makes sense. A message going to 350,000 people feels like it has to cover 350,000 situations.

The result is language so broad it covers none of them.

The more useful discipline: identify the centre of gravity.

The group that feels the impact most intensely. The people who will read every word carefully, looking for what the message confirms or avoids.

Write primarily for them.

Not at the expense of everyone else.

But with enough specificity that the people most affected recognize their reality inside the message.

"This change will require some of you to relocate" was not something Amazon's memo contained clearly or early enough.

Yet that was the reality for thousands of employees.

When people encounter a message that doesn't acknowledge their situation, they don't feel informed.

They feel managed.

And managed people don't adopt change. They resist it.

One of the quieter failures in Amazon's RTO communication was the absence of ongoing dialogue.

The decision was made without employee voices in the process. With no feedback loop and no credible channel for employees to be heard, the memo had no relational foundation to stand on.

This is what most organizations get wrong about change communication.

They treat it as an event.

An announcement. A memo. A town hall.

Then silence until the next thing happens.

Employees don't trust sporadic communication that appears when leadership has something to say.

They trust rhythm.

Regular, honest, predictable updates that continue whether the news is good or not.

When that rhythm exists before the hard message arrives, the hard message has somewhere to land.

When it doesn't, even a well-crafted announcement falls into distrust that was already there.

Predictable beats polished. Every time.

Most organizations measure change communication by activity.

Emails sent. Click rates. Town hall attendance.

None of that measures comprehension.

The real test is simple:

Can employees explain the change in their own words?

Can they say what's changing, why it's happening, and what it means for their team — without referring back to the original message?

If they can't, the communication created activity. Not clarity.

Amazon's lack of a feedback loop after the announcement led to a wave of employees venting publicly — which is what happens when people have processed a message but haven't understood it.

They fill the gap themselves.

Publicly.
Loudly.
In ways the organization can't control.

Portable understanding, the kind that travels from employee to employee without distortion, is the real measure of whether change communication did its job.

Before your next change message goes out, ask:

Does this create clarity or just activity?

If it's the latter, it isn't ready.

Until next time,
Ana

Clarity isn’t corporate - it’s human.