How to tell your people what AI will change about their jobs. · VANDAM

This page as Markdown llms.txt llms-full.txt services.json sitemap.xml
# How to tell your people what AI will change about their jobs. · VANDAM

> How CEOs and CHROs should tell employees what AI changes: what Amazon and Duolingo show, the trust data, a six-step sequence and what never to promise.

URL: https://vandam.ai/notes/telling-your-people  
Contact: hendrik@vibelab.be

# How to tell your people what AI will change about their jobs.

Most employees can see AI arriving, and only a quarter say their employer has explained a plan. What silence and shifting explanations cost, a communication sequence for the CEO and CHRO, and what never to promise.

Hendrik De Winne 25 October 2026 8 min read

On June 17, 2025, Andy Jassy sent Amazon’s employees a memo about generative AI. It was candid. “We will need fewer people doing some of the jobs that are being done today,” he wrote, and “more people doing other types of jobs.” Over the next few years, he expected AI to “reduce our total corporate workforce.” He even admitted what he did not know: “It’s hard to know exactly where this nets out over time.” You can read it on [About Amazon](https://www.aboutamazon.com/news/company-news/amazon-ceo-andy-jassy-on-generative-ai).

Four months later, Amazon cut about **14,000** corporate roles. The message from Beth Galetti, who runs people experience and technology, explained the cut through layers and bureaucracy, and added that “this generation of AI is the most transformative technology we’ve seen since the Internet,” according to [Amazon](https://www.aboutamazon.com/news/company-news/amazon-workforce-reduction). Two days later, on the earnings call, Jassy told analysts the cut was “not really financially driven, and it’s not even really AI-driven, not right now at least. Really, it’s culture,” as [GeekWire](https://www.geekwire.com/2025/its-culture-amazon-ceo-says-massive-corporate-layoffs-were-about-agility-not-ai-or-cost-cutting/) reported. In January 2026 came another **16,000** roles, with a [message](https://www.aboutamazon.com/news/company-news/amazon-layoffs-corporate-jan-2026) that did not mention AI at all and answered the obvious fear directly: some employees might ask whether broad reductions every few months were the new rhythm. “That’s not our plan.”

Each of those messages can be defended on its own. Read in sequence by someone who works there, they say four different things about why jobs are going. I start with Amazon because it is a company with every resource for internal communication, and it still produced the pattern I see in mid-sized firms: an honest first message, followed by explanations that drift. Employees keep the first one and judge everything after it against that.

- **52%**
  US workers who feel worried about future AI use in the workplace, per [Pew](https://www.pewresearch.org/social-trends/2025/02/25/workers-views-of-ai-use-in-the-workplace/), surveyed October 2024.
- **25%**
  US employees who say their organization has communicated a clear plan for AI, per [Gallup](https://www.gallup.com/699797/indicator-artificial-intelligence.aspx), May 2026.
- **66%**
  Employees who trust their own CEO, down from 70% and a record low, per [Edelman](https://www.edelman.com/newsroom/richard-edelmans-6am-blog/trust-at-work-2026), October 2026.
- **18%**
  Employees with a negative transformation experience who would embrace more AI at work, against 40% after a positive one, per [Edelman](https://www.edelman.com/newsroom/richard-edelmans-6am-blog/trust-at-work-2026).

## Most employees have heard nothing they can use

The worry is broad and it predates most of the memos. When [Pew Research Center](https://www.pewresearch.org/social-trends/2025/02/25/workers-views-of-ai-use-in-the-workplace/) surveyed 5,273 employed Americans in October 2024, **52%** said they felt worried about how AI will be used at work and **36%** felt hopeful. **32%** expected fewer job opportunities for themselves in the long run, and only 6% expected more. Lower-income workers were the most pessimistic. Use was still thin: by September 2025, about **21%** of workers said at least some of their work was done with AI, up from 16% a year earlier, per a [Pew follow-up](https://www.pewresearch.org/short-reads/2025/10/06/about-1-in-5-us-workers-now-use-ai-in-their-job-up-since-last-year/). So most people form their view of AI at work from headlines about other companies.

Their own employer rarely fills the gap. In [Gallup’s](https://www.gallup.com/699797/indicator-artificial-intelligence.aspx) May 2026 reading, **47%** of US employees say their organization has integrated AI, and only **25%** say it has communicated a clear plan. That leaves a large group of people who can see the tools arriving and have been told nothing about what they mean for their job.

Edelman’s 2026 [Trust at Work](https://www.edelman.com/newsroom/richard-edelmans-6am-blog/trust-at-work-2026) study, published this month from a survey of more than 10,000 employees in ten markets, shows what that silence lands on. AI implementation is now the most common transformation employees report, at **53%**. Three quarters of workers fear losing their job to tariffs, automation, offshoring or a lack of training. Trust in “my CEO” fell from 70% to **66%**, and trust in direct managers from 79% to 72%, each a record low in Edelman’s series. Associates were roughly three times as likely as executives to call their experience of the change less than positive, 49% against 17%. The people deciding and the people affected are living through different events.

## Uncertainty does more damage than bad news

The research on this is older than generative AI, and it is consistent. In a field experiment published in 1991, [David Schweiger and Angelo DeNisi](https://doi.org/10.5465/256304) followed two plants of a company that had just announced a merger. One plant received what they called a realistic merger preview, a program of frank and regular communication about what would happen. The other received limited information. Across four rounds of measurement, the preview reduced the damaging effects of the merger, and in some cases attitudes returned to where they had been before the announcement. Both plants went through the same merger, and the plant that heard about it early and often from the company came through it in better shape.

The cost of getting it wrong shows up in who leaves. [Charlie Trevor and Anthony Nyberg](https://doi.org/10.5465/amj.2008.31767250) studied organization-level data across industries in 2008 and found that downsizing predicts higher voluntary turnover among the people who stay, through lower commitment. HR practices that convey procedural fairness or tie people to the organization softened that effect. My reading, which goes beyond their data: the people who leave voluntarily are the ones with options, and in an AI transition those are usually the people already doing the most with the tools.

Edelman’s new numbers say the same about AI specifically. Employees with a negative experience of transformation were less than half as likely to embrace more AI at work, **18%** against **40%**. Commitment to a long-term career at the company was 51% after a negative experience and **83%** after a positive one. A badly communicated rollout makes the next rollout harder, because the people you need to adopt it have stopped believing you.

## Broken promises do the most damage

Most damage comes from a promise or an explanation that later turns out to be incomplete. Duolingo is the clearest case. Luis von Ahn’s April 2025 “AI-first” memo said the company would gradually stop using contractors for work AI could handle, as [Fortune](https://fortune.com/2025/06/09/duolingo-ceo-surprised-backlash-ai-first-company-announcement/) reported. Readers outside the company heard layoffs. Months later he was still correcting the record.

> We’ve never laid off any full-time employees. We don’t plan to.
>
> Luis von Ahn, CEO, Duolingo, August 2025, [Source](https://fortune.com/2025/08/18/duolingo-ceo-admits-controversial-ai-memo-did-not-give-enough-context-insists-company-never-laid-off-full-time-employees)

Look at the second sentence. It is the kind of line every CEO is tempted to say, and the one that costs the most if circumstances change. Amazon’s “That’s not our plan” has the same shape. Both are probably sincere. Neither is a commitment a CEO fully controls, because markets, models and boards move. The memos from Shopify and Duolingo about AI use, which I wrote about in [an earlier note](https://vandam.ai/notes/tinkerers), ran into a related problem: when the message is mainly an instruction to use AI, people start asking what the instruction is really for.

The CEOs who did this better, in my reading, did two things. They said plainly which part was uncertain, as Jassy did in June. And they kept the explanation stable afterwards. Amazon’s June memo would have aged well if October and January had repeated its logic. The memos went wrong in the follow-up.

## A communication sequence that holds up

This is the order we use with clients. It assumes a CEO and a CHRO doing it together, with the CFO in the room for the first step.

1. **Before saying anything, write three lists.** What we know (which tasks agents already do, in which teams), what we have decided (budget, tools, the first roles to be redesigned), and what we have not decided (headcount, timing, which roles shrink). The third list is the one most leadership teams skip, and it is the one employees care about. If headcount reduction is on the table, it goes on that list honestly.
2. **Week one: the CEO tells everyone at once, in person or live.** Give the business reason in terms of competitiveness and customers. Edelman reports that employees see change as justified by outcomes like competitiveness and survival, and much less by shareholder value. Read out all three lists. End with the date of the next update.
3. **Within 48 hours: every manager holds a team conversation.** Give them a one-page brief and the three lists the day before the CEO speaks. [Gallup](https://www.gallup.com/workplace/712433/employee-engagement-remains-flat-adoption-accelerates.aspx) finds engagement of 48% among employees whose manager actively supports AI use against 30% among those whose manager does not, and **53%** when frequent use, a clear plan and active manager support come together. The manager is the channel people believe.
4. **First month: role-by-role conversations.** For each role, write down which tasks move to agents, which new tasks arrive, what training comes with it and who decides. Then talk to the people in that role before the description is final. This is where the redesign work from [the org chart note](https://vandam.ai/notes/org-chart-redrawn) meets real people.
5. **Monthly: update on the date you promised.** Even when nothing changed. Start each update with what you said last time and what actually happened. Move items from “not decided” to “decided” in public. A steady cadence does more for trust than any single speech.
6. **If roles go, say it once, with the real reason, and keep it.** State the criteria, the notice, the support and the internal options. Amazon’s 90 days to look for an internal role is a mechanism worth copying. Then give the same explanation to analysts, press and staff, because they compare notes.

What never to promise: that no jobs will be lost, that a given role will stay as it is, a date you do not control, or a reason you might contradict next quarter. What you can promise and keep: how decisions will be made, how much notice people get, that the people affected will be consulted first, that they get training before the switch, and first look at new internal roles.

## What to do this month

Sit down with your CHRO and write the three lists for your own company, on one page. If the “not decided” list is empty, you have probably decided more than you have told anyone, or less than you think.

Then make a second list of the twenty people you can least afford to lose, especially the ones already doing the most with AI. Have each of their managers talk with them within two weeks about what their job becomes, before the all-hands. They are the first to hear the rumor and the first to get a call from a recruiter.

Finally, put the first all-hands and the next three monthly update dates in the calendar now, and send the dates to the whole company. The calendar invite is the first promise, and it is one you can keep.

## More notes

29 October 2026 6 min read

## Who owns what your AI learns.

Y Combinator now asks for startups that help companies own their intelligence. Before a mid-sized company owns a model, it can own the four things every model works with: context, evals, rules and connections.

26 October 2026 9 min read

## Delete the step first and give the agent whatever survives.

Musk’s five-step method puts automation last, and most AI programs start there because an agent is the one step a vendor can sell. I walk accounts payable through the steps in his order and show why an agent that clears exceptions fast hides the steps that should go.

## Your agents need a critic and so does the plan they carry out.

Models grade their own work too kindly, and the labs now separate the agent that makes from the agent that checks, the way finance separates maker and checker. I set out a four-layer review design with a minutes budget, and why the brief itself needs a critic with no stake in it.