Introduction
Over the years I have participated in countless transformation discussions.
Some focused on PLM. Others on ERP. CPQ. Digital threads. Data platforms. AI initiatives. Cloud migrations. Engineering modernization.
The conversations often sounded different. The technologies were different. The business cases were different. The objectives were different.
Yet I kept noticing a familiar pattern.
Many transformation programs successfully delivered what they promised. The new platform was implemented. The roadmap was completed. The project was closed.
And yet, somehow, the expected business impact remained smaller than anticipated.
Not always. But often enough to raise an uncomfortable question.
Why do so many transformation programs improve systems while leaving business performance largely unchanged?
The more I thought about this question, the more I became convinced that many organizations are optimizing the wrong thing.
Not because the technology is wrong. But because the technology was never the thing that needed to improve.
The Transformation Conversation
Most transformation initiatives begin with a discussion about solutions.
We need a new PLM platform. We need a new ERP system. We need better master data. We need AI. We need a digital thread.
Sometimes those conclusions are absolutely correct.
But it is interesting how quickly organizations move toward solutions.
Much less time is often spent discussing a different question.
What capability are we actually trying to build?
That question sounds simple. But it changes everything.
Because systems and capabilities are not the same thing. And the distinction is one of the most important lessons I have learned.
Systems Are Purchased. Capabilities Are Built.
A system is something an organization acquires.
A capability is something an organization becomes.
The difference may sound subtle. In practice it is enormous.
An organization can buy a PLM platform. It cannot buy product lifecycle management.
An organization can buy AI. It cannot buy decision quality.
An organization can buy CPQ. It cannot buy commercial excellence.
An organization can buy ERP. It cannot buy operational effectiveness.
Technology enables capabilities. Technology does not automatically create them.
And somewhere between those two statements lies the explanation for many disappointing transformation outcomes.
The Illusion of Progress
One of the reasons this issue is difficult to identify is that transformation projects often appear successful.
Budgets are approved. Systems are implemented. Processes are documented. Training is delivered. Reports show progress.
From a project perspective, everything may look positive.
The challenge is that organizations frequently measure implementation rather than capability.
The system exists. But can people make better decisions?
Information is available. But has complexity decreased?
Processes are standardized. But is the business learning faster?
Technology has improved. But has the capability improved?
Those are very different questions. And they often produce very different answers.
The Capability Behind the System
Consider a common example.
A company struggles with product complexity. Configuration errors occur frequently. Sales and engineering become disconnected. Quotations take too long. Product knowledge becomes difficult to manage.
Eventually a transformation initiative begins. A new PLM platform is selected. Or a CPQ initiative is launched. Or both.
The technology investment may be completely justified.
The problem is that complexity management itself is the capability. The systems are only enablers.
If ownership remains unclear, if product governance remains weak and if lifecycle accountability remains fragmented, then the new platform may simply automate the old problems.
At a larger scale. And usually at a higher cost.
Why Leadership Naturally Focuses on Systems
This is not a criticism of executives. In many ways, the behavior is understandable.
Systems are visible. Capabilities are not.
Systems have budgets. Capabilities do not.
Systems have vendors. Capabilities have organizational dependencies.
Systems can be demonstrated. Capabilities often emerge gradually.
One is easy to discuss. The other is difficult to measure.
As a result, transformation conversations naturally gravitate toward technology investments.
Technology feels tangible. Capabilities feel abstract.
Yet capability is ultimately where value is created.
A Different Way to View the Business
Over time I have started asking a different set of questions.
Instead of asking, "Which systems do we have?" I ask, "Which capabilities do we depend on?"
For example:
- Product definition
- Configuration management
- Commercialization
- Lifecycle governance
- Change management
- Learning from operation
- Decision support
These capabilities exist whether organizations formally describe them or not.
They already influence performance. They already influence competitiveness. They already determine how effectively value moves through the lifecycle.
The question is simply whether we understand them.
When Capability Thinking Changes Everything
Organizations that think in capabilities often approach investment decisions differently.
The conversation becomes:
- What capability is limiting performance?
- Why is it struggling?
- What information does it require?
- Which decisions must improve?
- Which technology can support those improvements?
Notice the sequence. Technology appears later. Not earlier.
This sounds like a small change. It rarely is.
Because now technology becomes a means rather than an objective.
A capability-driven transformation often looks less exciting. But it generally produces stronger business outcomes. Because it starts with the real constraint.
The Multiplication Effect
Another reason capabilities matter is that they create leverage.
A system typically improves a specific area. A capability often influences many areas simultaneously.
Consider lifecycle learning.
Improve that capability and engineering improves. Service improves. Product quality improves. Decision making improves. Future investments improve. Customer outcomes improve.
The impact multiplies across the business.
This is one reason some capability investments produce dramatically greater returns than others. They improve multiple value flows simultaneously.
The technology itself may be identical. The capability effect is completely different.
Why This Matters Now
The pressure facing industrial organizations has never been greater.
Products are becoming more complex. Software content is increasing. Customer expectations continue rising. AI is accelerating decision speed. Business models continue evolving.
In this environment, capability weaknesses become visible much faster.
Organizations can no longer afford to spend years modernizing technology while fundamental business capabilities remain unchanged.
The cost of that mismatch is growing rapidly.
Which means leadership teams increasingly need a better way to determine where investments will create real value.
A Different Question
Perhaps one of the most useful questions a leadership team can ask is this:
If we successfully complete this transformation, what business capability will be measurably stronger?
Not which system will be implemented. Not which platform will be modernized. Not which technology will be deployed.
But what will the organization be able to do that it cannot do today?
That question forces a different conversation. And often exposes assumptions that would otherwise remain hidden.
Final Thoughts
I have spent much of my career around systems. PLM systems. Engineering systems. Configuration systems. Enterprise systems.
And I continue to believe they are incredibly important.
But I have gradually become convinced that many transformation initiatives overestimate the role of technology and underestimate the role of capability.
Technology is visible. Capability is valuable.
Technology consumes investment. Capability creates outcomes.
The organizations that consistently succeed in transformation are rarely the ones that start with systems. They are usually the ones that first understand the capability they are trying to build.
And only then decide which technology belongs in the solution.
Because systems matter. But capabilities are what actually transform the business.