Someone on your team is already using AI.
They may be drafting emails with it. A vendor may have built it into a tool you already pay for. Or you may have announced nothing at all, and people are still wondering what it means for their role.
It is easy to buy a tool. It is easy to announce a rollout. It is harder to sit with the people who do the work and ask them what they see. If you skip that conversation, you are leading blind. Your team will fill in the blanks without you.
AI is changing how work gets done, and some of your people are wondering if their role is on the line. That is a fair question. You do not have to have the whole plan figured out before you talk about it. You do have to talk about it.
People will not tell you the truth about AI if they think the conversation is really about their job.
So start with one ground rule, and say it out loud.
No one's job is being decided in this conversation. You are naming what is true so you can plan.
You do not need a long offsite to do this. If you only have time for one conversation this week, start with three questions.
What part of your job would you happily hand off, and what part would you never want to give up?
What worries you most about AI here, and what would help you feel steadier about it?
What would you need from me to trust how we use AI as a team?
That third question is the one most business leaders skip. It is easier to talk about tools and tasks. This one puts you in the conversation. That is the point.
If you already asked it, you know what your people need from you. If you didn't, the conversation is not finished.
You can ask all ten if the room is ready. You do not have to. Three honest answers will tell you more than a packed agenda that stays on the surface.
When someone tells you what they would never hand off, do not talk them out of it. When someone names a worry, do not rush to reassure them with a tool. Thank them. Write it down. That is how the room learns it is safe to keep talking.
Then, before you leave the room, pick one small thing you could try together in the next 30 days, and put a name and a date on it.
A 30-day try is the right first move. It is not the whole plan.
Some of the work can be handed off. Some of it should stay in human hands. Think about the places people come to you because a real person shows up, listens, or makes a judgment call. Your team already knows where that line is, if you ask them.
If the conversation shows you that some of the work, or some of the people, are more exposed than a small experiment can cover, that is the moment to map it on purpose. That is the work of a 30-minute AI Exposure Audit: we map where AI hits your team's work first, and we name your top priorities, so you can use AI without losing your team's trust.
You do not need that meeting to start, though. You need a better conversation with your team.
I put these ten questions, plus a few low-risk ways to start, into a free PDF for business leaders. Enter your email at kccupp.com/10-questions and I will send it to you.
Ask the questions this week. Write down what you hear. Your team would rather have that conversation with you than guess about what is coming.