Resources list
Low code
TAM
AI

Automation: why projects fail (and how to avoid these traps)

Team Rokodo
8
-
21.10.2026
Automation: why projects fail (and how to avoid these traps)
The Strategic Vs. Tactical Automation Divide

Automation programs exhibit staggering failure rates. According to a 2023 Deloitte study, 72% of digital transformation initiatives fall short of their initial targets. Yet the obstacle rarely stems from technology itself. Low-code platforms, artificial intelligence, and automation engines are mature, accessible, and performant. The real problem lies elsewhere: in the absence of clear strategy, business governance, and organizational readiness.

This ground-level reality explains why two companies in the same industry, equipped with identical tools, achieve radically different results. One transforms its operations; the other accumulates costs. The difference is never technological. It is strategic.

What Is Strategic Automation?

Strategic automation aligns technology investments with measurable business objectives. It does not seek to digitize for its own sake, but to resolve specific friction points with a defined ROI and adoption roadmap.

This approach rests on four pillars: clear mapping of current processes, quantification of expected economic impact, structured end-user engagement, and phased deployment with continuous refinement.

What Is Tactical Automation?

Tactical automation selects a high-performing tool and introduces it into the organization hoping that gains will follow. It reverses the logic: technology precedes strategy.

This short-term approach generates impressive pilots, rapid rollouts, but also abrupt abandonment and major cost overruns. The tool is installed; the organization has not adapted to use it.

Difference 1: Decision-Making

Strategic Approach: Vision Before Tools

An insurance company aiming to automate incoming claim triage begins with a business question: what financial gain should we expect? Faster processing times? Lower error rates? Team reallocation?

Once the gain is quantified, the organization examines its existing data, assembles a cross-functional project team (business, IT, operations), and only then selects the appropriate tool. Technology is a means; the business outcome is the end.

  • Decisions centered on measurable ROI and operational impact
  • Technology selection after true needs assessment
  • Business case validation before any IT investment

Tactical Approach: Tool-First Thinking

The alternative involves acquiring a reputable low-code platform, designating an IT lead, and launching workshops to identify what could be automated with that tool.

Result: existing processes are forced into the solution's constraints, rather than selecting a solution tailored to real needs. Teams pilot the technology, not the transformation.

  • Decisions based on tool functionality
  • Technology selection without prior business analysis
  • Needs discovery after acquisition

Reference: McKinsey, "Why Digital Transformations Fail" (2019) identifies strategic misalignment as the leading cause of failure.

Difference 2: Data Quality

Strategic Approach: Data Hygiene as Foundation

Intelligent automation without data quality is like a car without fuel. A workflow relying on inconsistent, duplicate, or poorly structured data will yield unpredictable results.

Strategic preparation first audits existing data quality. It identifies gaps, inconsistencies, and sources of truth. This initial investment—lengthy and unglamorous—determines the ultimate success of automation.

  • Upfront audit of data quality, completeness, and consistency
  • Cleansing and structuring before automation begins
  • Data governance framework to prevent future degradation

Tactical Approach: We'll Figure It Out

Tactical automation assumes the tool will handle imperfect data. Result: automation creates additional layers of errors, users learn to bypass the system, and the project loses credibility.

  • Implicit expectation that the tool will compensate for data flaws
  • Data quality issues discovered in production
  • Accumulation of manual workarounds and ad hoc fixes

Reference: Gartner, "Data Quality Scorecard" (2022) reports that 45% of analytics initiatives fail due to poor data quality.

Difference 3: User Engagement

Strategic Approach: Co-Creation and Ownership

Change resistance kills 60% of transformation projects. Yet this resistance rarely stems from ideological opposition. It comes from a sense of powerlessness, poor communication, and users treated as passive implementers.

Automation strategy engages business teams from diagnosis onward. Their input informs design. Pilots test automated processes in real environments. Training prepares adoption. Users feel like actors, not victims.

  • Diagnosis and design involving business teams from the start
  • Local pilots with iterative feedback and adjustments
  • Structured training and communication before rollout
  • Adoption and user sentiment tracking

