Field note
What to tell your team the first time you introduce AI
The first conversation sets whether people lean in or quietly wait it out. Get the order right.
To introduce AI to your team, have their direct manager explain, in plain terms, which specific tasks are changing and why, address job security directly instead of avoiding it, and end with a concrete next session rather than a one-off announcement. Skipping any of those three steps is what turns a rollout into rumour.
Name who's talking
Their manager, not IT or HR
State what's changing
The task, not just the tool
Address job security first
Before anyone has to ask
Set the next session
So it's a start, not one memo
Who should actually deliver the announcement?
Not IT, and not a company-wide email from leadership alone. The message should come from each person's direct manager, in a team meeting where questions are allowed. Routing an AI announcement through the tech team signals this is a systems update. Routing it through the person someone already trusts with their workload signals it is about how the work itself is changing, which is the truth.
What should the first message actually say?
Name the specific task, not the tool. "We're using AI to draft the first pass of client update emails" lands. "We're rolling out an AI initiative" does not, because nobody can picture what changes on Monday. Say what stays the same too: who still owns the final decision, what still gets checked by a person, what nobody is being asked to hand over blind.
How do you address job security without dodging it?
Say it before anyone has to ask. Silence on the job question does not read as reassuring, it reads as confirmation that leadership has not thought it through or does not want to answer. If the honest answer is that no roles are changing, say that plainly. If some work will genuinely shift, say what and over what timeframe. A team that hears an honest version of a hard answer trusts the next announcement more than a team that got a vague one.
What comes after the announcement matters more than the announcement
A single meeting with no follow-up is where most rollouts stall, because people file it as a thing that was mentioned rather than a thing that is happening. Close the first conversation with a specific next step already on the calendar: a hands-on session on the actual task named in the announcement, not a generic training deck. That is what turns the announcement into the start of something instead of the whole of it.
Even where a company has actually adopted AI, a meaningful share of the team has no idea it happened, which is the direct cost of treating the rollout as a memo instead of a real conversation.
The takeaway
Before you announce anything, write down the one task that is changing, the one thing about job security you will say without being asked, and the date of the follow-up session. If you cannot fill in all three, you are not ready to announce yet.