{"id":6147,"date":"2026-04-13T14:22:33","date_gmt":"2026-04-13T14:22:33","guid":{"rendered":"https:\/\/iwis.io\/?p=6147"},"modified":"2026-04-13T13:48:47","modified_gmt":"2026-04-13T13:48:47","slug":"5-mistakes-in-business-process-automation","status":"publish","type":"post","link":"https:\/\/iwis.io\/en\/blog\/5-mistakes-in-business-process-automation\/","title":{"rendered":"5 Mistakes in Business Process Automation That Cost Millions"},"content":{"rendered":"","protected":false},"excerpt":{"rendered":"","protected":false},"author":2,"featured_media":6115,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[],"tags":[212],"class_list":["post-6147","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","tag-212"],"acf":{"blog_custom_title":"5 Mistakes in Business Process Automation That Cost Millions","blog_featured_image":6115,"blog_custom_excerpt":"","blog_external_url":"","blog_categories":false,"blog_tags":[212],"blog_featured_post":false,"blog_content_blocks":[{"acf_fc_layout":"text_block","text_content":"
\r\n
\r\n

Back in 2011, Lidl launched a large-scale project to implement a new ERP system based on SAP. The goal was to centralize inventory management and standardize processes across the international network.<\/p>\r\n

Seven years later, the company halted the project, having previously spent about 500\u043c\u043b\u043d\u20ac. The main reason was that the system did not match Lidl's actual goods accounting logic, required a radical overhaul of internal processes, and the company was not ready to change its management model to fit the SAP architecture.<\/p>\r\n

This is not an isolated case.<\/p>\r\n

According to the Standish Group (CHAOS Report), only about 31% of IT projects are fully successful \u2013 within budget, timelines, and with expected value. The rest either exceed the budget, or fail to achieve stated goals, or are terminated altogether.<\/p>\r\n

And it is important to understand here that the problem is rarely in the technology itself. Rather, it is in the approach, because business process automation is, first and foremost, a change in the company's work logic. And if launched without a strategy, without reviewing processes, and without a measurable goal, it can easily turn into a very expensive experiment.<\/p>\r\n

This is especially relevant in the context of business automation in Ukraine, where many companies start automation implementation as a reaction to accumulated chaos, rather than as a systematic step toward scaling.<\/p>\r\n

In this article, we will break down 5 typical automation mistakes that regularly cost companies millions, and show how they can be avoided.<\/p>\r\n\r\n<\/div>\r\n

Why 30-70% of Automation Projects Fail<\/h2>\r\n

The figure looks shocking, but it regularly appears in studies by major consulting firms. McKinsey in its digital transformation reviews notes that about 70% of such initiatives fail to achieve their stated goals. Bain & Company raises the bar even higher: 88% of business transformations do not meet their initial ambitions.<\/p>\r\n

And notably, the problem is rarely technical: 72% of transformation failures are explained by managerial reasons: insufficient leadership support (33%) and employee resistance (39%).<\/p>\r\n

In Ukrainian companies, this difference is felt even more acutely: business grows quickly, processes often form evolutionarily, without formalization. At a certain point, the volume of operations exceeds the capabilities of manual management, and automation seems like an obvious solution. But if the work order has not been fixed beforehand, roles described, and control points defined, the digital system will only transfer the problem to another interface.<\/p>\r\n

Therefore, the main question is at what maturity stage the automation of business processes is launched and whether the organization is prepared for it.<\/p>\r\n\r\n

Mistake 1: Automating Chaotic Processes<\/h2>\r\n

What is the Problem<\/h3>\r\n

The most common reason for automation failure is the attempt to automate what has not been structured.<\/p>\r\n

Most digital initiatives do not create value if the company does not review its operating model before implementing technologies.<\/p>\r\n

This is particularly evident in the case of RPA. In Ukraine, interest in robotizing routine operations has been growing in recent years: business seeks ways to reduce manual labor without expanding staff. But robotization is often launched where processes are not yet standardized. As a result, the bot works with unstable data, exceptions, and manual decisions, and instead of savings, the company gets complex maintenance and constant refinements.<\/p>\r\n

Business process optimization must precede automation implementation.<\/p>\r\n\r\n

Real Case: ERP without Process Changes<\/h3>\r\n

Let's return to the Lidl case. The key problem with SAP implementation was that the ERP system operated on standard goods valuation logic, while Lidl used its own accounting model based on purchase cost.<\/p>\r\n

The important thing here is not the scale, but the mechanics of the error. The company tried to adapt the system to the existing model instead of reviewing processes before implementation. As a result, automation turned into an expensive and complex project that did not deliver the expected value.<\/p>\r\n

This is a classic example of how automation without aligning processes and systematic preparation can cost hundreds of millions. But the same happens at the level of small and medium-sized businesses, just with fewer zeros in the amount. When a company has no standardized sales funnel, clear lead qualification rules, fixed approval stages, or responsible persons for each step, CRM will only show the problem in a more structured form.<\/p>\r\n\r\n

How to Avoid This Mistake<\/h3>\r\n

The rule is simple: optimize processes first, then automate. Before implementing any tool, there are three mandatory steps.<\/p>\r\n

First: describe the process as it actually happens.<\/p>\r\n

Second: eliminate redundant steps, duplications, and points where decisions are made haphazardly.<\/p>\r\n

Third: standardize \u2013 the process must yield the same result regardless of who from the team executes it.<\/p>\r\n

A good candidate for automation is a process where the share of non-standard situations does not exceed 10-15%. If exceptional cases account for 40% or more, RPA is not just risky here; it will almost certainly create more problems than it can solve.<\/p>\r\n\r\n

Mistake 2: Choosing a Tool without Needs Analysis<\/h2>\r\n

After the company realizes it needs business process automation, the next temptation arises \u2013 to quickly select a tool. And here the lottery often begins, because they choose not what really solves the specific problem, but what sounds louder on the market or what sells best at the demo.<\/p>\r\n

But during a demo, almost any system looks convincing: it shows good scenarios where data is ideal, integrations supposedly already exist, and users click the right buttons. In real business, everything is different: data is dirty, processes vary in each department, exceptions outnumber rules, and integration with the current IT architecture turns into a separate project.<\/p>\r\n

Therefore, the correct order is always one: needs and processes first, then criteria, then the tool.<\/p>\r\n\r\n

Symptoms of This Mistake<\/h3>\r\n

How to understand that the tool was chosen without analysis, and now they are trying to attach it to the business?<\/p>\r\n

First, requirements start surfacing already during implementation. They initially wanted CRM, then suddenly complex access roles, custom directories, non-standard approval scenarios, integration with accounting, exchange with the warehouse, and also for the manager to see everything in one dashboard are needed. None of this is bad in itself, but it is bad that it was not described before the start.<\/p>\r\n

Second, the team continues to maintain the same Excel tables and messengers in parallel. The system exists formally, but real work lives outside it, because the tool does not fit the company's daily rhythm and rules.<\/p>\r\n

After 6-12 months, the thought of a wrong platform choice appears, and the cycle starts over.<\/p>\r\n

This is a direct path to the project expanding, becoming more expensive, and losing sense. Precisely undefined scope and weak requirements management are the basic triggers for scope creep.<\/p>\r\n\r\n

Example from Practice: When the Tool Was Chosen, but No Value Was Obtained<\/h3>\r\n

In 2013, Target actively entered the Canadian market and in less than two years opened over 130 stores. The ambition was huge, the infrastructure \u2013 not.<\/p>\r\n

The problem turned out not to be in the brand or marketing, but in the operational part: internal inventory management systems worked with incorrect data. Catalogs had errors, product information was duplicated or incomplete. The supply chain did not synchronize with actual demand. As a result, store shelves were often empty, while warehouses held thousands of units of unnecessary goods.<\/p>\r\n

In 2015, Target completely closed its Canadian division, writing off approximately 5.4\u0431\u043b\u0440\u0434$ in losses.<\/p>\r\n

Analysts directly pointed to systemic problems with data and IT processes as one of the key reasons for failure.<\/p>\r\n

This is a telling example of how scaling a system without real process and data audit can destroy even a global brand.<\/p>\r\n\r\n

Correct Approach<\/h3>\r\n<\/div>"},{"acf_fc_layout":"list_block","list_title":"To ensure that choosing a tool doesn't turn into a never-ending repair job, you need to:","list_type":"ul","list_items":[{"item_text":"Define a strategic goal (time savings, cost reduction, scalability, increased transparency)."},{"item_text":"Describe the key processes that the system must cover."},{"item_text":"Identify critical integrations."},{"item_text":"Calculate the total cost of ownership (including customization, training, and support)."},{"item_text":"Conduct a pilot launch in a limited area."}]},{"acf_fc_layout":"text_block","text_content":"Only then can the choice of tool be justified."},{"acf_fc_layout":"text_block","text_content":"
\r\n

Mistake 3: Ignoring the Human Factor<\/h2>\r\n

Resistance to Change in the Team<\/h3>\r\n

Any automation has a side effect that is rarely discussed at the start: it changes the distribution of influence within the company. Before CRM implementation, a manager could decide for themselves what to record and what not. After implementation, everything is visible as on the palm of one's hand.<\/p>\r\n

Before automation, approvals could be resolved through personal arrangements. After \u2013 the system tracks deadlines, responsible persons, and deviations.<\/p>\r\n

Technology creates transparency, and transparency creates tension. That is why automation implementation often stalls precisely due to the team's psychological discomfort: people resist the loss of familiar control mechanisms. And if at this stage management thinks that the team will somehow get used to it on their own, a slow, imperceptible sabotage begins: part of the processes returns to messengers, and data is entered formally or with delay.<\/p>\r\n\r\n

Lack of Training<\/h3>\r\n

Another mistake is to perceive the system launch as the final point, whereas in reality, the launch is only the beginning of the adaptation phase. And if at this moment the company does not invest in training, explaining process logic, and regular support, automation is perceived as an additional duty. Whereas it should be a tool for simplifying work.<\/p>\r\n\r\n

Staff Engagement Strategy<\/h3>\r\n<\/div>"},{"acf_fc_layout":"list_block","list_title":"Here's how it works:","list_type":"ol","list_items":[{"item_text":"First, a clear explanation of why this is being done and what problems it solves."},{"item_text":"Next, involve key staff members in the process design."},{"item_text":"Next, we need to adjust the KPIs so that the new system becomes an integral part of our day-to-day operations."},{"item_text":"And only after that zoom."}]},{"acf_fc_layout":"text_block","text_content":"Automation needs to be integrated into the performance evaluation and management system."},{"acf_fc_layout":"text_block","text_content":"
\r\n

Mistake 4: Lack of Results Measurement<\/h2>\r\n

There is a strange thing that often happens with automation: the company invests in a system, spends months on implementation, and if asked what exactly changed, the answer sounds vague. Business process automation should primarily impact the numbers.<\/p>\r\n

If you do not know exactly what should change in the numbers, you cannot assess whether anything has changed at all.<\/p>\r\n

This is like building a new route without knowing how you traveled before and how much time the road took: you try to plot the path, but cannot say whether it became faster or just different.<\/p>\r\n\r\n

KPI for Automation<\/h3>\r\n

Before implementation, you need to fix the baseline. For different types of processes, these can be different metrics:<\/p>\r\n

Sales: lead processing time, conversion between funnel stages, number of deals per manager, average deal cycle.<\/p>\r\n

Operational processes: document approval time, number of manual operations, error frequency, cost per transaction.<\/p>\r\n

Financial processes: month-end closing time, number of manual adjustments, share of operations requiring reprocessing.<\/p>\r\n

The point is to select 3-5 key metrics that truly reflect value.<\/p>\r\n\r\n

How to Calculate ROI for Automation<\/h3>\r\n<\/div>"},{"acf_fc_layout":"list_block","list_title":"The ROI of automation typically consists of two components:","list_type":"ol","list_items":[{"item_text":"Direct savings: time savings, fewer errors, staff optimization, or workload redistribution."},{"item_text":"Indirect benefits: faster sales cycle, increased conversion rates, reduced lead loss, and greater transparency."}]},{"acf_fc_layout":"text_block","text_content":"The classic formula is: ROI = (Financial gain \u2013 Investment) \/ Investment \u00d7 100%\r\n\r\nLet\u2019s examine a hypothetical scenario involving the automation of lead processing in the sales department."},{"acf_fc_layout":"list_block","list_title":"Input data (for automation):","list_type":"ul","list_items":[{"item_text":"5 sales managers;"},{"item_text":"Each person handles about 200 leads per month;"},{"item_text":"15% of leads are lost (they didn't call back, weren't entered into the system, or were lost in the messaging app);"},{"item_text":"Average check: 8,000 UAH;"},{"item_text":"Conversion rate: 20%."}]},{"acf_fc_layout":"text_block","text_content":"Here\u2019s what happens every month:\r\n\r\n200 leads \u00d7 5 managers = 1,000 leads\r\n\r\n15% are lost: 150 leads. Of these 150 leads, 20% could be converted: 150 \u00d7 20% = 30 deals. 30 deals \u00d7 8,000 UAH = 240,000 UAH in lost revenue per month.\r\n\r\nAfter implementing business process automation, all leads are tracked automatically, and losses are reduced from 15% to 5%. Now 50 leads are lost instead of 150, a difference of 100 leads.\r\n\r\n100 \u00d7 20% = 20 additional deals\r\n\r\n20 \u00d7 8,000 UAH = 160,000 UAH in additional revenue per month.\r\n\r\nPer year: 160,000 \u00d7 12 = 1,920,000 UAH\r\n\r\nInvestments:\r\n\r\nDevelopment and implementation \u2013 600,000 UAH\r\n\r\nLicenses and support per year \u2013 240,000 UAH\r\n\r\nTotal investment: 840,000 UAH\r\n\r\nROI = (1,920,000 \u2013 840,000) \/ 840,000 \u00d7 100%\r\n\r\nROI = 128%\r\n\r\nThis is a hypothetical example based on the assumptions that the conversion rate remains constant, the average check is stable, and there are no additional hidden costs. But the point is clear.\r\n
\r\n

Mistake 5: Overly Ambitious First Project<\/h2>\r\n

Automation often starts with euphoria: a new strategy appears, and logically, there is a desire to change everything at once. Sales, warehouse, finance, HR \u2013 if entering this process, then on a large scale.<\/p>\r\n

And at this very moment, the company complicates life for itself.<\/p>\r\n

When one process changes, the team can still adapt. When five critical functions change simultaneously, people do not have time to understand the new rules of the game, managers do not have time to track the effect, and any failure starts affecting adjacent areas. As a result, after a few months, it becomes difficult to say where exactly the problem arose.scriptum<\/span>+1<\/span><\/span><\/span><\/span><\/span><\/span><\/p>\r\n\r\n

Why Start Small<\/h3>\r\n

A small, clearly defined project allows maintaining control. When one specific area is automated, for example, processing incoming requests or approving contracts, you can fix the input metrics and really assess the effect. Did the time decrease or not? Did losses reduce or not? Did the workload redistribute or not?<\/p>\r\n

In addition, the team undergoes adaptation gradually, and people do not feel that the usual way of working is completely destroyed. Experience with new tools emerges, internal confidence forms that changes are manageable.<\/p>\r\n

Most importantly, the first internal result appears, without which automation looks like an expense, and with it \u2013 like an investment.<\/p>\r\n\r\n

Phased Approach<\/h3>\r\n

First, the bottleneck is identified where the most time or money is lost. Then, baseline metrics are fixed. And only after that, automation is launched on a limited area without trying to cover everything at once.<\/p>\r\n

After obtaining a measurable effect, a decision on scaling is made, and only then does automation expand to adjacent processes.<\/p>\r\n

This approach may seem slower, but it significantly reduces risks. Automation becomes a series of manageable changes, each with a clear business result.<\/p>\r\n\r\n

Successful Automation Checklist<\/h3>\r\n

Before launching automation implementation, it is worth going through several questions.<\/p>\r\n\r\n

Clearly formulated business goal.<\/h4>\r\n

Not abstractly, but specifically: reduce deal cycle by 20%, reduce lead losses to 5%, shorten contract approval time from three days to one. It is impossible to assess the result if the goal is vague.<\/p>\r\n\r\n

Processes described.<\/h4>\r\n

It must be fixed who is responsible for what, where delays occur, what exceptions to the rules exist.<\/p>\r\n\r\n

Bottleneck identified.<\/h4>\r\n

Need to start with the area with the greatest financial or time effect.<\/p>\r\n\r\n

Baseline fixed for measurement.<\/h4>\r\n

Before the start, there should be \"before\" numbers: cycle duration, number of errors, loss share, operation cost.<\/p>\r\n\r\n

Full implementation cost calculated.<\/h4>\r\n

Licenses, development, integrations, training, support, internal team resources.<\/p>\r\n\r\n

Team involved in the process.<\/h4>\r\n

Key employees must understand what is changing and why.<\/p>\r\n\r\n

KPI tied to the new system.<\/h4>\r\n

If result evaluation continues somewhere outside the system, it does not bring the desired benefit.<\/p>\r\n\r\n

Phased scaling plan in place.<\/h4>\r\n

After the first successful stage, it should be clear what next: which processes to automate next and by what criteria the decision is made.<\/p>\r\n

This checklist seems obvious, but neglecting one of these points most often creates those same automation mistakes that later cost millions.<\/p>\r\n\r\n

Order a Process Audit<\/h3>\r\nAutomation often fails due to uncertainty: it\u2019s unclear exactly what needs to be changed and which processes should be addressed first. That\u2019s why the most valuable step is the diagnostic phase.\r\n\r\nA process audit allows you to see everything as it is, in a real operational context: where delays occur, where data is duplicated, and where decisions are made manually even though they could be automated. Often, it becomes clear at this stage that some problems can be solved without complex solutions, simply by changing the workflow logic.\r\n\r\nAt IWIS, we start our work precisely with this\u2014with analysis and structure. Before discussing tools, we get to grips with the processes, the financial model, growth opportunities, and bottlenecks. And only then do we propose a format: whether it will be turnkey automation, phased implementation, or in-depth business consulting.\r\n\r\nIf you feel that your company has outgrown its manual processes but don\u2019t want to turn automation into an expensive experiment, it\u2019s definitely worth starting with an honest conversation and a structured analysis.\r\n\r\nSometimes the right first step is to figure out whether you really need automation in the form you envision it.\r\n\r\n<\/div>"}]},"yoast_head":"\n5 Mistakes in Business Process Automation That Cost Millions - iwis<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/iwis.io\/en\/blog\/5-mistakes-in-business-process-automation\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"5 Mistakes in Business Process Automation That Cost Millions - iwis\" \/>\n<meta property=\"og:url\" content=\"https:\/\/iwis.io\/en\/blog\/5-mistakes-in-business-process-automation\/\" \/>\n<meta property=\"og:site_name\" content=\"iwis\" \/>\n<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/IWIS.UKRAINE\/\" \/>\n<meta property=\"article:published_time\" content=\"2026-04-13T14:22:33+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/iwis.io\/wp-content\/uploads\/2026\/04\/4.webp\" \/>\n\t<meta property=\"og:image:width\" content=\"1080\" \/>\n\t<meta property=\"og:image:height\" content=\"1080\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/webp\" \/>\n<meta name=\"author\" content=\"Content Manager\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Content Manager\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"1 minute\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/iwis.io\\\/en\\\/blog\\\/5-mistakes-in-business-process-automation\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/iwis.io\\\/en\\\/blog\\\/5-mistakes-in-business-process-automation\\\/\"},\"author\":{\"name\":\"Content Manager\",\"@id\":\"https:\\\/\\\/iwis.io\\\/en\\\/#\\\/schema\\\/person\\\/6e21d0700bedf0c2ef539d66b34969b6\"},\"headline\":\"5 Mistakes in Business Process Automation That Cost Millions\",\"datePublished\":\"2026-04-13T14:22:33+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/iwis.io\\\/en\\\/blog\\\/5-mistakes-in-business-process-automation\\\/\"},\"wordCount\":8,\"publisher\":{\"@id\":\"https:\\\/\\\/iwis.io\\\/en\\\/#organization\"},\"image\":{\"@id\":\"https:\\\/\\\/iwis.io\\\/en\\\/blog\\\/5-mistakes-in-business-process-automation\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/iwis.io\\\/wp-content\\\/uploads\\\/2026\\\/04\\\/4.webp\",\"keywords\":[\"\u0430\u0432\u0442\u043e\u043c\u0430\u0442\u0438\u0437\u0430\u0446\u0456\u044f\"],\"inLanguage\":\"en-US\"},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/iwis.io\\\/en\\\/blog\\\/5-mistakes-in-business-process-automation\\\/\",\"url\":\"https:\\\/\\\/iwis.io\\\/en\\\/blog\\\/5-mistakes-in-business-process-automation\\\/\",\"name\":\"5 Mistakes in Business Process Automation That Cost Millions - iwis\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/iwis.io\\\/en\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/iwis.io\\\/en\\\/blog\\\/5-mistakes-in-business-process-automation\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/iwis.io\\\/en\\\/blog\\\/5-mistakes-in-business-process-automation\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/iwis.io\\\/wp-content\\\/uploads\\\/2026\\\/04\\\/4.webp\",\"datePublished\":\"2026-04-13T14:22:33+00:00\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/iwis.io\\\/en\\\/blog\\\/5-mistakes-in-business-process-automation\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/iwis.io\\\/en\\\/blog\\\/5-mistakes-in-business-process-automation\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/iwis.io\\\/en\\\/blog\\\/5-mistakes-in-business-process-automation\\\/#primaryimage\",\"url\":\"https:\\\/\\\/iwis.io\\\/wp-content\\\/uploads\\\/2026\\\/04\\\/4.webp\",\"contentUrl\":\"https:\\\/\\\/iwis.io\\\/wp-content\\\/uploads\\\/2026\\\/04\\\/4.webp\",\"width\":1080,\"height\":1080},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/iwis.io\\\/en\\\/blog\\\/5-mistakes-in-business-process-automation\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/iwis.io\\\/en\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"5 Mistakes in Business Process Automation That Cost Millions\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/iwis.io\\\/en\\\/#website\",\"url\":\"https:\\\/\\\/iwis.io\\\/en\\\/\",\"name\":\"IWIS\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\\\/\\\/iwis.io\\\/en\\\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/iwis.io\\\/en\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\\\/\\\/iwis.io\\\/en\\\/#organization\",\"name\":\"IWIS\",\"url\":\"https:\\\/\\\/iwis.io\\\/en\\\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/iwis.io\\\/en\\\/#\\\/schema\\\/logo\\\/image\\\/\",\"url\":\"https:\\\/\\\/iwis.io\\\/wp-content\\\/uploads\\\/2026\\\/01\\\/cropped-main-favicon.png\",\"contentUrl\":\"https:\\\/\\\/iwis.io\\\/wp-content\\\/uploads\\\/2026\\\/01\\\/cropped-main-favicon.png\",\"width\":512,\"height\":512,\"caption\":\"IWIS\"},\"image\":{\"@id\":\"https:\\\/\\\/iwis.io\\\/en\\\/#\\\/schema\\\/logo\\\/image\\\/\"},\"sameAs\":[\"https:\\\/\\\/www.facebook.com\\\/IWIS.UKRAINE\\\/\",\"https:\\\/\\\/www.linkedin.com\\\/company\\\/iwis-ukraine\\\/\"]},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/iwis.io\\\/en\\\/#\\\/schema\\\/person\\\/6e21d0700bedf0c2ef539d66b34969b6\",\"name\":\"Content Manager\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/7a531ea524f9920bc9042dfdc0e2cfbfbd2f1ad4a85a123cba057564614a25ac?s=96&d=mm&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/7a531ea524f9920bc9042dfdc0e2cfbfbd2f1ad4a85a123cba057564614a25ac?s=96&d=mm&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/7a531ea524f9920bc9042dfdc0e2cfbfbd2f1ad4a85a123cba057564614a25ac?s=96&d=mm&r=g\",\"caption\":\"Content Manager\"},\"sameAs\":[\"https:\\\/\\\/iwis.io\"],\"url\":\"https:\\\/\\\/iwis.io\\\/en\\\/author\\\/iwis-content-manager\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"5 Mistakes in Business Process Automation That Cost Millions - iwis","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/iwis.io\/en\/blog\/5-mistakes-in-business-process-automation\/","og_locale":"en_US","og_type":"article","og_title":"5 Mistakes in Business Process Automation That Cost Millions - iwis","og_url":"https:\/\/iwis.io\/en\/blog\/5-mistakes-in-business-process-automation\/","og_site_name":"iwis","article_publisher":"https:\/\/www.facebook.com\/IWIS.UKRAINE\/","article_published_time":"2026-04-13T14:22:33+00:00","og_image":[{"width":1080,"height":1080,"url":"https:\/\/iwis.io\/wp-content\/uploads\/2026\/04\/4.webp","type":"image\/webp"}],"author":"Content Manager","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Content Manager","Est. reading time":"1 minute"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/iwis.io\/en\/blog\/5-mistakes-in-business-process-automation\/#article","isPartOf":{"@id":"https:\/\/iwis.io\/en\/blog\/5-mistakes-in-business-process-automation\/"},"author":{"name":"Content Manager","@id":"https:\/\/iwis.io\/en\/#\/schema\/person\/6e21d0700bedf0c2ef539d66b34969b6"},"headline":"5 Mistakes in Business Process Automation That Cost Millions","datePublished":"2026-04-13T14:22:33+00:00","mainEntityOfPage":{"@id":"https:\/\/iwis.io\/en\/blog\/5-mistakes-in-business-process-automation\/"},"wordCount":8,"publisher":{"@id":"https:\/\/iwis.io\/en\/#organization"},"image":{"@id":"https:\/\/iwis.io\/en\/blog\/5-mistakes-in-business-process-automation\/#primaryimage"},"thumbnailUrl":"https:\/\/iwis.io\/wp-content\/uploads\/2026\/04\/4.webp","keywords":["\u0430\u0432\u0442\u043e\u043c\u0430\u0442\u0438\u0437\u0430\u0446\u0456\u044f"],"inLanguage":"en-US"},{"@type":"WebPage","@id":"https:\/\/iwis.io\/en\/blog\/5-mistakes-in-business-process-automation\/","url":"https:\/\/iwis.io\/en\/blog\/5-mistakes-in-business-process-automation\/","name":"5 Mistakes in Business Process Automation That Cost Millions - iwis","isPartOf":{"@id":"https:\/\/iwis.io\/en\/#website"},"primaryImageOfPage":{"@id":"https:\/\/iwis.io\/en\/blog\/5-mistakes-in-business-process-automation\/#primaryimage"},"image":{"@id":"https:\/\/iwis.io\/en\/blog\/5-mistakes-in-business-process-automation\/#primaryimage"},"thumbnailUrl":"https:\/\/iwis.io\/wp-content\/uploads\/2026\/04\/4.webp","datePublished":"2026-04-13T14:22:33+00:00","breadcrumb":{"@id":"https:\/\/iwis.io\/en\/blog\/5-mistakes-in-business-process-automation\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/iwis.io\/en\/blog\/5-mistakes-in-business-process-automation\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/iwis.io\/en\/blog\/5-mistakes-in-business-process-automation\/#primaryimage","url":"https:\/\/iwis.io\/wp-content\/uploads\/2026\/04\/4.webp","contentUrl":"https:\/\/iwis.io\/wp-content\/uploads\/2026\/04\/4.webp","width":1080,"height":1080},{"@type":"BreadcrumbList","@id":"https:\/\/iwis.io\/en\/blog\/5-mistakes-in-business-process-automation\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/iwis.io\/en\/"},{"@type":"ListItem","position":2,"name":"5 Mistakes in Business Process Automation That Cost Millions"}]},{"@type":"WebSite","@id":"https:\/\/iwis.io\/en\/#website","url":"https:\/\/iwis.io\/en\/","name":"IWIS","description":"","publisher":{"@id":"https:\/\/iwis.io\/en\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/iwis.io\/en\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/iwis.io\/en\/#organization","name":"IWIS","url":"https:\/\/iwis.io\/en\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/iwis.io\/en\/#\/schema\/logo\/image\/","url":"https:\/\/iwis.io\/wp-content\/uploads\/2026\/01\/cropped-main-favicon.png","contentUrl":"https:\/\/iwis.io\/wp-content\/uploads\/2026\/01\/cropped-main-favicon.png","width":512,"height":512,"caption":"IWIS"},"image":{"@id":"https:\/\/iwis.io\/en\/#\/schema\/logo\/image\/"},"sameAs":["https:\/\/www.facebook.com\/IWIS.UKRAINE\/","https:\/\/www.linkedin.com\/company\/iwis-ukraine\/"]},{"@type":"Person","@id":"https:\/\/iwis.io\/en\/#\/schema\/person\/6e21d0700bedf0c2ef539d66b34969b6","name":"Content Manager","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/7a531ea524f9920bc9042dfdc0e2cfbfbd2f1ad4a85a123cba057564614a25ac?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/7a531ea524f9920bc9042dfdc0e2cfbfbd2f1ad4a85a123cba057564614a25ac?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/7a531ea524f9920bc9042dfdc0e2cfbfbd2f1ad4a85a123cba057564614a25ac?s=96&d=mm&r=g","caption":"Content Manager"},"sameAs":["https:\/\/iwis.io"],"url":"https:\/\/iwis.io\/en\/author\/iwis-content-manager\/"}]}},"_links":{"self":[{"href":"https:\/\/iwis.io\/en\/wp-json\/wp\/v2\/posts\/6147","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/iwis.io\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/iwis.io\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/iwis.io\/en\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/iwis.io\/en\/wp-json\/wp\/v2\/comments?post=6147"}],"version-history":[{"count":3,"href":"https:\/\/iwis.io\/en\/wp-json\/wp\/v2\/posts\/6147\/revisions"}],"predecessor-version":[{"id":6160,"href":"https:\/\/iwis.io\/en\/wp-json\/wp\/v2\/posts\/6147\/revisions\/6160"}],"acf:term":[{"embeddable":true,"taxonomy":"post_tag","href":"https:\/\/iwis.io\/en\/wp-json\/wp\/v2\/tags\/212"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/iwis.io\/en\/wp-json\/wp\/v2\/media\/6115"}],"wp:attachment":[{"href":"https:\/\/iwis.io\/en\/wp-json\/wp\/v2\/media?parent=6147"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/iwis.io\/en\/wp-json\/wp\/v2\/categories?post=6147"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/iwis.io\/en\/wp-json\/wp\/v2\/tags?post=6147"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}