Building a DevOps Culture in a Factory: The People Problem Nobody Talks About

70% of digital transformation initiatives fail to meet their objectives. McKinsey's research has pointed to the same cause consistently: the dominant obstacle is culture, not technology.

In a software company, building a DevOps culture is a people challenge. In a factory, it is a people challenge with an additional layer, two groups of people who have different priorities, different risk tolerances, and different definitions of what good looks like, operating on the same production floor.

OT teams, the engineers who run PLCs, SCADA systems, and production lines, were hired to keep machines running. Their performance metric is uptime. IT teams were hired to build and ship systems. Their performance metric is velocity. DevOps asks both groups to share a pipeline, share accountability, and share a definition of done. That is not a technology problem. It is an organizational problem that technology cannot fix.

This is the people problem that most manufacturing DevOps implementations fail to address, and the reason so many stall after the pilot.

Why Does DevOps Culture Fail in Manufacturing?

Only 26% of businesses treat change management as an important part of their Industry 4.0 transition, according to industry research. The majority treat it as an afterthought, or skip it entirely. They deploy the technology first and assume adoption follows.

It does not.

Four specific fears drive resistance on the factory floor:

• Job loss from automation - workers see new systems as a replacement for their roles, not a tool that changes them
• Inability to adapt - skills built over years on legacy equipment do not transfer automatically to new environments
• Distrust of new technology reliability - OT teams have seen IT systems crash. A crashed PLC stops a line. Skepticism is not irrational; it is earned
• Loss of control over familiar work methods - the people who know the floor best are the ones being asked to change the most

None of these fears are addressed by deploying better tooling. Each one requires a deliberate response, communication, training, involvement, and time.

What Does DevOps Culture Actually Require in a Manufacturing Context?

The DORA 2024 State of DevOps Report, the largest longitudinal DevOps study, covering 39,000+ respondents, found that organizational culture and leadership quality are as strong predictors of delivery performance as any technical practice. Culture is not a soft add-on to the technical implementation. It is an equal driver of outcomes.

In manufacturing, that finding has a specific implication. The DORA report identifies unstable organizational priorities as causing meaningful productivity decreases and substantial burnout, effects that persist even with strong leadership and good documentation, making them uniquely resistant to technical mitigation. In a factory context, unstable organizational priorities is the default state of an OT/IT integration that has not defined who owns the pipeline.

Ownership is the first cultural question. Not tooling, not process, not infrastructure. Who is accountable for the outcome?

Deloitte's 2025 Smart Manufacturing Survey found that 51% of smart manufacturing initiatives are owned by operations leaders and 38% by technology leaders. That split ownership is a direct cause of implementation failure. A pipeline with two owners and no arbitration mechanism defaults to the slowest decision-maker, which in manufacturing is always the OT team, because uptime risk falls on them.

How to Build a DevOps Culture in a Factory: A Practical Framework

Cultural change in manufacturing is not fast. LNS Research estimates that most industrial enterprises take 3-5 years to complete a transformation at scale. Technology deployment takes months. Cultural adoption takes years. Any implementation timeline that does not account for this gap is not a plan, it is a hope.

The framework that fits manufacturing environments best follows Kotter's 8-step change model, with two steps that are almost always skipped: creating urgency and anchoring change in culture.

Step 1: Create visible urgency before touching the technology

The Bitkom 2025 survey of German companies found that 82% believe Germany is in a digitalization crisis, and 73% say Germany has already lost market share due to slow adoption. That data exists at the national level. Operations directors need the same data at the company level, specific, measurable, immediate. Without a visible cost of inaction, the default choice on the factory floor is always stability.

Step 2: Build a cross-functional coalition with OT at the center

The most common mistake is assigning DevOps ownership to IT and asking OT to cooperate. That structure reproduces the vendor relationship that kills distributed teams, one group defines, the other executes. The coalition must be co-led. OT engineers carry irreplaceable process knowledge. When involved early, they become advocates. When informed late, they become blockers.

Step 3: Start with a single line and make the OT team the expert