Tactical Approach: The Tool Arrives from Above

The platform is configured in an IT silo. A go-live date is announced. Users discover it or receive generic training. They do not understand why the change is happening, how it affects their daily work, or what value it creates.

Result: system workarounds, reversion to manual methods, mounting support tickets, damaged initiative reputation.

  • Centralized configuration without business input
  • Abrupt deployment without phased transition
  • Minimal, post-deployment training
  • Absence of real adoption monitoring

Reference: MIT Sloan, "Digital Transformation Success Factors" (2021) ranks user adoption as the second-most critical success factor after strategic alignment.

Difference 4: Results Measurement

Strategic Approach: Clear and Continuous Metrics

Strategic automation defines key performance indicators before implementation. Productivity gains? Measured in hours saved. Error rate reduction? In basis points. Cycle time? In calendar days.

These metrics are tracked, published, and used to refine deployment. If an expected gain does not materialize, the root cause is investigated: insufficient adoption, underutilization, or process incompatibility.

  • Success metrics defined before go-live
  • Continuous measurement and transparent stakeholder reporting
  • Rapid adjustments based on observed data
  • Learning reuse across subsequent phases

Tactical Approach: We'll Review It in Six Months

Tactical automation deploys the tool, then forgets to measure. Six months later, it is unclear whether anything has changed. IT teams claim everything works technically. Business teams perceive no gains. Nobody knows for certain.

  • No predefined indicators
  • Sporadic and subjective post-deployment measurement
  • No feedback loop for system adjustments
  • Impossible to justify the investment retrospectively

Reference: Forrester, "Measuring Digital Transformation Success" (2023) notes that 58% of unmeasured initiatives are abandoned within 18 months.

Difference 5: Current Process Management

Strategic Approach: Fix, Then Automate

A broken process, once automated, remains broken. It is just faster. Automation amplifies existing flaws.

Automation strategy therefore begins by cleaning the current process. Process mining or operational audits identify redundancies, unnecessary validations, and bottlenecks. Simplification precedes automation. This sequence is counterintuitive but essential.

  • Audit of current processes to identify flaws
  • Simplification and optimization before automation
  • Elimination of redundant or non-compliant steps
  • Clean processes before automation deployment

Tactical Approach: Automate the Chaos

The temptation is to leave processes as they are and hope technology will fix everything. Existing workflows—redundancies and inefficiencies included—are encoded into the tool.

Result: automation faithfully reproduces existing dysfunctions. Worse, it obscures them. Why a task takes so long or generates errors becomes impossible to understand.

  • Encoding current processes without prior cleansing
  • Preservation and amplification of inefficiencies
  • Growing system complexity over time
  • Future optimization challenges

Reference: NIST, "Automation Best Practices" (2021) recommends process mining before any technology deployment.

Difference 6: Deployment and Learning

Strategic Approach: Progressive, Iterative, and Learning-Focused

Strategic automation proceeds in stages. One pilot process in one region, with a small team and tight measurements. Pilot learnings refine configuration before broader rollout.

This progression allows errors to be corrected before they crystallize at scale. It gives users time to adapt. It builds credibility through observed wins.

  • Localized and controlled pilot deployment
  • Intensive pilot measurement
  • Configuration and training refinement
  • Progressive rollout by waves, region, or team
  • Documentation of learnings and best practices

Tactical Approach: Big Bang and Hope

Tactical deployment favors the big bang: everyone, everywhere, all at once on the full platform. It is impressive, visible, "transformational."

It is also catastrophic if something breaks. Unlike a localized pilot, there is no safe zone, no fallback plan. Teams are overwhelmed, technical support cannot keep up, users panic.

  • Monolithic deployment across the entire organization
  • Limited testing or real-scale rehearsal
  • Technical support overwhelmed and reactive rather than prepared
  • Impossible to roll back quickly
  • Lessons learned too late to correct major errors

Reference: Standish Group, "Chaos Report" (2023) reports that phased deployments achieve 40% higher success rates than monolithic rollouts.