1898 & Co. Blog

The Risk of Utility Transformation Without Operational Context

Written by Amy Borgmeyer | June 24, 2026 at 4:06 PM

A previous blog post introduced knowledge risk as an emerging transformation constraint and argued that utilities must increasingly view knowledge as a strategic capability, rather than an informal byproduct of experience. It also distinguished between institutional knowledge — the wisdom developed by individuals through experience — and operational intelligence, the organization’s ability to make knowledge actionable at scale.

The growing gap between both critical assets is the challenge now facing many utilities. This gap becomes particularly important as utilities accelerate automation and digital transformation efforts. Closing the gap requires more than documentation; it calls for knowledge infrastructure: the processes, roles, systems, governance routines, decision rules and feedback loops that allow operational context to be captured, maintained and used in the flow of work. This blog post examines where that knowledge risk becomes especially visible: when automation and digital transformation efforts depend on operational context to produce value.

Deploying Advanced Tools Is Not Enough

Utilities are investing in advanced technologies designed to improve efficiency, reliability and decision-making. These might include advanced distribution management systems (ADMS), mobile workforce management (MWM) platforms, predictive maintenance tools, AI-enabled analytics, digital twins, remote monitoring technologies, and automated inspection systems. All are becoming increasingly common components of utility modernization programs, and the business case for these investments is often compelling. These tools are not merely digitizing existing work. They are increasingly shaping how work is identified, prioritized, assigned, escalated and evaluated.

There is growing pressure to do more with less, respond faster to operational conditions, and manage increasingly complex infrastructure networks. Automation and advanced analytics offer a pathway to achieve these objectives. Yet many organizations discover that deploying technology is significantly easier than realizing its intended value. The reason is often the operating environment surrounding the technology:

  • The assumptions built into workflows.
  • The judgment needed to interpret outputs.
  • The exception paths that determine when a recommendation should be overridden.
  • The accountability structures that determine who acts.

Utilities typically pursue enhanced efficiency through automation as a core element of any digital transformation. However, achieving the benefits from automation is fundamentally an operating model initiative. It changes how work is prioritized, how exceptions are handled, who makes decisions, what information people trust, and how teams coordinate across field operations, engineering, planning, customer operations and the control room.

Technology can automate activities, accelerate workflows and improve visibility. It cannot independently provide the operational context required to determine whether a recommendation is appropriate under specific conditions.

Figure 1: Automation changes where judgment lives, embedding it into the design of work.

Consider a predictive maintenance model that identifies assets most likely to fail. The model might accurately analyze thousands of data points and correctly rank risk. An experienced operator or field supervisor also might know that a particular asset behaves differently during high-load periods, that access is limited during part of the year, that a nearby capital project will address the issue, or that prior repairs are not fully reflected in the data.

Neither insight may exist within the underlying dataset, yet both could materially influence the decision. This highlights a broader reality: Utility operations depend on a combination of data-driven insight and operational judgment. The value of the model depends not only on its analytical accuracy, but on whether the organization has a reliable way to bring relevant context into the decision before work is prioritized or deferred.

What the System Sees What Operations Knows
Asset condition data High-load operating behavior
Failure probability Seasonal access constraints
Historical trends Nearby capital project timing
Risk score Prior repairs not reflected in data
Work queue priority Safety, customer and field constraints

Figure 2: Better decisions require both analytical insight and operational context.

The Automation-Context Gap

The challenge becomes even more pronounced as transformation accelerates. New technologies are often introduced faster than organizations can fully absorb them. Workflows evolve. Roles change. Decision rights shift. Employees must learn new systems while continuing to operate existing infrastructure. Automated work queues may increase the volume of findings without clear triage rules. Dashboards may change how priorities are set before the organization has aligned on who owns the decision.

Automation is one part of a broader transformation agenda, and it makes one issue clear: Utilities are changing systems, processes, roles and workforce expectations faster than their knowledge infrastructure can always support. This is the automation-context gap. Technology increases the speed, volume and visibility of operational decisions faster than the organization can consistently supply the context needed to make those decisions well.

Figure 3: The automation-context gap shows where decision quality can suffer.

These are not isolated implementation issues. They are signs that operational context has not been fully translated into the workflows, rules, roles and feedback mechanisms that automation depends on. When that translation is incomplete, technology can expose the gap quickly, and the addition of new or more advanced technology can exacerbate the issue.

An automated inspection program might identify more issues than the organization can prioritize. A mobile work platform might standardize the workflow while supervisors continue to manage exceptions outside the system. An analytics tool might surface risk, but operations may not have a consistent way to resolve conflicts among the model output, field conditions, customer impact, safety considerations and capital plans.

Ironically, the more aggressively utilities pursue transformation, the more important operational context becomes. Without sufficient context, organizations can find themselves in a position where technology capabilities increase while organizational effectiveness stagnates. Systems generate more information, but employees struggle to interpret it consistently. New processes are implemented, but local workarounds continue to emerge because operational realities were not fully incorporated into the design.

The result is not necessarily operational failure. More often, it manifests as something subtler: slower adoption, inconsistent execution, unrealized value and growing dependence on a shrinking number of experienced individuals to bridge the gap between system outputs and operational decisions.

Building Knowledge Readiness to Close the Circle

This is why knowledge readiness is becoming increasingly important. If knowledge risk represents the possibility that critical knowledge is unavailable or inaccessible, knowledge readiness represents the organization’s ability to continuously connect operational experience, organizational intelligence and technology-enabled decision-making.

To this end, utilities that successfully modernize are not simply deploying more technology. They are creating environments in which operational knowledge flows into systems, which reinforce decision-making, continuously improving operational performance.

In short, successful transformation requires operational context in support of automation. Without that context, utilities may increase the speed and volume of activity without improving the quality or consistency of decisions. That does not mean utilities should slow down digital transformation. Technology value depends on designing operational context — and the knowledge infrastructure to make that context visible, current, trusted and actionable — into how work gets done and how decisions are made.