Portfolio Value Is Negotiated Before It Is Measured

A portfolio cannot optimise value until leadership has decided what value means, for whom, and over what horizon.

The phrase “maximise portfolio value” sounds objective.

It rarely is.

A CFO may see value through cash flow, margin and return on capital. Operations may care about throughput, reliability and safety. Customers may value service, quality and speed. Engineering may prioritise platform capability and technical reuse. Government may value public benefit, compliance or sovereign capability. Employees may experience value through safer work, better tools or greater capability.

None of these perspectives is automatically wrong. The difficulty is that they cannot always be maximised at the same time.

That is why portfolio value should not be treated as a number waiting to be discovered. It is first a governance judgement about which outcomes count, how they should be weighted and which trade-offs leadership is prepared to make.

Only then does measurement become useful.

The Strategic Context

The supplied Week 5 material frames portfolio value management around the delivery of organisational goals and outcomes. It distinguishes portfolio value from narrower project delivery measures and notes that value can be financial or non-financial, immediate or long term.

Martinsuo and Killen's 2014 conceptual study strengthens that argument. They examine strategic value in project portfolios and argue that value management becomes more complex when multiple stakeholders hold different expectations. Their synthesis draws attention to collaborative sensemaking, interpretation and negotiation, particularly where strategic value includes non-commercial dimensions that are difficult to reduce to one metric.

This is an important shift in executive thinking.

Project selection systems often try to create objectivity through scoring. That discipline is useful. But if the organisation has not first resolved what it means by value, the scoring model only hides the debate inside criteria and weightings.

A portfolio can be mathematically consistent and strategically incoherent.

What Leaders Commonly Misread

The first misread is that value is synonymous with financial return.

Financial performance matters enormously in commercial organisations. Capital has a cost. Cash matters. Margin matters. Investment decisions need economic discipline.

But financial value is not the complete strategic question. A project may generate weak short-term return while building a capability required for future growth. A safety initiative may prevent losses that are difficult to value until an event occurs. A regulatory program may protect the organisation's licence to operate. A customer platform may improve retention and data access before its full economic effect is visible.

The second misread is that stakeholder value means giving every stakeholder equal weight.

It does not.

Leadership still needs to decide. Some interests are more material than others. Some are non-negotiable because of law, safety, ethics or enterprise survival. Others can be traded. The point of stakeholder engagement is not to outsource strategy to consensus. It is to understand the real value landscape before making accountable choices.

The third misread is that a quantified score eliminates negotiation.

Every scoring model embeds judgements about:

what criteria are included;
how metrics are defined;
which time horizon matters;
how uncertainty is treated;
how non-financial outcomes are weighted;
who supplies the estimates;
what minimum thresholds apply.

The negotiation does not disappear. It moves into model design.

Reframing the Issue

Portfolio value should be treated as a negotiated strategic contract between the organisation's objectives and the stakeholders whose support, behaviour or outcomes determine whether those objectives are meaningful.

That contract does not need unanimous agreement. It needs clarity.

Leaders should be able to explain:

what value the portfolio is expected to create;
which stakeholders are intended to benefit;
which forms of value are mandatory;
which outcomes are tradeable;
which sacrifices are acceptable;
when value is expected to emerge;
how assumptions will be revisited.

This creates a stronger foundation for portfolio selection than a generic business-case score.

Value Conflict Is Often Legitimate

A common governance mistake is to treat disagreement about value as evidence that one function “doesn't understand the strategy”.

Sometimes disagreement is exactly what a healthy decision process should surface.

Imagine a hypothetical manufacturing portfolio considering a highly automated production line.

Finance may favour the investment because of expected labour savings and lower unit cost. Operations may support the productivity case but raise concerns about maintenance capability and downtime risk. Engineering may value the technology because it develops automation capability. HR may identify workforce transition costs. Customers may care only if quality and lead time improve. Safety leaders may see significant ergonomic benefit.

The strategic decision is not solved by declaring one perspective correct.

The portfolio needs a value model that exposes the trade-offs.

If the investment creates attractive return but depends on a capability the organisation cannot sustain, the value case is incomplete. If it reduces cost but damages customer responsiveness, the value case is incomplete. If it creates important long-term capability with weak short-term economics, leadership must consciously decide whether that option value deserves investment.

That is governance.

Sensemaking Before Scoring

Martinsuo and Killen highlight the role of sensemaking in strategic value. This is useful because some portfolio decisions begin before the organisation has stable measures.

Sensemaking involves creating a shared understanding of what an ambiguous situation means.

For executives, that can include questions such as:

What strategic problem are we actually trying to solve?
Which stakeholders experience the current problem differently?
What would success look like in operational terms?
Which benefits are directly measurable and which will require proxies?
What value might emerge only after other capabilities are built?
What negative value could the initiative create elsewhere?

This interpretive work should occur before the portfolio model produces a score.

Otherwise, the organisation risks applying precision to a badly framed question.

Related article: From Framework Knowledge to Executive Judgement: Diagnose Before You Recommend

The Value Constitution

A practical portfolio can benefit from a short value constitution, not as a bureaucratic document but as a decision rule.

