Introduction
In the previous article, I argued that many transformation initiatives focus on systems when they should focus on capabilities.
That distinction is important. But it immediately creates a new problem.
If capabilities matter so much, which ones deserve investment?
This is where many leadership teams become stuck.
Because almost every capability appears important.
Product development is important. Configuration management is important. Lifecycle governance is important. Commercialization is important. Aftermarket support is important. Data management is important. Decision support is important. Learning is important.
The list never seems to end. And unfortunately, budgets do.
Which means the real challenge is often not identifying worthwhile investments. The real challenge is understanding which capabilities create disproportionate value.
Because not all capabilities are equal. And treating them as equal may be one of the most expensive mistakes organizations make.
The Fairness Trap
One pattern I have noticed throughout my career is that organizations often distribute investments relatively evenly.
Every function has legitimate needs. Every department has improvement opportunities. Every manager can present a convincing business case.
And individually, many of those business cases are correct.
The challenge is that transformation is not about fairness. It is about leverage.
An organization that spreads investment equally may create satisfaction. It does not necessarily create impact.
Because some capabilities improve local performance. Others improve the entire system.
Understanding the difference is one of the most important responsibilities of leadership.
Why Everything Looks Important
The problem becomes clearer when viewed from inside individual functions.
Engineering sees engineering constraints. Sales sees commercial constraints. Service sees operational constraints. IT sees technology constraints. Finance sees financial constraints.
Each perspective is valid. Each perspective identifies real opportunities.
The difficulty is that every capability tends to look strategically important from the place where it lives.
This makes prioritization extremely difficult.
When everyone has evidence, everyone has needs and everyone can demonstrate value, how do you choose?
The answer, I believe, is that you stop looking at functions and start looking at flows.
Local Value Versus System Value
Consider two hypothetical investments.
The first improves engineering productivity by ten percent.
The second improves how product knowledge moves between engineering, sales, manufacturing and service.
Both may be valuable. But they behave differently.
The first creates local optimization. The second affects multiple capabilities simultaneously.
The first improves execution. The second improves coordination.
The first helps one function. The second improves the entire lifecycle.
This distinction is often overlooked.
Because traditional business cases typically evaluate benefits within organizational boundaries. The largest opportunities frequently exist across them.
The Multipliers
Over time I have become increasingly interested in what I think of as multiplier capabilities.
Capabilities that make other capabilities stronger.
For example:
- Product lifecycle governance
- Product knowledge management
- Configuration management
- Decision support
- Lifecycle learning
- Cross-functional accountability
These capabilities may not always produce the most visible short-term benefits. But they often influence a large number of downstream activities.
Improve lifecycle learning and engineering improves. Service improves. Quality improves. Decision making improves. Future investments improve. Customer outcomes improve.
One investment creates multiple effects.
That is a multiplier. And multipliers are where transformation economics become interesting.
The Hidden Mathematics of Transformation
Many transformation programs still evaluate investments one capability at a time.
The thinking often looks like this:
"This initiative saves X."
"This process improves by Y."
"This department gains Z."
Those calculations are useful. But they are incomplete.
Because capabilities interact.
The value of a capability is rarely limited to its own output. Its value often depends on how many other activities it influences.
A capability that improves ten different value flows may generate vastly greater business impact than a capability that improves only one, even if the direct benefits initially appear smaller.
This is one reason transformation outcomes are often difficult to predict.
Organizations measure direct effects. The strongest effects are frequently indirect.
The Capability Portfolio
The longer I work with transformation, the less I think about individual projects.
Instead, I increasingly think about capability portfolios.
Every organization is already investing in capabilities, whether intentionally or not.
Hiring decisions are capability investments. Process improvements are capability investments. Technology implementations are capability investments. Governance decisions are capability investments. Training initiatives are capability investments.
The question is not whether investments are happening. The question is whether they are aligned.
Because capabilities either reinforce each other or compete with each other.
And leaders who understand this tend to make very different decisions.
The Capabilities Nobody Owns
One of the most interesting observations is that some of the most valuable capabilities often lack clear ownership.
Nobody owns lifecycle learning. Nobody owns lifecycle context. Nobody owns decision quality across the lifecycle. Nobody owns cross-functional product knowledge.
Everyone contributes. Nobody controls.
As a result, these capabilities frequently receive less investment than they deserve.
Not because they are unimportant. Because they are difficult to place on an organizational chart.
And what lacks ownership often lacks priority.
The Danger of Chasing Symptoms
This creates another common trap.
Organizations frequently invest in the area where the pain appears.
Sales struggles. Invest in sales tools.
Engineering struggles. Invest in engineering tools.
Service struggles. Invest in service processes.
Sometimes this is exactly the correct decision. But sometimes the visible problem is merely a symptom.
A sales challenge may originate in product definition. A service challenge may originate in configuration strategy. An engineering challenge may originate in lifecycle governance.
If leaders invest only in the visible symptom, they may improve performance locally while leaving the underlying constraint untouched.
The organization becomes more efficient without becoming significantly more effective.
Why This Matters More Than Ever
The pressure on industrial companies continues increasing.
Product complexity is growing. Software content is growing. Customer expectations are growing. Decision cycles are shrinking. Competition is accelerating.
In this environment, investment mistakes become more expensive.
Organizations can no longer afford to improve everything. They must become better at identifying what matters most.
Not the loudest problem. Not the most visible problem. The most influential problem.
Those are rarely the same thing.
A Different Investment Question
Many organizations ask: "What should we improve?"
I increasingly believe a better question is:
Which capability would improve several other capabilities if it became stronger?
That question changes the conversation dramatically.
Because now we are not simply looking for value. We are looking for leverage.
And leverage is where transformation creates disproportionate returns.
Not every capability deserves identical investment. Some capabilities support the entire system. Others support only themselves.
Learning to distinguish between the two may be one of leadership's most important responsibilities.
Final Thoughts
One of the biggest challenges in transformation is that almost every proposed investment sounds reasonable. And often it is.
The difficulty is not separating good ideas from bad ideas.
The difficulty is separating important capabilities from multiplier capabilities.
Important capabilities help the business operate. Multiplier capabilities help the business improve.
The difference may sound subtle. In practice, it changes how organizations compete.
Because the companies that consistently outperform their peers are rarely the ones investing the most.
They are often the ones investing in the capabilities that make every other investment more effective.
Understanding which capabilities create that leverage is where transformation becomes a leadership challenge rather than a technology challenge.
And it is also where many of the most difficult executive decisions begin.