Insights
What I see in projects, the questions they raise, and what I learn from them.
-
Automation
Why an automated process needs to be understood before it is built
When faced with a slow process, the temptation is to jump straight to the technical solution. Write the script, connect the systems, deliver quickly. This approach rarely works first time and often costs more than expected because an essential step has been skipped: understanding the real process before turning it into an automation.
-
Automation
How to recognise a task worth automating, and one that isn't
Not every repetitive task is worth automating. Some take time, but happen too rarely, vary too much or are too complex to formalise to justify the investment. Others could be automated, but only after simplifying the process around them. Knowing the difference helps avoid spending an automation budget in the wrong place.