Explain to people what the automation changes

Automation also changes everyday collaboration

When a repetitive step is automated, people need to know what has changed, who now monitors the result, and how to report a problem. If you introduce a change without explaining it, a colleague may continue using the old process, create a duplicate record, or assume someone has neglected the task.

Before implementation, talk with the people affected by the process. Explain what problem you want to solve, what will be automated, and which decisions will remain with people. Ask about exceptions and concerns without assuming that resistance means unwillingness to change. Someone may point out a genuine issue—for example, that the new alert doesn’t take a colleague’s availability into account.

During the pilot, agree where people should report an error and how quickly someone will respond. A clear guide should cover the usual process and what to do if the automation doesn’t run or produces the wrong output. If the change affects customers, explain whether they’ll receive automated messages and how they can request human contact, when appropriate. Communication helps set expectations, but it doesn’t replace good design or support when a real problem occurs.

A change can also affect the tone customers expect or how quickly they receive a response. Test messages for clarity and make sure recipients know whether they’re communicating with a system or a person.

What’s useful to communicate to your team before introducing automation?

Automation in Practice: Choose Tasks and Check Results

Continue the training

Enter your email address to continue the training.