AI and people: from fear to trust

The technology almost always works. What makes an AI project fail is people not using it: because they are afraid of it, or because nobody explained what it is for. If the staff pull the other way, failure is certain, even with the best tool. The rule to start from is a simple one: AI takes away tasks, not people.

What you can do, in practice

01

Listen before you start

Name the fears, openly: “will it replace me?”, “I won't be able to use it”, “what is it for?”. A fear said out loud can be dealt with; an unspoken one turns into resistance.

02

Let the owner do the talking

The first meeting with the team is run by whoever leads the company, not by the consultant. They explain why, and never present AI as a way to cut costs. The words of the first meeting stick for months.

03

Start with a small pilot

One boring task, chosen by the team, with a result you can see within a few weeks. “Let's try it together on a case you choose” works better than “from Monday we use this tool”.

04

Say where the freed-up time goes

It is the first question people ask themselves. Two hours a week saved by ten people add up to over 900 hours a year: more time for customers, for reading the numbers, for projects stalled for years. The destination has to be stated before you start, or those hours get scattered or turn into fear.

05

Train with dedicated time

“Learn it yourselves, it's easy” does not work. You need hours set aside in the calendar, real cases and an in-house person to ask.

06

Leave the last word to people

AI prepares and proposes; the person checks, decides and signs off. A few clear rules on what is allowed and what is not are enough.

07

Different people, different approaches

The enthusiasts become the point of reference for colleagues. With the sceptics you start from their problems and show results, not promises. With the worried you clarify their role straight away and involve them in choosing the pilot. The long-serving experts are the most valuable: without their knowledge AI stays generic, and turning it into shared procedures gives them the recognition they deserve.

Where to start

A 90-day path. In the first 30 days you listen: interviews with the team, a map of the processes, the choice of two or three repetitive tasks. From day 31 to 60 you run the pilot, with a small group and training on the job, measuring the hours saved. From day 61 to 90 you roll out: shared usage rules and other departments. Every stage has a result you can measure.

How I can help

  • I run the interviews with the team and bring fears and resistance to the surface, before they become a problem.
  • I prepare the first meeting with the owner: what to say, what to avoid, where the freed-up time will go.
  • I choose the pilot together with the people who will use it and train them on the job, on their own real cases.
  • I leave clear usage rules and an in-house point of reference who supports colleagues.

Want to find out what can be done in your company?

A first half-hour chat, no strings attached: you tell me how you work and I'll tell you where AI can deliver a concrete result, and where it isn't worth it.