Short answer
Say what it means for jobs, early and specifically, because the absence of a statement is heard as bad news. Involve the people who do the work in mapping it, since they know where the real workarounds are. Deliver into the tools they already use. And measure adoption as a deliverable rather than assuming it — a system nobody opens has failed regardless of how well it performs.
Silence is not neutral
When a company announces an automation project without addressing employment, people fill the gap themselves, and they fill it pessimistically. By the time the workshops begin, the staff whose knowledge the project depends on have concluded they are being asked to help build their own replacement.
The statement does not have to be a guarantee — guarantees you cannot keep are worse than honesty. It has to be specific about intent, and it has to arrive before the rumour does.
The people doing the work know where the value is
Workflow mapping done from the management view produces the process as documented. The process as performed includes every workaround, and the workarounds are usually where both the waste and the institutional knowledge live. You only get them from the people doing the work, and only if they are not defensive.
Deliver into where people already work
If using the system means opening another tool, adoption decays within weeks. This is not stubbornness; it is a rational response to added friction. Systems that live inside the CRM, the inbox or the ticketing tool get used. Separate portals get used briefly.
Make correction easy and visible
People trust a system they can overrule. If disagreeing with it is awkward, slow, or requires justification to a manager, they will either stop disagreeing — which removes your oversight — or stop using it. Both outcomes are worse than a slightly higher correction rate.
A team that can easily overrule the system will tell you when it is wrong. A team that cannot will simply route around it.
Treat adoption as a deliverable
Measure it, report it, and give it an owner with authority over the process rather than only over the software. A pilot that performs well technically and is used by three of twelve people has not succeeded, and the reasons will be human ones that no amount of tuning addresses.
Last updated 2026-08-05 · Koderead
Related
Apply this to your own business
Eleven questions, scored in your browser, with the arithmetic shown.
Find my AI opportunities