By Kevin Price | Global Head of Enterprise Asset Management

Here’s a familiar story to most, have you heard it as well?

It’s Monday morning and the leadership team is reviewing the capital plan.

One of the organisation’s most critical assets is becoming increasingly difficult to rely on. The team has done its homework. They understand the operational risk, the consequences of failure, the cost of maintaining the existing equipment and the impact that an outage could have on customers and production.

The investment case is compelling and the objective is clear: reduce operational risk and improve the long-term resilience of the operation.

Funding is approved. Everyone leaves the meeting feeling good about the decision. So far, so good.

How Strategic Intent Gets Lost in the Translation

A few weeks later, the project team receives the approved initiative, but they don’t necessarily receive Monday morning’s conversation. They receive a project brief, a budget, a target date and a scope that effectively says: replace the existing asset.

Engineering gets involved and starts developing the technical solution. They identify equipment that meets the specification and begin making design decisions. Procurement starts talking to suppliers. There are choices to make between different equipment options, delivery dates, warranties and prices.

Finance keeps an eye on the approved budget while operations is busy running the plant. Maintenance may not become deeply involved until someone starts thinking about commissioning, spare parts or the maintenance program. In other words, everyone is doing their job. And that is, believe it or not, exactly where things can start to go wrong.

The Tuesday Afternoon Decision Nobody Talks About

Imagine the engineering team discovers two viable equipment options.

Option A costs less and comfortably meets the technical specification.

Option B is slightly more expensive but provides better reliability, makes condition monitoring easier and is already commonly used elsewhere across the organisation, meaning technicians understand it and spare parts are readily available.

Which option gets selected?

If the project team is looking primarily at its budget, Option A might be the sensible choice.

But remember why the organisation approved the investment. It wasn’t simply to replace a piece of equipment, it was to reduce operational risk and improve resilience.

That context can completely change the conversation.

The problem is that several months after the investment committee approved the business case, the people making Tuesday afternoon’s equipment decision may have little visibility of the assumptions and outcomes that drove Monday morning’s investment decision. That’s the translation gap and nobody made a bad decision.

Perhaps the most important point is that projects don’t always drift away from strategy because somebody made a bad decision. Quite often, everyone makes perfectly reasonable decisions based on the information, responsibilities and incentives in front of them. The investment team optimises the portfolio, finance manages capital, engineering optimises the design, procurement negotiates commercial terms.

The project manager protects scope, schedule and budget, operations protects production, and maintenance thinks about reliability and maintainability.

All perfectly reasonable.

But if those decisions aren’t connected to a common understanding of why the organisation is making the investment, local optimisation can gradually undermine the wider objective. Everyone can be right, and the project can still be wrong.

What Happens to an Investment as It Travels Through an Organization

Strategic intent almost always gets lost in the translation from one step to the next. Think about what happens to an investment as it moves through your organisation:

It might start with: We need to reduce the operational consequences of failure and improve the resilience of this critical process.

Then it becomes: We need to replace this aging asset.

Then: We need to procure a replacement that meets these specifications.

And eventually: We need to deliver this equipment by October for this budget.

None of those statements is necessarily incorrect, but notice what disappeared along the way.

The outcome. The project gradually became about delivering the asset rather than delivering the reason the organization wanted the asset in the first place. That distinction matters.

Why the Business Case Shouldn’t Disappear Once the Money Is Approved

In many organisations, enormous effort goes into developing the investment case. Teams analyse alternatives, asset condition, risk, cost, operational impact and expected benefits. Then the investment gets approved and something strange happens.

The business case has effectively done its job.

Attention moves from “Why are we doing this?” to “How quickly can we deliver it?”

But approval shouldn’t be where the investment conversation ends — it should be where it becomes real. If reliability justified the investment, reliability should still influence design decisions. If reducing lifecycle cost mattered, procurement should understand that when evaluating equipment alternatives. If operational resilience was the objective, the project team should be able to see whether a proposed change increases or decreases that resilience.

And when circumstances change, the organisation should be able to ask:

“What does this mean for the outcome we originally wanted?”

Not just:

“What does this mean for the schedule and budget?”

Connecting Investment Planning to Project Delivery

Go back to that engineering team choosing between the two pieces of equipment.

This time, alongside the specification, cost and schedule, they can see the original investment rationale. They know which operational risks the investment was intended to address. They understand the assumptions behind the business case. They can see that lifecycle reliability and resilience were important factors in approving the investment.

Suddenly Option B isn’t simply the more expensive alternative — it’s the right decision. It’s the option actually better aligned with the investment the organization approved.

The technology hasn’t changed. The decision context has. And that can be enormously powerful for everyone involved.

From Project Success to Investment Success

This is why connecting investment planning, project delivery and asset operations matters.

The goal shouldn’t simply be better handoffs between departments. It should be preserving a continuous thread through the entire process:

Strategy → Investment → Decision → Project → Asset → Outcome

A project manager still needs to manage cost and schedule. Engineering still needs to deliver a technically sound solution. Procurement still needs commercial discipline. Operations and maintenance still need assets they can operate and maintain effectively.

But everyone should also be able to understand how the decisions they make connect back to the outcome the organisation originally wanted.

Because ultimately, finishing a project is not the same thing as realising an investment.

A project delivers an asset. An investment is supposed to deliver an outcome.

Closing the gap between those two ideas is one of the biggest opportunities for asset-intensive organisations to get more value from the capital they are already spending.

And perhaps that is the real reason good strategies sometimes produce bad projects. The strategy didn’t necessarily fail. The organisation simply lost sight of it along the way.