Independent research across 92 production automation environments — how organizations design, operate, and evolve business-critical workloads.
Automation failures do not stay in IT. They cascade.
When a batch job misses its window, a downstream financial report does not reconcile. When a file transfer stalls, a warehouse management system stops receiving inventory updates. When a workflow dependency breaks, the people who depend on that output — in operations, finance, and customer service — start making decisions with incomplete data.
Across 92 production environments spanning banking, healthcare, technology, public sector, and manufacturing, one finding cuts through every other result.
An additional 23% report impact to multiple teams. Only 1% classify their workloads as non-critical. Automation has graduated from an IT efficiency exercise to the operational backbone of the enterprise.
Independent practitioner research. 46-day collection window. Production environments only.
This report draws on responses from 92 practitioners across a 46-day collection window. Respondents include individual contributors, managers, directors, and executives responsible for designing, operating, and maintaining production automation environments across a range of industries and organizational sizes.
The survey covers deployment architecture, use case scope, business criticality, feature priorities, and attitudes toward emerging technologies including generative AI. Responses reflect environments actively running in production — not pilot programs or proof-of-concept deployments.
Nearly half (47%) of respondents have more than five years of direct experience. More than two-thirds (67%) have been running production environments for three or more years.
Note: Response data reflects production environments only. Pilot and proof-of-concept deployments were excluded from analysis.
When automation fails, the business feels it — immediately, and across organizational boundaries.
The most striking finding in this survey is not the technology choices practitioners make. It is the operational weight they carry. Asked how critical their automated workflows are to the business, respondents left little room for ambiguity.
Seventy-three percent describe their automation as "extremely critical" — meaning a failure creates significant business impact across the entire organization. Another 23% say issues affect multiple teams.
When the majority of automated workloads carry cross-organizational risk, the tolerance for fragile infrastructure shrinks dramatically. Practitioners need visibility, dependency management, and reliable alerting before something fails — not after.
Forty-three percent of respondents report that 51–75% of their workloads are business-critical. Twenty-two percent report 76–100%. Fewer than 11% say fewer than a quarter of their workloads carry that designation.
N=92. Single response.
N=92. Single response.
Practitioners who started with a scheduler now operate something closer to an integration layer.
Workload automation began as a solution to a narrow problem: run the right job, in the right order, at the right time. For most organizations in this survey, that problem remains — but it has expanded considerably. File transfers remain the most common use case at 75%, but workflows connecting multiple applications rank second at 70%, and business process automation has reached 52%.
The architecture most organizations rely on today was not designed for the workloads they run today.
The most significant structural tension in this data is the gap between deployment architecture and use case ambition. Seventy-seven percent of respondents run on self-managed, on-premises infrastructure — while feature requests point overwhelmingly toward cloud-native patterns. Cloud execution methods lead by a wide margin. Credential vault support — integrations with Azure Key Vault, CyberArk, and Delinea — ranks second at 61%.
Most production environments in this survey do not fit neatly into an on-premises or cloud category. They are hybrid by circumstance: core systems remain on-premises, while data pipelines, cloud storage, and SaaS applications introduce cloud touchpoints that the orchestration layer must reach.
The organizations building a reliable automation foundation today are the ones that will operationalize AI tomorrow.
Generative AI is not yet a significant factor in production automation environments. Only 4% of respondents currently use it to support their orchestration workflows. Seventy-nine percent report no current plans to do so. But 16% report active plans for adoption — and among the 69% who already use AI for research and ideation outside orchestration, the building blocks are present.
What is missing is not interest. It is a reliable, observable automation foundation to run AI workflows on top of.
Practitioners are ready to use AI tooling inside their orchestration environments. They are waiting for the environment to be ready for them.
Systems Administrators represent the largest role category at 29%, followed by IT Management and Executive at 26%, Data Engineers and DBAs at 18%, and Developers at 11%. The financial services concentration is consistent with the criticality findings: industries with strict SLA obligations naturally produce practitioners who understand automation failure as a business problem, not an IT inconvenience.
Note: Geography spans multiple countries. The United States represents 28% of total respondents. Other represented geographies include Australia, Canada, the United Kingdom, and Switzerland. Thirty-five percent of respondents come from organizations with fewer than 500 employees.