The first team conversation about AI, on one page.

The five beats, in your own words

• Name the change plainly. What the tool is, which of the team's tasks it touches, starting when. No vision language. One concrete example from your team's actual work beats any slide.
• Say what does not change. Who they report to, what they are measured on this quarter, and the standard of the work. Uncertainty fills silence; fill it first.
• Be honest about what is unknown. Roles will evolve as this lands, and you will tell them what you learn when you learn it. Said once, plainly, this builds more trust than any reassurance.
• Make the first step small and dated. One task, this week, with the tool. Not a commitment to transform. An experiment with a review date.
• Show your own use. Name the task you have moved to the tool yourself. If you have not, do that before this meeting. Teams adopt what their manager visibly does, not what their manager announces.

The four questions you will get

“Is this about headcount?”

Answer only with what you have been told is true, and name what you do not know. Do not improvise a reassurance here; a broken one costs the whole rollout. If the program has not given you an answer, take the question upward, loudly, and come back with it.

“Will this be used to raise my targets?”

The honest frame: the first quarter is for learning the tool, and this quarter's measures stand as they are. Beyond that, commit to telling them before anything about measurement changes, not after.

“I tried it and it was wrong.”

Treat it as a finding, not a complaint. Ask for the example, log it where the program can see it, and pair them with whoever on the team has made it work for the same task.

“Do I have time for this?”

Only if you make it true: name which existing task gets deprioritized during the learning window. If nothing can move, that is your escalation to the program, before pushing the team.

Three promises not to make

• “Nobody's job will change.” Jobs will change; that is the point. Promise honesty about it, not the absence of it.
• “This will make everything easier.” The first month is harder. Say so, and say what the second month buys.
• “It is optional.” If the organization has decided, softening it locally only delays the conversation and spends your credibility.