SA/01 Self Aware
AI & Change Leadership Apr 1, 2026 3 min read

The Reassurance Trap: What Your Team Needs to Hear About AI

When your team asks what AI means for their work, reassurance is tempting.

Abstract technical line-art illustration of a circuit board, symbolizing the internal processing behind an integrity hangover after staying silent in a meeting.

When your team asks what AI means for their work, reassurance is tempting.

“It is here to help, not replace you.”
“Nothing is changing right now.”
“We are just exploring ways to work smarter.”

Those statements may be true. They may also be more certain than you have any right to be.

The leadership failure is not feeling anxious about AI. It is using confidence to cover what you do not know. That performance can make a difficult conversation easier for you in the moment. It leaves your team to work out the implications on their own.

Reassurance can become a way to manage the room

A broad announcement about AI might describe innovation, efficiency, or new opportunities. The questions employees bring to their managers are usually more specific: What tasks will change? Who decides? What does this mean for my responsibilities? Is anything about my role settled?

These are different questions. A tool may make one task faster without resolving what happens to the rest of the work—or how responsibilities will be divided. Technical adoption and role changes are related, but they are not the same conversation.

When you answer both with a polished phrase about “augmentation, not replacement,” you may be trying to create calm. You may also be trying to escape the discomfort of saying, “I do not know yet.”

That is understandable. Managers are often expected to explain decisions they did not make and cannot fully predict. You may have limited information, confidentiality obligations, or no authority over what the organization decides. Candor does not require you to speculate, disclose what you should not, or turn your own anxiety into a burden for the team.

It does require you to distinguish what is known from what is still undecided.

Be precise about the uncertainty

“I do not know” is honest, but it can leave people wondering whether anyone is paying attention. Give the uncertainty boundaries.

You might say: “We are testing this tool for these tasks. We have not decided whether or how responsibilities will change. I cannot promise what the final arrangement will be. I can tell you what we are evaluating, what questions are still open, and when I expect to have an update.”

Only say what is true. If you do not know when there will be an update, do not invent a date to make the answer feel complete. If a decision is outside your control, say so plainly. A promise made to quiet the room is still a promise your team may rely on.

Then make room for the questions that a software demo does not answer. Ask what parts of the work people think may change, what the tool handles poorly, and what they need clarified. Listen without treating every concern as resistance—or every concern as proof that something is wrong.

Your team can help test how a tool performs in actual work. That does not mean they control the organization’s decisions or can be promised a say in every outcome. Be clear about what they can evaluate and what remains someone else’s decision.

Do not confuse calm with clarity

A quiet meeting is not necessarily a resolved one. But you cannot assume that silence means people are hiding something, either. Your job is not to read minds. It is to make it possible to ask a direct question without answering it with a slogan.

Separate the practical from the personal. Answer what the tool does, what is being tested, and what standards apply. When the question is about job security or future responsibilities, do not substitute a product explanation for an answer about the role. If you cannot answer, say what you can—and name the limit.

And do not mistake honesty for unloading. Your team does not need every anxious thought you have about a changing technology. They need an account of what you know, what you do not know, and what you are responsible for doing next.

You may not be able to give people certainty. You can refuse to manufacture it.

That is a less comforting promise. It is also one you can keep.

The newsletter

One honest leadership email.

A new essay and a question worth sitting with. Free. 13,000+ leaders read it.