From delivery logic to investment logic

Here is the problem

A delivery PMO has no instrument that answers that. It can tell you a project is eighty percent complete and running to plan. It cannot tell you whether the remaining twenty percent is a better use of the organization's scarcest people than something that has not been started.

Those are different questions, and only one of them is about delivery. The second is an investment question, and it is being asked of a function built to report on execution.

The governance language has caught up

The direction of travel in portfolio governance is toward treating every project as an investment rather than a commitment: something with a forecast return, a remaining cost, and a decision attached to it that can be revisited. That framing is becoming the expected language at board level.

The vocabulary moved faster than the tooling. Most portfolios still run on a delivery model underneath, so the investment question gets asked in a governance forum and answered with a delivery report.

Why this is not a delivery problem

A value management office runs the same portfolio on different arithmetic. It asks what each project returns against what is left to spend on it, and it ranks work by what it earns on the resource that is actually scarce, rather than by who asked loudest.

The measure that carries this is DIPP, Stephen Devaux's metric for project investment health. It asks the forward-looking question: given what remains to be spent, is finishing this still the best thing these people could be doing? A project can be on time, on budget and still fail that test, which is exactly the case a delivery report cannot surface.

Put the same logic across the portfolio and the effect compounds. Work that shares people is sequenced by what it returns rather than by when it was approved, and the projects that should wait are visible before they start consuming the constraint rather than after.

What changes for the head of a PMO

Very little of the existing function is wasted. The data a delivery PMO already collects is most of what the economic view needs. What changes is the question it is put to.

• Projects are ranked by return on remaining investment, not by stage or sponsor.
• Sequencing decisions are made against the capacity of the teams the work shares, not against a calendar.
• Stopping or deferring a project becomes a normal economic decision rather than an admission of failure.

None of it begins with hiring more people or imposing another methodology. It begins by modeling the portfolio differently and making the sequencing choice explicit.