Essay 03

When your people are afraid AI will take their jobs

Your people have read the same headlines you have. Some of them are quietly wondering whether the AI project you mentioned is the first step toward replacing them, and most of them will not ask you directly.

That worry is reasonable. It is also the biggest practical obstacle to getting anything useful out of AI, because the people who are worried are the same people who know where the work actually breaks.

Treat it as a trust problem, not a messaging problem. A well written memo does not fix it. What you do over the next few months does.

Do not promise what you cannot keep

The tempting move is to stand up and say nobody's job will change. It feels kind. It is usually not true, and people know it. The first time a role shifts, that promise becomes the thing everyone remembers.

Say something you can keep instead. The work will change, some tasks will go away, and if a role changes you will tell people early, explain why, and give them a real chance at the new version of the job before anything else happens. Then do exactly that.

Talk before the project, not after

People fill silence with the worst version. If the first they hear of AI is a new tool appearing in their inbox, they will assume the plan was made without them and the decision is already final.

Talk to the team before the first process changes. Keep it short and plain:

• What you are trying to fix, in terms of the work. The report that takes a day to rebuild. The requests that sit too long.
• What you are not doing. If this project is not about cutting the team, say so, and be specific about what the project covers.
• How they will be involved. The people who do the work help decide what the tool takes and what they keep.
• What happens if a role does change. Early notice, an honest reason, the first chance at the new role.

Then ask what worries them, and listen without arguing.

Let the people closest to the work shape it

The most useful thing you can do for trust is let the people doing the work shape the change. Ask them which parts of their week are the most tedious. Those are often exactly the steps AI handles well, and when the idea comes from them, the change feels like relief instead of a threat.

Let them try the tool on their own tasks before anything changes officially. Let them say where it falls short. When their objections change the plan, tell them so, by name.

Watch what you reward

People believe what they see, not what they are told. If the first person who finds a way to save time with AI ends up with a worried look and an uncertain future, everyone else learns to keep quiet. If that person gets more interesting work, credit, and a say in the next process, everyone learns that helping is safe.

Be careful how savings are discussed in meetings. If every conversation about AI ends with a cost figure, people will hear headcount, whatever you meant.

Signs the fear is still there

• People say the tool is fine in meetings, and nobody uses it.
• The old spreadsheet quietly comes back.
• Questions stop. Silence is not agreement.
• Good people start looking elsewhere.

If you see these, go back to the conversation. Ask directly. Say again what you will and will not do, and point to where you have already kept your word.

When you do not know yet

Sometimes you cannot say what will happen to a role, because you have not decided. The honest answer is: I do not know yet, here is how I will decide, and here is when you will hear. People can live with uncertainty. What they struggle with is being kept in the dark.

On Monday

Before you change any process, write three sentences you can say to your team and keep: what you are trying to fix, what you are not doing, and how you will treat anyone whose role changes. Read them to one manager you trust and ask whether they sound true. Then say them to the team in person.