When Engineering, IT, and OT All Own a Piece, Who Owns Delivery?

By Michael Turner

Not all complexity is technical, some of it is organizational. In today’s utility environment, few initiatives live neatly within a single function. Engineering designs the assets. IT enables the systems. OT operates and monitors the infrastructure in real time. Each group owns a critical piece, and each does its job well. Yet many projects still struggle to move from design to operation smoothly. Why?

Because while ownership is distributed, delivery often isn’t.

Utility programs increasingly fail not due to flawed technology, but because accountability gets lost in the handoffs between disciplines. Engineering optimizes for physical assets. IT focuses on systems, networks, and security. OT prioritizes reliability, safety, and operational continuity. These priorities are all valid, but without intentional coordination, they can unintentionally work at cross purposes.

This challenge becomes especially visible in operational technology initiatives. SCADA, telemetry, and control systems are frequently treated as secondary to engineering work, something to be “plugged in” after construction is complete. In reality, these systems are the eyes and ears of the asset. Without them, infrastructure cannot be monitored, controlled, or safely operated at scale.

The issue is not a lack of expertise. It is the absence of a clear delivery owner, someone accountable for orchestrating the full lifecycle across functions.

When no one owns delivery end‑to‑end, teams default to what they know best. Engineers focus on mechanical completion. IT focuses on standards and architecture. OT focuses on operations and response. The gaps between those responsibilities, that is, testing, integration, sequencing, readiness, are where risk accumulates.

Effective delivery in this environment requires a different mindset: delivery as a service.

Delivery as a service is not about replacing engineering, IT, or OT expertise. It is about enabling those teams to succeed by providing structure, coordination, and accountability across organizational boundaries. It means standardizing how work moves from design to implementation to operation, regardless of site size or complexity. It means understanding not just what needs to be built, but how it will be operated, supported, and scaled over time.

This approach also recognizes an important reality: no single delivery framework fits every type of work. Operationally intensive programs often move faster, involve more interdependencies, and carry different risk profiles than traditional initiatives. Successful delivery requires governance that sets expectations and accountability while remaining flexible enough to reflect how the work actually gets done.

Ultimately, the question is not whether Engineering, IT, and OT each own a piece. They do, and they must. The real question is who owns delivery across those pieces.

Organizations that answer that question clearly reduce friction, improve outcomes, and build trust across teams. Those that don’t, often find themselves solving the same problems again and again, just with different projects.