When the honest answer is to leave it alone
Not everything should be automated. Some of the most important work in an organisation is the part a person has to do. Knowing the difference is the job.
Most of what is written about automation assumes the question is how much of it you can have. We think the more useful question is where it has no business being, because getting that wrong costs far more than getting it slightly slower.
There is work that is genuinely repetitive, where a person adds nothing by doing it themselves, and handing it to a system gives them their attention back. And there is work that looks similar on a process map but is not the same thing at all, because the point of it is that a person did it.
The clearest example is the first reply to someone in difficulty. A charity supporter reaching out at a hard moment, a client whose project has gone wrong, a person making contact because something matters to them and they are not sure they will be heard. The words can be near identical to an automated equivalent. The effect is not. People can tell when the thing that reached them was sent rather than written, and at the wrong moment that distinction does real damage.
Part of my job is telling you where automation does not belong at all, even where it could technically be done and would technically save time. The saving is not worth what it costs you.
This is the part of the VTA Framework we hold under Trust. The test is not only whether a thing works, but whether the people on the other side of it would still trust you if they knew exactly how it worked. If automating a step would quietly change what someone receives from you, in a way they would mind, that step stays with a person. Automation earns the routine. People keep the moments that carry weight.
The reassuring thing, for anyone worried that caution means missing out, is that drawing this line clearly is what lets you automate the rest with confidence. Once the human moments are protected and named, the genuinely repetitive work can be lifted off your team without anyone losing sleep over it. The restraint is not the opposite of the benefit. It is the thing that makes the benefit safe to take.
Get in touch
Have a question about this post or want to explore working together? Your enquiry will be linked to this content.
