Process automation is getting a sequence of work to happen without somebody doing each step by hand.<\/strong><\/p>\n An order arrives, so stock is checked, the customer is verified, a delivery is created, and accounts are notified.<\/p>\n That sequence exists in every business.<\/strong> The question is whether it runs because somebody remembers, or because the system makes it happen.<\/p>\n Three things it gets confused with.<\/strong><\/p>\n Not a tool.<\/strong> RPA, workflow tools and AI are ways of automating. The process comes first<\/strong>, and picking a tool before understanding the process is the most common expensive mistake.<\/p>\n Not the same as digitising.<\/strong> Moving a paper form to a screen is useful and it is not automation. Somebody still does every step.<\/p>\n Not the same as speed.<\/strong> A bad process running faster is a bad process running faster.<\/p>\n You cannot automate a process you cannot describe.<\/strong><\/p>\n And most companies cannot describe theirs accurately.<\/strong><\/p>\n Why:<\/strong> the written procedure describes what should happen. The actual process includes exceptions people handle without noticing \u2014 the customer who always pays late, the supplier who ships short, the month the file arrives on a different day.<\/p>\n Those exceptions are where automation projects fail<\/strong>, because they were never in anyone’s description.<\/p>\n Which makes the first step non-technical:<\/strong> watch the work being done, several times, by more than one person.<\/p>\n FIGURE 1: WHAT HAS TO BE TRUE FIRST<\/p>\n The process is described accurately<\/p>\n People agree on it<\/p>\n It is worth doing at all<\/p>\n Somebody will own it<\/p>\n Should this process exist?<\/strong><\/p>\n Automating a step nobody needs makes it cheaper to do something pointless.<\/strong><\/p>\n Three questions worth asking of any process before automating it:<\/strong><\/p>\n Why does this step exist?<\/strong> If the answer is “we’ve always done it”, investigate.<\/p>\n Who uses the output?<\/strong> A report nobody reads should be deleted, not automated.<\/p>\n What would break if we stopped?<\/strong> Sometimes nothing.<\/p>\n Removing three of eight steps often saves more than automating all eight<\/strong> \u2014 and costs nothing to maintain afterwards.<\/p>\n Four characteristics. The more it has, the better it automates.<\/p>\n Repetitive.<\/strong> It happens often. Daily or weekly, not twice a year.<\/p>\n Rule-based.<\/strong> The steps follow from the inputs, without judgement.<\/p>\n Structured input.<\/strong> Data in a consistent form, in a known place.<\/p>\n Stable.<\/strong> It is not changing every month.<\/p>\n And one that matters as much:<\/strong> somebody will own the result.<\/strong> An automation with no owner breaks quietly and stays broken.<\/p>\n Judgement at the centre.<\/strong> If the core of the task is a decision, automate the gathering and leave the decision.<\/p>\n High variety, low volume.<\/strong> Every case different, few cases.<\/p>\n Unstable.<\/strong> A process changing monthly will need reworking monthly.<\/p>\n Undocumented and contested.<\/strong> If two departments disagree about how it works, that is not a technology problem.<\/p>\n FIGURE 2: SUITABLE AND UNSUITABLE<\/p>\n Automates well<\/p>\n Does not<\/p>\n Partial automation is often the better answer<\/strong>, and it is underused.<\/p>\n A process might be twelve steps<\/strong>, of which nine are mechanical and three need judgement.<\/p>\n Automate the nine.<\/strong> The system gathers, checks, prepares and presents. A person decides.<\/strong><\/p>\n Why this is frequently better:<\/strong><\/p>\n Faster to build.<\/strong> No need to encode judgement as rules.<\/p>\n More reliable.<\/strong> Fewer cases where the rules do not cover reality.<\/p>\n Safer.<\/strong> Nothing irreversible happens unreviewed.<\/p>\n And most of the time saved is in the gathering anyway<\/strong> \u2014 the decision usually takes a minute.<\/p>\n In the order you should consider them.<\/strong><\/p>\n Your existing system’s settings.<\/strong> Most business systems do more than people know. Odoo has automated actions, scheduled jobs, approval rules and reordering. A setting needs no maintenance.<\/strong><\/p>\n A workflow tool.<\/strong> For multi-step logic across systems, where both have APIs.<\/p>\n Custom integration.<\/strong> High volume, complex logic, or business-critical.<\/p>\n RPA.<\/strong> Where there is genuinely no programmatic way in.<\/p>\n AI.<\/strong> Where the input is unstructured \u2014 documents, free text \u2014 and no rule handles it.<\/p>\n Most requests are satisfied at the first or second level.<\/strong> Reaching for the last two first is how projects become expensive.<\/p>\n Before you automate anything, record the baseline.<\/strong><\/p>\n Time.<\/strong> Minutes per run, runs per month.<\/p>\n Errors.<\/strong> How often the manual process goes wrong.<\/p>\n Delay.<\/strong> How long from trigger to completion.<\/p>\n Afterwards, compare \u2014 including maintenance time.<\/strong><\/p>\n That last part is what people leave out<\/strong>, and it is the difference between a real saving and an apparent one.<\/p>\n A rough guide:<\/strong> if the annual saving is not several times the annual cost including maintenance, it is marginal. Marginal automations get abandoned<\/strong> when whoever built them leaves.<\/p>\n FIGURE 3: THE SEQUENCE<\/p>\n Watch the work<\/p>\n Question the steps<\/p>\n Choose the lightest tool<\/p>\n Measure against a baseline<\/p>\n Automating an undocumented process.<\/strong> Halfway through, you discover it is not what anyone described.<\/p>\n Automating a process nobody questioned.<\/strong> Faster, in the same wrong direction.<\/p>\n Picking the tool first.<\/strong> Then fitting the process to the tool.<\/p>\n No owner.<\/strong> Something changes, it breaks, nobody fixes it.<\/p>\n Silent failure.<\/strong> Nobody notices for weeks, and by then you cannot reconstruct what was missed.<\/p>\n No baseline.<\/strong> Nobody can say whether it helped.<\/p>\n Process automation is getting a sequence to run without somebody doing each step<\/strong> \u2014 and the process comes before the tool.<\/p>\n You cannot automate what you cannot describe<\/strong>, and most written procedures leave out the exceptions where automation fails.<\/p>\n Ask whether each step should exist<\/strong> before making it faster.<\/p>\n Automate the mechanical parts and leave the judgement.<\/strong> Partial automation is usually faster to build, more reliable, and captures most of the saving.<\/p>\n A process somebody repeats every week?<\/p>\n Get in touch. We start by watching it done \u2014 the exceptions nobody documented decide whether it can be automated at all.<\/p>\n<\/div>","protected":false},"excerpt":{"rendered":" The plain definition Process automation is getting a sequence of work to happen without somebody doing each step by hand. An order arrives, so stock is checked, the customer is verified, a delivery is created, and accounts are notified. That sequence exists in every business. The question is whether it runs because somebody remembers, or […]<\/p>\n","protected":false},"author":3,"featured_media":9489,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[27],"tags":[],"class_list":["post-9491","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-automation"],"yoast_head":"\nWhat it is not<\/h2>\n
The prerequisite<\/h2>\n
\n
\n
\n
\n
The question before any of it<\/h2>\n
What makes a process suitable<\/h2>\n
What makes it unsuitable<\/h2>\n
\n
\n
Full or partial<\/h2>\n
The tools, briefly<\/h2>\n
Measuring it<\/h2>\n
\n
\n
\n
\n
Where projects fail<\/h2>\n
Where to start<\/h2>\n
\n
The short version<\/h2>\n