Before leaders ask whether an investment produces an attractive return, they must be clear about what the organisation is trying to maximise—and what it refuses to sacrifice in the process.

A board can approve a project with a positive net present value, a strong internal rate of return and a short payback period and still make the wrong decision for the enterprise. The mathematics may be correct. The problem may sit one level above the mathematics: the organisation has not agreed what success actually means.

This is not a semantic problem. It is a governance problem. Every metric directs attention. Every target changes behaviour. Every investment criterion privileges one type of outcome over another. When leaders reward revenue growth, managers pursue revenue. When the dominant measure is margin, teams protect margin. When utilisation is the operational priority, people fill capacity. When a public agency measures only delivery volume, it can produce more outputs while weakening the outcome it exists to create.

The first question in investment governance is therefore not, “What is the return?” It is, “Return against what enterprise objective?”

The Strategic Context

The supplied material on corporate finance frames investment as a forward-looking decision: organisations commit scarce capital today in expectation of future economic gains. Capital budgeting concerns what to invest in; capital structure concerns how investment is financed; working capital concerns whether the organisation can continue to meet day-to-day obligations. These are different questions, but they all depend on an underlying view of what the organisation is trying to achieve.

Gary Fields' Bottom Line Management makes that dependency explicit. His central argument is that sound decisions require clarity about the organisation's overriding objective or objectives. The decision problem changes depending on whether the organisation is a profit-seeking company, a public body, a university, a charity or another form of institution. The relevant “bottom line” is not necessarily accounting profit, but the outcome against which the organisation ultimately judges whether it is doing better or worse.

For an executive team, this creates a practical discipline. Investment analysis should not begin inside the finance model. It should begin with a clear statement of enterprise purpose translated into decision criteria.

A manufacturer may seek sustainable economic profit while protecting safety, quality and customer trust. A hospital may need to improve patient outcomes within funding constraints. A defence organisation may prioritise mission capability and resilience where the benefits cannot be reduced to commercial cash flows. A technology company may accept lower near-term returns to build a platform capability that changes its future competitive position.

These are not excuses to abandon financial discipline. They are reasons to apply it in the correct decision context.

What Leaders Commonly Misread

A common mistake is to assume that because a measure is precise, the objective behind it must also be clear.

It is not.

A portfolio can contain dozens of projects with well-developed business cases while leadership remains ambiguous about the enterprise outcomes those projects collectively serve. In that environment, selection becomes a contest between local sponsors. Projects are justified using whatever measure is easiest to defend: revenue, savings, regulatory necessity, customer demand, risk reduction or strategic importance. The organisation appears analytical but is actually negotiating priorities project by project.

A second mistake is to confuse local optimisation with enterprise optimisation. A project can make a department more efficient while making the wider system slower. A procurement decision can lower unit cost while increasing inventory, lead time or quality risk. A transformation program can reduce headcount in one function while transferring workload to another. A digital initiative can increase transaction speed while creating support, cyber or data-governance obligations that are not visible in the originating business case.

Fields' discussion of bottom-line decision-making is useful here because it challenges shorthand rules. Decisions should be judged by whether the rule used tends to improve the organisation's actual objective, not by whether the result looks favourable in isolation.

The third mistake is to treat constraints as afterthoughts. Safety, ethics, regulatory obligations, capacity, liquidity and reputation are not variables that can always be traded away for a higher financial return. Some are hard constraints. Others are thresholds. A decision framework that does not distinguish objectives from constraints invites the organisation to optimise the wrong thing.

Reframing the Issue

The strategic question is not “Which KPI should we use?”

It is:

What outcome are we trying to improve, what constraints must remain protected, and what evidence will show that an investment genuinely contributes to that outcome?

This reframing creates three levels of measurement.

The first is the enterprise objective: the result leadership ultimately wants to improve. Depending on the organisation, this may include economic value, mission effectiveness, health outcomes, service performance or a deliberately balanced set of objectives.

The second is the decision criterion: the measure used to compare alternative uses of capital or capacity. NPV, IRR, lifecycle cost, risk reduction, benefit-cost analysis and strategic scoring can all sit here, but only when their role is clear.

The third is the operating metric: the measure used by teams to control execution. Schedule, cost variance, throughput, defect rates, utilisation, service levels and adoption can be important without being the enterprise objective themselves.

Confusion arises when level three becomes level one. A project delivered on time is not automatically valuable. A machine running at high utilisation is not automatically profitable. A program spending its budget is not automatically successful. An AI model with high benchmark performance is not automatically safe or useful in the operating environment.

The distinction is simple, but it changes governance.

Strategic Analysis: Metrics Create Behavioural Architecture

Metrics do more than report performance. They influence resource allocation, incentives and attention.

If executives consistently approve projects based on payback, the portfolio will tend towards investments that recover cash quickly. That may be appropriate in a liquidity-constrained environment, but it can systematically disadvantage longer-horizon capability building. If projects are ranked only on percentage return, smaller high-return investments may crowd out larger initiatives that create more absolute value. If managers are assessed on annual budget performance, they may defer maintenance or capability expenditure that improves long-term economics but worsens the current year's result.

