Portfolio Management: Choosing the Right Projects to Do
The capacity constraint is universal. Every organisation, regardless of size or sector, generates more project ideas than it has the people, budget, and organisational bandwidth to execute well simultaneously. The question is not whether to choose between projects — that choice happens regardless, either through a deliberate portfolio process or through the ad hoc accumulation of commitments until the organisation grinds to a halt trying to do everything and finishing nothing. Project portfolio management — PPM — is the discipline that makes that choice explicit, structured, and aligned to strategy rather than to whoever has the most political capital in this quarter's budget cycle.
The selection criteria: what makes a project worth doing
Strategic alignment. The first question in any portfolio evaluation is whether the project advances the organisation's declared priorities. A project that is well-executed but does not contribute to strategic objectives is a distraction, not an investment. Strategic alignment scoring typically maps each proposed initiative against the organisation's strategy on a defined scale, sometimes weighted by the relative importance of each strategic priority. The discipline this requires — having clearly defined strategic priorities to score against — is itself valuable: organisations that cannot articulate their strategic priorities clearly cannot make coherent portfolio decisions.
Return on investment. Financial return is the most familiar selection criterion and the most frequently gamed. NPV, payback period, and internal rate of return are the standard financial evaluation tools, but they require revenue and cost projections that are notoriously optimistic at the project proposal stage. Organisations with mature portfolio processes apply reference class forecasting — adjusting projected returns based on the historical performance of similar projects in the organisation — to counteract the systematic optimism bias that inflates benefit estimates in project business cases. Non-financial returns — regulatory compliance, employee experience, customer satisfaction, risk reduction — should be scored and weighted alongside financial returns rather than treated as unquantifiable.
Risk. Risk in portfolio selection has two dimensions: the probability that the project delivers its expected benefits, and the consequence if it does not. A project with a high expected return and low execution risk is more valuable than a project with the same expected return and high execution risk. Portfolio-level risk analysis also looks at concentration: a portfolio where all projects depend on the same technology platform, the same external vendor, or the same small team of subject matter experts has portfolio risk that exceeds the sum of individual project risks. Scenario analysis — examining what the portfolio looks like if two or three high-risk projects fail simultaneously — is a useful discipline that most organisations skip.
Dependencies. Project dependencies — cases where one project's deliverable is a prerequisite for another project's start — constrain the sequence in which projects can be executed regardless of their individual priority scores. A dependency map that makes these relationships visible is an essential input to portfolio sequencing. Dependencies also create risk: if Project B depends on the output of Project A, a delay in Project A cascades into Project B's timeline unless the dependency is actively managed. The portfolio process should identify these dependencies and either eliminate them through project redesign or build dependency buffers into schedules.
Resource availability. The most sophisticated portfolio scoring model is irrelevant if the projects it selects require more people than the organisation has available. Capacity planning — matching the resource demands of the selected portfolio against actual availability by skill type and time period — is the step where many portfolio processes break down. Organisations routinely approve portfolios that assume 120 per cent utilisation of key resources, creating a queue of in-flight projects where each is delayed because the resources it needs are already consumed by others. True capacity planning requires honest assessment of how much productive capacity is available after operational work, meetings, and unplanned demand.
Portfolio balancing: managing the mix
A portfolio of entirely short-term, low-risk, incremental improvement projects generates near-term returns while eroding long-term competitive position. A portfolio of entirely long-duration, high-risk transformation initiatives bets the organisation's future on a set of projects that may take years to deliver any value — and most of which will not deliver as expected. Portfolio balancing applies the logic of a financial investment portfolio: maintaining a deliberate mix across time horizon (near-term versus long-term), risk level (incremental versus transformational), and type (revenue growth, cost reduction, risk mitigation, regulatory compliance). The appropriate balance varies by industry and strategic context, but the discipline of consciously managing the mix rather than letting it emerge from individual project decisions is a consistent feature of high-performing portfolio management.
The governance process: from intake to active rebalancing
A portfolio management process has four structural elements. Intake is the standardised process by which project proposals enter the portfolio pipeline — a business case template that collects the information needed for consistent evaluation across proposals. Scoring and prioritisation applies the selection criteria to rank proposals and identify which to fund. Stage-gate funding releases project resources in phases, with continued funding contingent on demonstrated progress at defined gates — rather than approving the full project budget upfront and hoping delivery follows. Active rebalancing is the ongoing discipline of adjusting the portfolio as circumstances change — adding high-priority projects that emerge mid-year, stopping projects that are no longer viable, and reallocating resources from lower-priority to higher-priority work.
Common failure modes
The pet project problem is the most pervasive failure mode: a senior leader sponsors an initiative that would not survive objective portfolio scoring, but political capital overrides the process. No prioritisation — approving every project that clears a minimum threshold rather than making explicit trade-offs between them — produces a portfolio that is too large for the organisation's capacity. The "zombie project" is a related failure: a project that has lost its rationale but continues to consume resources because stopping it requires admitting the original decision was wrong. Organisations with mature portfolio governance treat stopping a project as a normal, expected outcome of an effective portfolio process, not as a failure requiring explanation.
If your organisation is building or improving its project portfolio management process — from the selection criteria and governance structure to the capacity planning and rebalancing disciplines that make prioritisation real rather than theoretical — XNM's program and project delivery practice works with organisations to design portfolio management frameworks that are rigorous enough to improve decision quality and practical enough to be sustained through normal organisational life.