Answer

What do I do if my colleagues are afraid of AI?

Answer the real question, which is almost always „is my job safe”. Say it plainly before the project starts, then show them the first version on their own work so the fear becomes a concrete opinion. Involve the person who does the task as the one who defines what correct means.

Last updated:

Separate the two fears

One is about employment and one is about competence: „will I be replaced” and „will I look stupid because I do not understand this”. The second is more common and less often voiced. It is answered by making the daily interaction ordinary, approving a draft in the email client they already use, with nothing new to learn.

Let them test it before it goes live

Run the first version on last month's real cases and let the team compare the output with what actually happened. They will find errors, and that is the point: finding an error converts scepticism into ownership faster than any presentation, because now it is their correction in the system.

Do not oversell it

Calling it a revolution creates an expectation the first week will not meet, and the first visible error then confirms everyone's doubts. Describing it as a tool that prepares work for review is both accurate and easier to live up to.

Asked next

Should we involve everyone or just the process owner?

The people who do the task daily, plus whoever approves. A wider audience slows the project and adds opinions from people who will not use it.

What if someone is genuinely at risk?

Say so directly and early, and offer the move into the work that is growing. Pretending otherwise is found out at go-live and costs you the rest of the team's trust.

Similar solutions

Related terms

Related questions

Related services

Have a process like this? Tell us about it.

Book a call