Ask your portfolio office what it did last quarter. If the answer is a list of things it looked at rather than a list of things it declined, you have built the wrong institution.
There are two organisations that can plausibly be called a portfolio function, and they do different work.
The first selects. It sits between demand and capital, receives more proposals than it can fund, and decides which ones proceed. Its output is a set of decisions — this, not that — and the decisions are visible because some proposals do not survive them. Its central discipline is opportunity cost.
The second supervises. It receives work that has already been approved elsewhere, groups it by theme or sponsor or business unit, tracks its progress, and reports on it in aggregate. Its output is visibility. Its central discipline is consolidation.
Both are useful. Only one of them is doing the job the word portfolio implies, and a great many organisations have built the second while believing they have built the first. The distinction is not semantic: it determines whether anyone in the enterprise is systematically asking what is being sacrificed to fund what.
The Strategic Context
The literature is reasonably clear about which of the two is meant. Morris and Jamieson, in research published in Project Management Journal in 2005, report that within the four companies they studied, portfolio management was used primarily to select and prioritise programmes and projects, not to manage programmes or projects. Three of the four implemented it mainly as a process for selecting and prioritising the right projects. The paper also carries the distinction, attributed there to Cooke-Davies, that portfolio management is predominantly about choosing the right project, whereas project management is about doing the project right.
That is the design intent, and the case evidence supports it. The pharmaceutical company in the study had a dedicated portfolio management practice that played a very important part in development, reviewing and rebalancing formally every six months. In their own striking phrase, portfolios essentially formed the hand from which the future of the company was being played.
Set against this, the same paper reports something from its survey that points the other way: most respondents perceived portfolio management to be about managing projects around a common theme rather than maintaining a balanced portfolio or selecting the right project — a perception the authors note runs contrary to the literature.
That survey figure must be handled carefully and is offered here only as indicative. The authors put the response rate at about 2% — 75 replies, roughly half of them from one country — and are explicit that this is far too few to treat as statistically valid, describing their own study as exploratory at best. It cannot tell us how common the supervising model is.
What it can do is name the gap — between what portfolio management is designed to do and what a set of practitioners reported believing it was for. That gap is worth an executive's attention regardless of its prevalence, because it is checkable inside a single organisation in about twenty minutes.
What Leaders Commonly Misread
The first misreading is that a portfolio view is the same thing as portfolio management. A consolidated view of everything in flight is genuinely valuable — it reveals dependencies, exposes capacity conflicts, and prevents the same work being commissioned twice. But visibility is not allocation. An organisation can have a complete, well-maintained, beautifully reported portfolio view and still make every funding decision one initiative at a time, in isolation, on the merits of the paper in front of the approver.
The second misreading is that prioritisation is selection. Ranking approved work is not the same as choosing between candidates. By the time an initiative appears in a priority list it has already been funded, staffed and announced; the ranking sorts what will be done first, not what will be done at all. The consequential decision happened earlier, elsewhere, and usually without comparison.
The third misreading concerns where the decision actually sits. In many enterprises the real selection is performed by the annual budget process — each business unit receives an envelope and decides within it — and the portfolio function then assembles the results. Under that arrangement the portfolio function is structurally incapable of selecting, because selection has already occurred at a level of aggregation where cross-business comparison is impossible. This is a legitimate operating model. It is not portfolio management, and calling it that obscures the fact that nobody is comparing an initiative in one division against an initiative in another.
A fourth misreading is that supervision at least does no harm. It does one specific harm. A supervising function generates the impression that the portfolio is being governed, which reduces the pressure to build the selecting function. The organisation reports portfolio maturity while its capital continues to be allocated by whoever asks most persuasively.
Reframing the Issue
The reframing is to judge the function by what it declines, not by what it observes.
A selecting function produces a visible, countable stream of decisions not to proceed. Those decisions are its product. If the function has never declined anything, or declines only proposals that were going to fail anyway, it is not selecting — it is validating.
This gives an executive a test that takes minutes and cannot be argued with. Ask for the list of proposals the portfolio function considered in the last twelve months and the list it declined. If the second list is empty or trivially short, the answer is settled regardless of what the terms of reference say.
Two further consequences follow from taking the reframing seriously.
Selection requires a surplus of demand. A function that receives exactly as many proposals as it can fund cannot select; it can only approve. Organisations that want a selecting function must deliberately generate more candidate initiatives than they intend to fund, which feels wasteful and is the price of choice.
Selection requires comparability. Two proposals cannot be compared unless they are expressed in commensurable terms. This is where most selection functions actually fail — not through lack of will but because a regulatory initiative, a growth initiative and a resilience initiative arrive in three incompatible currencies, and the function has no agreed method for converting them.
There is also a comparator that is missing rather than incomparable. Every candidate is implicitly assessed against the alternative of not proceeding, and in most organisations that alternative arrives with nothing attached to it at all — which distorts every ranking built on top of it, as [Related article: What Is the Risk of Not Doing It?] sets out.
Strategic Analysis
The comparability problem, and a workable answer
A telecommunications business will typically have, in any given year, a spectrum acquisition, a network resilience upgrade, a regulatory compliance programme, a customer platform replacement and a cost-out initiative competing for the same capital and the same scarce engineers.
Only one of those has a clean financial case. The compliance programme has no return and cannot be declined. The resilience upgrade prevents losses whose probability is contested. The platform replacement enables revenue nobody can size. Confronted with this, most selection processes retreat to the only common denominator available — cost — and end up choosing the cheapest, which is a decision rule nobody would defend if it were stated aloud.
The workable answer is not to force everything into a single financial number. It is to sort candidates into a small number of classes that are compared within class and allocated between classes by an explicit executive judgement about balance. Compliance and licence-to-operate work is sized, not ranked. Growth initiatives compete against each other on expected value. Resilience competes on exposure reduced per dollar. The executive decision is what proportion of the envelope each class receives — and that is a genuine strategic choice, made once a year, rather than an arithmetic exercise performed on incomparable numbers.
The corollary is that a portfolio function which reports a single ranked list of everything is almost certainly producing a false ordering.
A related caution applies within a class. Comparing two candidates requires that both be expressed in the same unit, and the unit tends to change as an initiative moves from investment case to delivery plan — the mechanism examined in [Related article: From Margin to Milestones: What Happens to Strategy on Its Way Down]. A portfolio function comparing delivery-level numbers is comparing the wrong quantity.
Balance is a decision, not an outcome
The literature's phrase is maintaining a balanced portfolio, and it is frequently treated as a diagnostic — measure the spread across horizons, risk levels or business units, and note whether it looks reasonable.
Treated as a decision instead, it becomes considerably more useful. Balance is the answer to a question the executive team must actually answer: how much of our capacity are we willing to commit to work whose return is distant and uncertain, given what we owe in the current year? That is not a measurement. It is a position, and it should be stated as one before the proposals arrive, because after they arrive it will be argued backwards from whichever proposals are most persuasive.
Value management, and a caution about it
The same research reports indicative survey figures on the use of value management — a process for optimising the value of a proposed strategy, most commonly expressed as benefit over resources used, and frequently combined with risk management.
These figures deserve less weight than any other in the paper, and the authors say so themselves: they note that the coverage and depth of some topics, value management among them, were limited, and that some of the terms may not have been well known to respondents. The concept is worth knowing — expressing candidate initiatives as benefit relative to resource consumed is exactly the commensurability discipline described above — but nothing here supports a claim about how widely it is practised.
Selection is not the only decision that must be renewed
Choosing well at the outset does not settle the matter. The authority granted to an initiative at selection is itself a bounded thing that should lapse and be renewed, which is a separate governance instrument examined in [Related article: Authority With an Expiry Date]. An organisation that selects rigorously and then delegates indefinitely has made one good decision and no subsequent ones.
What supervision is genuinely for
None of this argues for dismantling the reporting function. Aggregate visibility does real work: it surfaces the same person committed to four initiatives, it catches duplicate commissioning, and it gives the enterprise a capacity picture that no single sponsor can see.
The argument is that these are capacity and dependency functions, and they should be named as such rather than described as portfolio management. Naming them accurately has an immediate benefit: it makes visible that nobody is doing the other job.
The decision to continue or stop a single initiative already under way is a different instrument again, with its own logic, treated in [Related article: What a Stage Gate Is Actually For]. Selection asks which candidates to start; the gate asks whether one already started should carry on. An organisation can be good at one and poor at the other, and most are.
A final caution about evidence. Organisations frequently point to a maturity assessment as proof that portfolio management is in place. What such an assessment measures, and who it is really produced for, is examined in [Related article: Who Is Your Maturity Rating For?] — and a rating is not a substitute for the decline test below.
Decision Framework
Five tests, run against the function as it actually operates rather than as its charter describes it.
1. The decline test. How many proposals did the function decline in the last twelve months, and can you name three? An empty answer settles the question.
2. The surplus test. Does the organisation generate more credible candidate initiatives than it intends to fund? If not, selection is arithmetically impossible and the function is validating by construction.
3. The comparability test. Take two live initiatives from different classes and ask on what basis one was preferred to the other. If no answer exists, they were never compared, and the portfolio is a sum of independent approvals.
4. The timing test. At what point in the year is the consequential allocation decision actually made, and is the portfolio function in the room? Where allocation happens in the budget process and the portfolio function assembles the result afterwards, its role is administrative whatever its title.
5. The balance test. Has this leadership team stated, in advance and in writing, what proportion of capacity goes to each class of work? If the split is only visible retrospectively, balance is an outcome the organisation observes rather than a choice it makes.
Where a function fails three or more, the honest response is not to reform it but to rename it — and then to decide, separately and deliberately, whether the enterprise wants a selecting function at all.
From Strategy to Execution
Immediate. Run the decline test at the next executive meeting. It requires no preparation and no analysis, and the discussion it produces is usually more candid than any review commissioned for the purpose. Follow it with the timing test, which identifies where the decision really sits.
Medium term. If the organisation wants a selecting function, three things must change together, and changing one without the others fails. Demand must exceed supply by design. Candidates must arrive in classes with an agreed comparison basis within each. And the function must hold the authority to decline, not merely to advise — which means the executive that currently approves initiative by initiative must give something up.
Long term. Build the habit of stating balance before proposals arrive. This is the least procedural and most valuable of the changes, because it converts the annual capital conversation from an argument about individual initiatives into a decision about what kind of enterprise this is going to be over the next three years.
What the organisation retains from investing in the portfolio capability itself — the method, the tooling, the trained people — is a further question, and a different one, examined in [Related article: What Does the Enterprise Own After a Capability Investment?].
Signals to Monitor
- A decline rate of zero. The single most diagnostic figure available, and one almost no organisation reports.
- Proposals that arrive pre-approved. When an initiative reaches the portfolio forum with a sponsor, a budget line and a start date already set, the forum is ratifying.
- Ranked lists that mix classes. A single ordering that contains a compliance obligation, a growth bet and a resilience upgrade is producing a false comparison and should be read as evidence about the method, not about the initiatives.
- Balance discussed only in retrospect. If the split across horizons or risk classes appears in the annual review and not in the annual decision, it is being observed rather than chosen.
- Capacity conflicts discovered during delivery. These indicate that selection did not consider capacity, which means it was not really selection — it was approval with a schedule attached.
- The same business unit funded at the same level every year. Stable allocation across cycles is possible and sometimes correct. It is more often the signature of an envelope process wearing portfolio language.
Questions for the Leadership Team
- What did our portfolio function decline in the last twelve months, and can anyone in this room name three?
- Where and when is the consequential allocation decision actually made — and is that the same place our governance chart says it is?
- On what basis was our largest growth initiative preferred to our largest resilience initiative, and did anyone perform that comparison?
- Have we stated, in advance, what share of capacity goes to obligation, to growth and to resilience — or do we discover the split afterwards?
- Do we generate more credible candidates than we can fund, and if not, what is our selection process actually selecting between?
- If we renamed our portfolio function according to what it does rather than what it is called, what would we have to call it?
Closing Perspective
The word portfolio carries an implication that most organisations have not earned. It implies choice under constraint — a set of holdings deliberately composed, with the composition itself being the decision.
What many enterprises operate instead is an inventory: a complete, well-reported, carefully tracked list of everything already committed, updated monthly and governed by nobody in particular. The inventory is useful. It is not a portfolio, and while it exists the organisation will believe the allocation question is being handled.
The test is simple enough to run before lunch. Ask what was declined. If nothing was, the function is watching the capital, not allocating it — and somewhere in the enterprise, the decisions that determine what gets built are being made one at a time, by whoever was most persuasive on the day.
About EraNorth Insights
EraNorth Insights publishes practical analysis on strategy, projects, operations, transformation and decision intelligence for professional and organisational use. About EraNorth.