The build finishes, the tool works, the demo goes well. Six months later usage is a handful of people and the old spreadsheet is still circulating.
Nobody resisted it. They simply had a way of doing the job that worked, and the new way asked for something the old way did not.
What “another system” actually costs
A separate tool asks for a password, a tab, a habit and a reason to switch. Each is small. Together they exceed the benefit of a task that only took four minutes to begin with.
This is why adoption correlates so poorly with quality. A better tool that sits outside the workflow loses to a worse one that is already open. The competition is not the old tool; it is the cost of moving.
Build into the workflow
The version that gets used usually has no interface of its own:
It happens in the tool they already have. The document system, the practice management system, the inbox. If the work happens in Outlook, the automation happens in Outlook.
It triggers itself. Started by an event — a matter opened, a form submitted, a date passing — rather than by someone remembering to run it.
It delivers to where the person already looks. A report that arrives is used. A report available in a portal is not.
It leaves the existing route intact at first. Automation that removes the old way before it has earned trust makes its own failures unrecoverable, and people will not forgive that twice.
Make the good path the easy one
The strongest pattern is to make the automated route less effort than the manual one at the exact moment of choice — a form pre-filled with what is already known, a pack assembled by default with a review step, a status that updates itself so nobody has to be chased.
If the automated path is more work than the workaround, the workaround wins, and it does not matter how much better the outcome would have been.
Keep the review step
There is a temptation, particularly with anything generative, to remove the human entirely. Resist it for work with professional consequences.
A draft that a person reviews and approves is faster than writing from scratch and retains accountability. Full automation of a judgement is a small additional time saving for a large increase in risk, and the first bad outcome ends the programme.
How to tell whether it worked
Not by usage of the new tool. By whether the old artefact has disappeared — the spreadsheet, the shared inbox, the printed checklist.
If both exist, you have added a system rather than replaced a process, and the cost is now higher than before you started.
If your last automation is not being used, get in touch, or read about our professional services work.