It should define five things.

1. Enterprise purpose

Which strategic objectives is the portfolio meant to advance?

2. Value dimensions

Which forms of value count? Examples may include financial return, customer outcomes, safety, resilience, future capability, compliance or societal impact.

3. Non-negotiables

What minimum conditions must every component meet regardless of financial attractiveness? Safety and legal compliance may fall here. So may strategic guardrails established by the board.

4. Trade space

Where can leaders make explicit trade-offs? A project may accept lower near-term return to build strategic capability, but only within a defined funding envelope.

5. Review conditions

What evidence would cause the organisation to redefine the expected value or change the portfolio?

This is important because value itself can change.

A strategic capability may become less important after a technology shift. A regulatory change may increase the value of compliance investment. A customer segment may decline. A new partnership may reduce the need to build an internal capability.

Value management therefore requires both initial definition and continuing reinterpretation.

Value Has Distributional Effects

Portfolio choices create winners and losers.

A transformation may improve enterprise productivity while increasing workload in one function during transition. A consolidation program may reduce cost while reducing local autonomy. A digital service may improve customer access while creating data or privacy concerns. An infrastructure program may create broad public benefit while imposing local disruption.

These distributional effects matter for two reasons.

First, they affect whether the portfolio can be implemented. Stakeholders who bear costs without seeing value can resist, disengage or create delay.

Second, they affect the ethical quality and legitimacy of the decision.

An executive value model should therefore distinguish between:

total value created and how that value and burden are distributed.

The two are not identical.

Decision Framework: The Seven Value Questions

Before approving or reprioritising a major portfolio component, ask:

1. Value for whom?

Identify the principal beneficiaries and those carrying the cost or risk.

2. Value of what type?

Financial, customer, operational, capability, safety, regulatory, societal or other?

3. Value over what horizon?

Immediate, medium term or strategic?

4. What evidence supports the claim?

Separate measured evidence, forecast assumptions and judgement.

5. What is non-negotiable?

Clarify thresholds that cannot be traded for higher return.

6. What is the opportunity cost?

What other value could the organisation create with the same capital, people or attention?

7. What would change our view?

Define the signals that would cause value to be re-estimated or the investment to be stopped.

This framework makes value explicit without pretending it is entirely objective.

From Strategy to Execution

Immediate action should ensure that major business cases state the relevant value dimensions and the stakeholders affected. Avoid forcing all value into one financial metric, but require evidence proportional to the importance of each claim.

Medium-term capability building should create a consistent portfolio value model and a governance process for resolving trade-offs. Finance should remain central, but value discussions should also draw on operations, customers, risk, capability and other functions where materially relevant.

Long-term strategic positioning requires the organisation to improve how it learns what actually created value. Portfolio reviews should compare expected value with realised outcomes and feed that learning back into future investment criteria.

This is especially important for intangible benefits. If every capability, learning or customer-value claim is accepted without later evaluation, non-financial value becomes a language for avoiding accountability.

Signals to Monitor

Value governance may be weak when:

every project claims strategic value using different language;
executives cannot explain why one non-financial benefit deserves more weight than another;
business cases monetise benefits aggressively but treat costs conservatively;
stakeholder concerns appear only after approval;
benefits are redefined after delivery to make the project appear successful;
projects with weak economics survive because their value claims are too vague to test;
financial return dominates even where strategy explicitly depends on capability, safety or future preparedness;
the portfolio reports delivery status more clearly than value status.

A strong portfolio can explain not only whether initiatives are on track, but what value thesis each initiative is testing.

References

Martinsuo, M. & Killen, C.P. 2014, 'Value Management in Project Portfolios: Identifying and Assessing Strategic Value', Project Management Journal, vol. 45, no. 5, pp. 56-70.
Project Management Institute 2017, The Standard for Portfolio Management, 4th edn, Project Management Institute, Newtown Square, PA.
University of South Australia, Portfolio Stakeholder Engagement & Portfolio Value Management, Week 05 study notes and student materials supplied for this synthesis.

Questions for the Leadership Team

Who currently has the greatest influence over what our portfolio counts as value?
Which value dimensions are non-negotiable, and which are legitimately tradeable?
Where are we using financial precision to avoid discussing strategic uncertainty?
Which stakeholders bear costs or risks that are not visible in our current value model?
How often do we revisit the definition of value after strategy or external conditions change?
Can we identify projects whose value case depends mainly on claims that are never measured after delivery?
What evidence would cause us to conclude that an initiative no longer creates sufficient strategic value?

Closing Perspective

Value does not become objective simply because it is placed in a spreadsheet.

The strongest portfolio decisions combine measurement with explicit judgement. They recognise that different stakeholders see different outcomes, that some forms of value emerge slowly and that trade-offs cannot be eliminated by scoring.

The executive responsibility is therefore to make the value logic visible before capital is committed.

Measure what can be measured. Challenge what is assumed. Negotiate what is genuinely contested. Then make the choice and remain accountable for it.

About EraNorth Insights
EraNorth Insights publishes practical analysis on strategy, projects, operations, transformation and decision intelligence for professional and organisational use. About EraNorth.