Answer

How do I get my team to actually use the automation?

Start with the process that annoys them most, not the one that saves you most. Let the person who does the work define what „correct” means, and show the weekly numbers openly. Adoption fails when it is announced and works when the first version visibly removes something the team already complained about.

Last updated: 22 September 2026

Pick the process they complain about

Owners tend to choose the process with the best business case. The team judges the project by whether their Monday got better. These are often different processes, and starting with theirs buys you the cooperation you need for the one with the bigger number.

Let them define correct

The person who has answered those emails for four years knows which phrasing causes a complaint and which customer must never get a template. Writing those rules down with them turns the automation into their tool instead of something imposed on them, and it produces a better system.

Show the numbers, including the bad ones

A weekly figure on the wall, items handled automatically, items sent to a person, corrections made, keeps the conversation factual. Hiding the correction count destroys trust the first time someone notices an error that was not reported.

Asked next

Should we run a pilot with one team?

Yes, with the team most likely to engage. A visible success in one place spreads faster than a company-wide launch that nobody asked for.

What if adoption stalls after a month?

Look at the correction log. Stalling almost always traces back to a specific repeated error that nobody bothered to report, and fixing it restarts usage.