This is why the metric eventually shapes the organisation.

A useful executive test is to ask what behaviour would emerge if every manager optimised the chosen measure perfectly. If the answer is undesirable, the measure is incomplete or incorrectly positioned.

Consider a hypothetical manufacturing portfolio. One project automates inspection and reduces labour cost. Another improves process capability and reduces variation. A third modernises maintenance systems and reduces the probability of extended downtime. If selection is based only on immediate labour savings, the first project may dominate. Yet the second could improve quality, yield and customer performance across several product families, while the third protects a production constraint whose failure would affect the entire factory. The “best” project depends on the enterprise objective and the system in which the investment operates.

Portfolio leaders therefore need more than ranking mathematics. They need a hierarchy of value.

At minimum, this hierarchy should separate:

  • outcomes leadership is trying to maximise;
  • minimum conditions that must be satisfied;
  • risks that must be controlled;
  • scarce resources that constrain the portfolio; and
  • measures used to verify benefits after investment.

This also changes the role of strategy. Strategy is not a list of themes attached to projects after they are proposed. It defines the choices that determine what qualifies for investment in the first place.

Related article: Capital Allocation Is More Than Choosing Positive-NPV Projects

Decision Framework

A practical way to improve investment governance is to require every material proposal to pass five tests before detailed financial ranking.

1. Objective test — What enterprise result is this intended to improve?

The answer should be specific enough that two executives can independently recognise whether the investment contributes to it.

2. Causality test — How does the investment produce the claimed result?

Map the chain from expenditure to capability, from capability to operational change, and from operational change to benefit. This exposes business cases that jump directly from activity to value without showing the mechanism in between.

3. Constraint test — What must not be damaged while pursuing the benefit?

Identify safety, quality, regulatory, liquidity, customer, workforce, environmental and reputational thresholds that limit acceptable choices.

4. Alternative test — What else could we do with the same capital, people and executive attention?

The opportunity cost of an investment is not zero simply because funding exists.

5. Verification test — What evidence after implementation would prove that the expected value was realised?

Benefits should have owners, baselines and review points. Otherwise the organisation approves value but manages delivery.

These five tests do not replace NPV, IRR or other financial tools. They establish the decision architecture within which those tools become meaningful.

From Strategy to Execution

In the immediate term, executive teams should review major investment templates and remove ambiguity between strategic objective, financial measure and delivery metric. A business case should not be allowed to use phrases such as “strategic alignment” without identifying the strategic outcome and the causal link.

In the medium term, portfolio governance should build an explicit value taxonomy. For a commercial enterprise this may include economic value, growth option value, risk reduction, customer value and capability development. For a public organisation it may also include mission, social, environmental or service outcomes. The categories should be few enough to govern, not an unlimited catalogue that allows every project to claim strategic importance.

Longer term, leadership incentives and capital-allocation processes should be tested for coherence. If the strategy calls for resilience but every investment decision privileges short payback, the system will underinvest in resilience. If leadership wants innovation but punishes failed experiments regardless of decision quality, teams will avoid uncertainty. If the organisation wants enterprise optimisation but budgets and targets remain functionally isolated, local optimisation will continue.

The operating system has to support the strategy.

Signals to Monitor

Watch for signs that the organisation is optimising proxies rather than outcomes:

  • projects consistently meet delivery targets but realised benefits remain unclear;
  • investment proposals use different definitions of value depending on the sponsor;
  • strategic initiatives are repeatedly deferred because short-term financial measures dominate;
  • departments improve their KPIs while end-to-end performance deteriorates;
  • business cases have detailed cost estimates but weak counterfactuals and benefit baselines;
  • executive debates focus on ranking scores rather than the assumptions behind them.

These are not merely reporting weaknesses. They indicate a problem in the decision architecture.

Source Notes

This article draws principally on Gary Fields, Bottom Line Management (Springer, 2009), and the supplied chapter Financial Decisions and Investment Criteria, which frames corporate finance around capital budgeting, capital structure and working capital. Full bibliographic details for the latter source were not available in the supplied extract. [SOURCE DETAILS REQUIRED]

Questions for the Leadership Team

  1. What is the enterprise outcome we are genuinely trying to optimise over the next three to five years?
  2. Which current KPIs are useful controls, and which have quietly become substitutes for the real objective?
  3. What behaviours would emerge if every manager optimised our current investment criteria perfectly?
  4. Which constraints are non-negotiable even when a project offers a higher financial return?
  5. Where are functions currently improving local performance at the expense of the end-to-end system?
  6. How often do we verify that approved benefits were actually realised after project delivery?

Closing Perspective

Investment discipline begins before the spreadsheet. A financial model can compare cash flows, but it cannot decide what the organisation exists to accomplish. That responsibility sits with leadership.

The metric selected for investment decisions eventually becomes a behavioural instruction to the enterprise. Choose it without clarity and the organisation can become highly efficient at producing the wrong result. Define the outcome first, distinguish objectives from constraints, then use financial and operational measures in their proper place. That is how metrics become instruments of strategy rather than substitutes for it.