{"id":174,"date":"2026-06-01T12:39:59","date_gmt":"2026-06-01T12:39:59","guid":{"rendered":"https:\/\/solucom.si\/?p=174"},"modified":"2026-06-02T14:57:03","modified_gmt":"2026-06-02T12:57:03","slug":"when-to-automate-a-process","status":"publish","type":"post","link":"https:\/\/solucom.si\/en\/quando-automatizzare-un-processo\/","title":{"rendered":"How to understand if a process can be automated (and when it's not advisable)"},"content":{"rendered":"<p>There's a mistake I often see companies make as soon as they discover automation: <strong>to automate everything<\/strong>. It's the fastest way to end up with ten fragile streams that no one controls, more problems than before, and the feeling that \u00abautomation doesn't work.\u00bb The truth is another: automation works just fine, but only on the right things. This article is precisely for you to understand, pen and paper in hand, what the right things are. <em>for you<\/em>.<\/p>\n\n<h2>Premise: Automating everything is a mistake<\/h2>\n<p>Every automation has a hidden cost: it has to be built, tested, documented, and above all <strong>kept<\/strong>. A workflow that handles something rare or constantly changing will cost you more time than it saves. The goal isn't \u00abhow many things I automate,\u00bb but \u00abhow much time and how many errors I remove, stably.\u00bb Fewer, well-chosen workflows always beat many randomly implemented workflows.<\/p>\n\n<h2>Activity, process, system: three different things<\/h2>\n<p>Before deciding what to automate, you need to know <em>What<\/em> You're watching. There are three levels:<\/p>\n<ul>\n<li><strong>Activity<\/strong>: a single action. \u00abCopy contact data to CRM\u00bb.<\/li>\n<li><strong>Process<\/strong>: a sequence of connected activities towards a goal. \u00abFrom initial contact to the sent quote.\u00bb.<\/li>\n<li><strong>System<\/strong>The set of processes and the tools that make them work together. \u00abHow the entire commercial side functions.\u00bb.<\/li>\n<\/ul>\n<p>Why does this distinction matter? Why <strong>It's better to automate starting with individual tasks within a process<\/strong>, not the \u00absystem\u00bb as a whole. Those who try to automate \u00aball of sales\u00bb get stuck; those who automate \u00abnotifications when a lead arrives\u00bb achieve results within the same week. Think big about the process, but act small regarding the task.<\/p>\n\n<h2>The Four Questions Test<\/h2>\n<p>For every activity you are evaluating, ask yourself these four questions. The more \u00abyes\u00bb answers you gather, the better candidate it is.<\/p>\n<ul>\n<li><strong>Is it repetitive and does it follow clear rules?<\/strong> If you always do it the same way and could explain it to a new colleague in two minutes, it's automatable. If it \u00abdepends\u00bb every time, it's less so.<\/li>\n<li><strong>Does it happen often enough?<\/strong> Something that happens every day is worth the effort. Something that happens twice a year, almost never is.<\/li>\n<li><strong>3. Is the starting data already digital and sorted?<\/strong> If the information is already in an email, a form, or a management system, you're halfway there. If it's on sticky notes or in people's heads, it first needs to be organized.<\/li>\n<li><strong>4. What happens if they make a mistake?<\/strong> If an error is small and recoverable, you can automate with peace of mind. If an error is costly or difficult to fix, more checks are needed\u2014or perhaps it's better to let it go.<\/li>\n<\/ul>\n<p>Note how these questions measure four specific things: <strong>repeatability, frequency, data quality, and risk<\/strong>. Keep them in mind, because they return in the final exercise.<\/p>\n\n<h2>Two concrete examples<\/h2>\n<p><strong>Good example \u2014 appointment confirmation.<\/strong> A client books, and you send a confirmation email with the location, time, and instructions. It's repetitive, happens often, the data is already in the booking form, and an error is minimal (at most you correct an email address). Four \u00abyeses\u00bb out of four: automate it immediately.<\/p>\n<p><strong>Misleading Example \u2014 Responding to Important Complaints.<\/strong> It seems automatable (\u00aba complaint arrives, I send a response\u00bb), but it's not really. Every serious complaint is different, requires tone and judgment, and a wrong response can make you lose the customer. Here, automation can help to <em>sort<\/em> he <em>prepare<\/em>, but the answer is written and sent by a person. He seemed like a good candidate: in an honest exam, he is not.<\/p>\n\n<h2>The mini-matrix for deciding<\/h2>\n<p>If you don't want to reason case by case, this grid gives you the direction in three lines:<\/p>\n<ul>\n<li><strong>Frequent + repetitive + low risk \u2192 automate.<\/strong> It's the ideal territory. Start from here.<\/li>\n<li><strong>Rare + variable + high risk \u2192 don't start there.<\/strong> So much effort, little return, too much to supervise.<\/li>\n<li><strong>Frequent + variable \u2192 automates only some parts.<\/strong> Assign the mechanical tasks (picking, sorting, preparation) to automation and keep humans on tasks that require judgment.<\/li>\n<\/ul>\n\n<h2>And when does AI come into play?<\/h2>\n<p>AI is useful in automation in a specific case: when it's necessary to <strong>interpret something unstructured<\/strong>. Understand what an email is about, summarize a document, classify requests written in a thousand different ways: a fixed rule is not enough here, and AI makes the difference.<\/p>\n<p>When instead <strong>avoid it<\/strong>Where precision and predictability are needed. \u00abIf the amount exceeds 1,000 euros, ask for approval\u00bb doesn't need AI: it's a clear rule, and a rule is faster, cheaper, and more reliable. Using AI where a simple \u00abif\u00bb would suffice is a waste that also adds unpredictability. If you want to better understand the difference between a rule and <a href=\"\/en\/what-is-an-ai-agent\/\">reasoning system<\/a>, I explained it separately.<\/p>\n\n<h2>Human review: draft yes, send no<\/h2>\n<p>There's one move that makes almost every automation safer: <strong>have the machine generate the draft and leave the final action to a person<\/strong>. It is the right compromise when the risk is not negligible. Keep the human in the loop when:<\/p>\n<ul>\n<li>The communication is directed towards an important or sensitive client.;<\/li>\n<li>There is an amount, a commitment, or a deadline involved;<\/li>\n<li>the content becomes public (a post, a review, a visible reply);<\/li>\n<li>A mistake would be difficult to fix.<\/li>\n<\/ul>\n<p>In all other cases \u2014 the small, recoverable things \u2014 you can let automation run on its own. The secret is to decide <em>in advance<\/em> Where to put the control, don't find out after the first problem.<\/p>\n\n<h2>Common errors<\/h2>\n<ul>\n<li><strong>Start with the most complicated process.<\/strong> \u00abbecause that's what hurts the most.\u00bb Start with the simplest: you need a win, not a feat.<\/li>\n<li><strong>Automate a confusing process.<\/strong> If something is messy by hand, automating it just makes it messier, faster. Fix it first, then automate.<\/li>\n<li><strong>Forget the risk.<\/strong> The question \u00abWhat happens if I make a mistake?\u00bb should always be asked, even about trivial things.<\/li>\n<li><strong>Never question it.<\/strong> A useful automation today can become useless in a year. Review from time to time.<\/li>\n<\/ul>\n\n<h2>The Exercise: Your Map in 15 Minutes<\/h2>\n<p>Here is the real work, the one I really recommend you do now. Take a sheet of paper and write <strong>ten activities<\/strong> what do you (or your team) do every week. For each, give a score from 1 to 5 across four columns:<\/p>\n<ul>\n<li><strong>Frequency<\/strong>How often does it happen (5 = every day, 1 = rarely).<\/li>\n<li><strong>Repeatability<\/strong>: how much it is always the same (5 = identical every time, 1 = always changes).<\/li>\n<li><strong>Low risk<\/strong>: how harmless is it if it makes a mistake (5 = negligible error, 1 = costly error).<\/li>\n<li><strong>Little human judgment<\/strong>: how little a person's head is useful (5 = no judgment, 1 = all judgment).<\/li>\n<\/ul>\n<p>Sum the four grades. The activities with the <strong>highest score<\/strong> These are your first candidates for automation; leave the ones at the bottom where they are. In fifteen minutes, you have an organized list and a decision made with sound judgment, not just a hunch.<\/p>\n\n\n<p>understand <em>What<\/em> Automating is more important than knowing. <em>come<\/em> Do it. Start with individual, frequent, repetitive, and low-risk tasks; use AI only where there's ambiguity; keep a person in the final loop when it counts. Do this, and automation stops being a promise and becomes time back in your pocket.<\/p>\n\n\n<h2>Frequently Asked Questions<\/h2>\n\n\n<p><strong>Did you compile your top ten list?<\/strong> If you want, send me the top three activities on the leaderboard: I'll tell you, straight up, which ones are worth automating first and with what tool \u2014 sometimes that's all you need <a href=\"\/en\/n8n-automation-saves-hours\/\">a simple flow<\/a>, other times something else is needed. <a href=\"\/en\/#contatti\">Write me your three<\/a>.<\/p>","protected":false},"excerpt":{"rendered":"<p>A practical guide to deciding what to actually automate: the four-question test, a mini-matrix, when to use AI, and an exercise to map your processes.<\/p>","protected":false},"author":1,"featured_media":207,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_seopress_titles_title":"Quando automatizzare un processo (e quando no) | Solucom","_seopress_titles_desc":"Non tutto va automatizzato. Ti spiego con un test semplice quali processi conviene automatizzare e quando invece e meglio lasciar fare a una persona.","_seopress_robots_index":"","_seopress_robots_follow":"","_seopress_robots_imageindex":"","_seopress_robots_snippet":"","_seopress_robots_primary_cat":"","_seopress_robots_breadcrumbs":"","_seopress_robots_freeze_modified_date":"","_seopress_robots_custom_modified_date":"","_seopress_robots_canonical":"","_seopress_social_fb_title":"","_seopress_social_fb_desc":"","_seopress_social_fb_img":"","_seopress_social_fb_img_attachment_id":0,"_seopress_social_fb_img_width":0,"_seopress_social_fb_img_height":0,"_seopress_social_twitter_title":"","_seopress_social_twitter_desc":"","_seopress_social_twitter_img":"","_seopress_social_twitter_img_attachment_id":0,"_seopress_social_twitter_img_width":0,"_seopress_social_twitter_img_height":0,"_seopress_redirections_value":"","_seopress_redirections_enabled":"","_seopress_redirections_enabled_regex":"","_seopress_redirections_logged_status":"","_seopress_redirections_param":"","_seopress_redirections_type":0,"_seopress_analysis_target_kw":"automatizzare un processo","_seopress_news_disabled":"","_seopress_video_disabled":"","_seopress_video":[],"_seopress_pro_schemas_manual":[],"_seopress_pro_rich_snippets_disable_all":"","_seopress_pro_rich_snippets_disable":[],"_seopress_pro_schemas":[],"footnotes":""},"categories":[16],"tags":[],"class_list":["post-174","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-contenuti-automazioni"],"_links":{"self":[{"href":"https:\/\/solucom.si\/en\/wp-json\/wp\/v2\/posts\/174","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/solucom.si\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/solucom.si\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/solucom.si\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/solucom.si\/en\/wp-json\/wp\/v2\/comments?post=174"}],"version-history":[{"count":3,"href":"https:\/\/solucom.si\/en\/wp-json\/wp\/v2\/posts\/174\/revisions"}],"predecessor-version":[{"id":262,"href":"https:\/\/solucom.si\/en\/wp-json\/wp\/v2\/posts\/174\/revisions\/262"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/solucom.si\/en\/wp-json\/wp\/v2\/media\/207"}],"wp:attachment":[{"href":"https:\/\/solucom.si\/en\/wp-json\/wp\/v2\/media?parent=174"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/solucom.si\/en\/wp-json\/wp\/v2\/categories?post=174"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/solucom.si\/en\/wp-json\/wp\/v2\/tags?post=174"}],"curies":[{"name":"WP","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}