There is a question I have asked in every operational environment I have entered over the past 30 years: Are you managing your assets, or are you enabling performance through them?
The answer tells me almost everything I need to know about the organization.
Most companies manage assets. They track maintenance schedules, monitor depreciation, control costs, and measure uptime. These are necessary activities. But they are not sufficient. The organizations that consistently outperform their peers have made a fundamental shift in how they think about the physical infrastructure they depend on — from a liability to be managed to a capability to be leveraged.
That shift is the subject of this post.
The Asset Management Trap
Traditional asset management is built around a simple logic: assets cost money, they degrade over time, and the job of the maintenance function is to slow that degradation at the lowest possible cost.
This logic is not wrong. It is just incomplete.
When cost control becomes the primary lens, several things happen. Maintenance becomes reactive rather than proactive. Capital investment decisions get made on financial criteria alone, without adequate weight given to operational impact. And the people closest to the equipment — the operators and technicians who understand its behavior better than anyone — get treated as cost inputs rather than knowledge sources.
The result is a function that is perpetually behind. Always catching up. Always justifying its existence by pointing to what it prevented rather than what it enabled.
What Performance Enablement Looks Like
The shift I am describing is not about spending more money on assets. It is about asking a different question at every decision point.
Instead of what is the minimum maintenance required to keep this asset running?, the question becomes what does this asset need to perform at the level the operation requires?
That reframe changes everything downstream.
Maintenance strategy becomes output-driven. Rather than applying a standard maintenance regime across all assets, you differentiate based on criticality and consequence. A pump that sits in a redundant configuration is not the same as a pump that is the single point of failure for an entire production line. They should not be maintained the same way.
Capital investment decisions incorporate operational risk. The financial case for replacing aging infrastructure is not just about maintenance cost avoidance. It includes the cost of unplanned downtime, the risk of regulatory non-compliance, and the opportunity cost of operating below designed capacity. When you model the full picture, the investment case often looks very different.
The maintenance function becomes a strategic partner. When the question shifts from cost to performance, the conversation between operations and maintenance changes. Instead of maintenance defending its budget, it is contributing to production planning, flagging emerging risks, and helping the business understand what is achievable and what is not.
The Role of Data — and Its Limits
Over the past decade, the asset management field has been transformed by data. Condition monitoring, predictive analytics, digital twins — the tools available today would have been unimaginable when I started my career.
I am a strong advocate for these technologies. Used well, they shift the maintenance function from time-based to condition-based, which is almost always more efficient and more effective.
But I have also seen organizations invest heavily in data infrastructure and see little improvement in operational performance. The reason is almost always the same: the data is being used to optimize the existing approach rather than to challenge the underlying assumptions.
Data tells you what is happening. It does not tell you what should be happening. That requires judgment — and judgment requires a clear view of what the operation is trying to achieve.
The organizations that get the most value from their data investments are the ones that have already done the harder work of defining what performance means for their specific context. They know which assets are critical, which failure modes matter most, and what the operational consequences of different scenarios look like. The data then becomes a tool for managing toward a defined outcome, rather than a source of information in search of a purpose.
Organizational Alignment Is the Real Constraint
In my experience, the biggest barrier to the shift from asset management to performance enablement is not technical. It is organizational.
Asset management sits at the intersection of operations, maintenance, engineering, and finance. Each of these functions has its own priorities, its own metrics, and its own view of what good looks like. Without deliberate alignment, they will optimize locally and sub-optimize the whole.
I have seen this play out in predictable ways. Operations pushes for maximum availability and resists any planned downtime. Maintenance advocates for more conservative maintenance intervals and gets overruled on cost grounds. Engineering specifies equipment to a standard that maintenance cannot sustain. Finance approves capital on a three-year payback horizon that does not capture the long-term reliability implications.
None of these functions is wrong. They are each doing their job. The problem is the absence of a shared framework for making trade-offs.
Building that framework is a leadership task. It requires someone who can hold the whole system in view — who understands the operational requirements, the technical constraints, the financial realities, and the organizational dynamics — and who can facilitate the conversations that align these functions around a common definition of performance.
Three Principles That Guide the Transition
Based on what I have seen work across industries and geographies, three principles consistently underpin successful transitions from asset management to performance enablement.
1. Define performance before you define the maintenance strategy. This sounds obvious, but it is rarely done rigorously. What does the operation need from each critical asset? What are the acceptable boundaries of performance? What are the consequences of falling outside those boundaries? The answers to these questions should drive every subsequent decision about maintenance approach, investment priority, and organizational capability.
2. Treat reliability as a designed-in property, not a maintained-in one. The most reliable operations I have worked with invest heavily in getting the design right — selecting the right equipment for the application, installing it correctly, and commissioning it thoroughly. They understand that you cannot maintain your way to reliability if the foundation is not sound. This principle extends to modifications and upgrades: every change to the physical plant is an opportunity to improve reliability, or to compromise it.
3. Build the capability to learn. High-performing asset management organizations are distinguished not just by what they know, but by how quickly they learn. They have systematic processes for capturing failure data, analyzing root causes, and translating those insights into changes in maintenance strategy, operating procedures, or equipment specification. This learning loop is what allows them to continuously improve rather than simply maintain the status quo.
A Final Thought
The shift from managing assets to enabling performance is ultimately a shift in how an organization thinks about its physical infrastructure — from a necessary cost to a strategic capability.
That shift does not happen through a technology implementation or a reorganization. It happens through a sustained change in the questions that leaders ask, the metrics that get tracked, and the conversations that happen between functions.
It is, at its core, a leadership challenge. And like most leadership challenges, it is harder than it looks and more rewarding than most people expect.
If this resonates with challenges you are navigating in your own organization, I would be glad to explore it further. The Resource Hub on this site includes a downloadable version of this paper, along with other frameworks I have developed over three decades of operational work.