Do not attempt to change the culture of an entire facility. Pick one production line, deploy the pilot, and structure the engagement so that the OT team on that line is teaching the IT team how the process works, not the other way around. The power dynamic matters. OT teams that feel like subjects of a change program resist. OT teams that feel like co-designers of it lead it.

Step 4: Define shared metrics before shared tooling

Shared tooling without shared metrics produces two teams measuring different things with the same instruments. Define the four DORA indicators, deployment frequency, lead time for changes, change failure rate, mean time to recovery, as the joint scorecard before any infrastructure decision. When both teams are measured against the same numbers, the incentive structure changes.

Step 5: Invest in reskilling as infrastructure, not as a perk

Demand for simulation and software competencies in manufacturing increased by 75% between 2021 and 2024, according to Deloitte and the Manufacturing Institute's 2024 Workforce Study. The OT engineers being asked to work in a DevOps pipeline were not hired for those skills. Reskilling is not optional, it is the enabler that makes shared ownership operationally possible. Treat it as a capital investment, not a training budget line.

Step 6: Anchor the change in operational language, not IT language

Deployment frequency means nothing to a plant manager. How many configuration changes can we make per week without stopping the line means the same thing. Every DevOps concept has a manufacturing equivalent. Use the manufacturing version. Terminology that signals IT ownership of the process will be rejected by the factory floor, not out of obstinacy, but because it signals that the change is happening to them, not with them.

What Does Good Look Like?

Global manufacturing workforce engagement sits at approximately 15%, based on Gallup's cross-industry data. That is the starting point, not a motivated workforce waiting for better tools, but one in which the overwhelming majority are not actively invested in the work or its improvement. Digital forerunners, companies that build the culture alongside the infrastructure, achieve up to 50% better margins than digital laggards in the same sector, according to McKinsey research on manufacturing digitalization.

The gap between 15% engagement and 50% better margins is not a technology gap. It is a leadership and culture gap. The companies that close it do not do so by deploying more systems. They do so by changing what the systems mean to the people who run them.

FAQ

How do you build a DevOps culture in a manufacturing company?

Building a DevOps culture in manufacturing requires addressing the OT/IT divide as an organizational problem, not a technical one. The practical steps: create urgency at the company level, build a cross-functional coalition with OT leadership at the center, start with a single-line pilot where OT teams co-design the process, define shared DORA metrics before shared tooling, and invest in reskilling as infrastructure. Cultural adoption takes 3-5 years at full scale, plan for it.

Why do DevOps transformations fail in manufacturing?

70% of digital transformation initiatives fail to meet their objectives, according to McKinsey's research, with culture consistently identified as the dominant obstacle. In manufacturing specifically, the failure mode is structural: OT and IT teams have different risk tolerances, different performance metrics, and different definitions of success. Only 26% of businesses treat change management as an important part of their Industry 4.0 transition, meaning the majority deploy technology without addressing the people conditions that determine whether it works.

What is the difference between DevOps culture in software vs. manufacturing?

In software, DevOps culture requires aligning development and operations teams around a shared delivery pipeline. In manufacturing, the same alignment is required, but the OT team running production equipment has an additional constraint: uptime is their primary responsibility, and a failed deployment does not roll back, it stops a line. This changes the risk tolerance, the change management requirements, and the time needed for cultural adoption.

How long does it take to build a DevOps culture in a factory?

Technology deployment in manufacturing takes months. Cultural adoption takes years. LNS Research estimates that most industrial enterprises take 3-5 years to complete a transformation at scale. Implementations that plan for a 12-month cultural change program will stall, not because the technology fails, but because the organization has not had enough time to change how it works.

What is the OT/IT divide and why does it matter for DevOps in manufacturing?

The OT/IT divide is the organizational and cultural gap between operational technology teams, who run factory equipment including PLCs, SCADA, and sensors, and information technology teams who build and manage software systems. OT teams prioritize uptime and stability. IT teams prioritize velocity and change. DevOps requires both teams to share a pipeline and shared accountability. Bridging that divide is the central challenge of manufacturing DevOps, and it is a culture problem, not a technology problem.