The fear is almost always concrete: will my work become redundant? That deserves an honest answer.
You can remove resistance to AI by first identifying the real concern: usually job security: and giving an honest answer. Then you help by involving the team in which work is taken over, starting small with the most tedious work, and giving people control over the outcome.
STEP BY STEP
This is how you approach it
- State the job question firstEveryone thinks it and no one asks. Say what is true: will something change about who does what, be honest about that. Remaining vague feeds exactly the fear you want to eliminate.
- Let the team designate the workAsk which work they find most annoying and miss the least. That is almost always the work that is best automated, and it changes the perspective from something that happens to you to something that you choose.
- Start with the most boring, not the most beautifulFirst, automate the work that no one wants to do. This immediately generates goodwill and shows that the goal is not to replace people.
- Give people the last wordWhen the agent prepares and approves a human, the role shifts from executor to evaluator. That feels like an upgrade instead of a replacement.
- Also show the mistakesDon't hide what's going wrong. A team that knows the limitations trusts the system more than a team that only saw the demo.
- Measure and share the resultsHours that were released, and where they went. If the answer is 'nothing visible', that is also an outcome worth discussing.
PITFALLS
What doesn't work
Dismissing resistance as lack of progress. If people are concerned about their jobs, that is a real concern and not obsolete.
Imposing a system without participation does not work either. Those who don't participate in the decision don't use it, and then the project fails for the soft reason instead of the technical one.
- Not: putting away resistance — the concern is usually justified.
- Don't: be vague about jobs — that feeds the fear.
- Not: imposing without participation — then it is not used.
- Well: start with the most boring work — generates goodwill.
- Well: give people the last word — evaluator instead of executor.
- Do: show mistakes — that builds trust.
FREQUENTLY ASKED QUESTIONS
More about implementation
What if my team just doesn't want it?
Investigate why. If the concern is job security, then that is a conversation you have to have regardless. If it is a previous bad experience with software, starting small helps with something that demonstrably helps.
Should I say that jobs are disappearing?
If that's the plan, yes. People notice anyway, and withholding it costs you more trust than the message itself. If that is not the plan, say so explicitly: otherwise everyone will fill it in themselves.
Will you supervise the implementation?
We provide documentation and a transfer, and help you think about where to start. Guiding change processes is not our service, and for larger teams a specialist is better at this.
CONTINUE READING
Of course, continue reading about this subject.
Enter without resistance?
We start with the work that your team identifies: that works better than a top-down plan.