When CAPEX Does Not Create the Expected Value

Every year, as budget season approaches, organizations start preparing the next wave of investments.

New equipment. Automation. Digital platforms. AI infrastructure. Capacity expansion. Asset refurbishments. Safety upgrades.

On paper, most CAPEX proposals look rational.

They come with a business case. They show expected savings. They promise growth, productivity, quality improvement, risk reduction, or better service.

But there is one uncomfortable question that is not always asked with enough discipline:

Will this investment really create the value we expect — and for whom?

Because value is not seen from only one angle.

For the customer, value may mean better quality, shorter lead times, higher reliability, or improved service.

For the workers, value may mean safer work, less frustration, clearer processes, better tools, and the skills to succeed in a changing environment.

For the shareholder, value may mean profitable growth, higher productivity, better asset utilization, stronger cash discipline, and sustainable returns.

A good CAPEX decision should consider all three.

When it does not, the organization may approve the investment — but fail to capture the value.

1. CAPEX can fail because the real problem was not the asset

Many CAPEX projects do not fail because the equipment was wrong.

They fail because the organization was not ready.

A new machine is installed, but the team is not fully prepared to operate, maintain, troubleshoot, and improve it.

A new digital platform is launched, but the organization does not have the routines, data discipline, or decision-making behaviours to use it properly.

A new automation system is justified by labour reduction, but later the hidden losses appear through downtime, complexity, dependency on external support, poor maintenance capability, and lower flexibility.

A refurbishment is approved every year because the asset keeps deteriorating — but nobody challenges whether the real issue is the maintenance system, the operating discipline, or the lack of problem-solving around recurring failures.

In these cases, CAPEX becomes a way to compensate for weak management of existing assets.

And that is dangerous.

Because when cash is limited, every investment competes with another possible use of capital.

The question is not only:

“Can we afford this investment?”

The better question is:

“Are we sure this is the best way to create value?”

2. Existing assets are often underestimated

Before replacing an asset, expanding capacity, or investing in a new system, organizations should ask:

Have we fully understood the losses in the current process?

Have we improved the existing asset before asking for a new one?

Have we applied structured problem-solving?

Have we improved maintenance routines?

Have we developed the people who work with the process every day?

Have we removed the waste, instability, and poor standards that are limiting performance today?

Sometimes the answer is no.

And when the answer is no, CAPEX may not solve the problem.

It may simply move the same management weaknesses into a newer, more expensive system.

This is especially common in automation and digital transformation.

The company invests in more advanced technology, but the operating system around it remains immature.

The result is predictable:

More complexity. More dependency. More hidden cost. More frustration. Less value than expected.

3. CAPEX without capability development is incomplete

One of the most important questions in any CAPEX proposal should be:

What new human capabilities are required to extract value from this investment?

Not only technical training.

Also leadership routines. Maintenance capability. Problem-solving skills. Data interpretation. Cross-functional collaboration. Standard work. Escalation discipline. Change management.

A robot, a production line, an ERP module, a digital dashboard, or an AI system does not create value by itself.

People create value by using those systems well.

And this is where many organizations underinvest.

They approve millions in technology, but treat capability development as a secondary cost.

They invest in assets that depreciate over time, while underinvesting in people — the only asset that can appreciate with the right development.

That does not mean every investment must have a perfect financial return calculation.

Some investments are necessary for safety, compliance, ethics, or long-term resilience. Those may not always show a direct payback, but they can still be essential.

However, when the investment is justified by growth, productivity, quality, cost reduction, or competitiveness, the expected value needs to be clear.

If it cannot be fully quantified, it should at least be clearly described.

What should improve? For whom? By when? How will we know? What assumptions are we making? What risks could prevent the value from being captured? What capabilities must be built before, during, and after implementation?

Without this clarity, the business case becomes a promise.

And promises are not the same as value creation.

4. CAPEX should be managed as a value realization system

To make this more practical, I like to view CAPEX through a value realization framework — not only an approval process.

In this logic, the investment decision starts with the strategic need or opportunity.

Then it requires clarity on expected value.

Not only financial value, but also customer value, worker value, and shareholder value.

After that, the organization needs to assess capability readiness.

Do we have the right people capability? Do we have the leadership routines? Do we have the maintenance system? Do we have the standards? Do we have the problem-solving capability? Do we have the digital or data maturity required?

Then comes the discipline of understanding risk and total cost of ownership.

The cost is not only the purchase price.

It is also maintenance cost, spare parts, external dependency, training, downtime during ramp-up, data quality, change management effort, and sometimes the complexity added to the system.

Only after that should the organization move into execution and change management.

Because implementation is not the same as adoption.

A project can be technically installed and still not be operationally absorbed.

The machine can be running. The system can be live. The dashboard can be available. The automation can be installed.

But the value may still not be there.

This is why benefit tracking is essential.

Expected value must be compared with actual results.

Not only once at the end, but through the full lifecycle of the investment.

5. The real discipline starts after approval

Many organizations are good at approving CAPEX.

Fewer are good at governing value after approval.

But this is where the real discipline starts.

CAPEX governance should not be a bureaucratic review of spending status.

It should be a learning system.

Are the assumptions still valid? Are the risks changing? Are the teams ready? Are the expected benefits visible? Are we seeing unintended consequences? Are we adjusting the plan when reality is different from the business case? Are we capturing lessons for the next investment?

Some results take years to materialize.

That is normal.

But long payback periods should not mean weak follow-up.

A large investment should be monitored with the same seriousness used to approve it.

This is especially important in breakthrough innovation, automation, digital systems, and AI infrastructure.

Some investments become extraordinary value creators.

Amazon’s investment in cloud infrastructure became AWS. NVIDIA’s long-term investment in GPU capabilities positioned the company at the centre of the AI revolution.

These examples are not only about spending money.

They are about strategic conviction, capability building, timing, ecosystem understanding, and the ability to learn and adjust over time.

Not every company is Amazon or NVIDIA.

But every company can apply one important principle:

CAPEX should not be managed only as a spending decision. It should be managed as a value creation system.

That means involving different perspectives before the decision is made.

Operations. Finance. Maintenance. Engineering. Quality. Safety. IT and Digital. Supply Chain. Commercial teams. And the people closest to the work.

Each group sees different risks. Each group sees different value. Each group sees different assumptions.

When those views are not integrated, the business case may look strong — but incomplete.

And when the governance stops after approval, the organization may only discover too late that the expected value was never fully realized.

The uncomfortable conclusion

CAPEX can create growth.

It can improve safety. It can unlock productivity. It can improve quality. It can transform competitiveness. It can open new strategic possibilities.

But CAPEX can also hide weak management.

It can cover poor asset care. It can compensate for lack of problem-solving. It can create complexity the organization is not ready to manage. It can consume cash without creating the expected return.

The difference is not only in the investment itself.

The difference is in the system around the investment.

Before approving the next CAPEX request, senior leaders should ask:

Are we investing in an asset — or are we building the capability to create value from it?

Because the first one creates depreciation.

The second one creates advantage.

Final question

Do you see this problem in your organization?

CAPEX projects approved with strong business cases, but later struggling to deliver the expected value?

New technology installed, but people not fully ready to use it?

Investments justified by productivity, quality, or growth, but without strong governance to compare expected value with actual results?

If this is a challenge in your organization, this is exactly the type of work I help leadership teams address — connecting strategy, operations, people capability, and governance so investments turn into real, sustainable value.