Portfolio management and project management get used as if they are different scales of the same activity. They are not. Project management is about delivering a specific scope on time and budget. Portfolio management is about deciding what projects should exist at all, how they relate to organisational strategy, and which ones should be stopped to make room for better ones. The disciplines are complementary, but the organisational leverage of portfolio management is higher because the right project delivered well produces more value than the wrong project delivered well.
Why Project Lists Are Not Portfolios
Most organisations have a list of active projects, often maintained in a PMO tool, sometimes broken into categories, occasionally ranked by priority. This is a project list, not a portfolio. A portfolio has a defined investment envelope, explicit selection criteria, formal balancing across categories (strategic vs run-the-business, mature vs emerging, near-term vs long-term), defined governance for adding and stopping projects, and ongoing performance review against portfolio-level objectives. Project lists do not have these structural elements.
The Hard Discipline: Stopping Projects
Most portfolio governance is well-developed for adding projects and underdeveloped for stopping them. Once a project is approved, it tends to continue regardless of changed circumstances — the original case getting weaker, better alternatives emerging, the team learning the project will not deliver the value originally promised. Strong portfolio management treats stopping projects as a normal governance act, not as evidence of failure. Sunk-cost discipline, regular value reassessment, and willingness to redirect resources to better-performing projects is what prevents the portfolio from clogging with inertial work.
Selection Criteria That Are Actually Used
Most organisations have a project intake process and selection criteria. Most of the time, the selection criteria do not actually filter — the projects approved match the projects requested at high rates. This usually indicates that the criteria are scored after the decision is made, not used to reach the decision. Useful selection criteria are applied before the decision is reached, produce different rankings than executive intuition would, and result in some projects not being approved. Criteria that always rank requested projects high are documentation, not governance.
A useful test for a portfolio process: in the past year, how many proposed projects were rejected, and on what basis? If the rejection rate is near zero, the portfolio process is rubber-stamping rather than governing. The rejection rate does not need to be high — but it does need to be non-zero and the criteria for rejection need to be defensible.
Balancing the Portfolio
A portfolio without explicit balance tends to converge on whatever projects are easiest to justify in the moment. Short-term, predictable, ROI-friendly projects tend to crowd out long-term, uncertain, strategic ones — even when leadership genuinely wants more strategic investment. Explicit allocation across categories (run-the-business, transform-the-business, growth, compliance) prevents drift, but only if the allocation is enforced rather than aspirational. A 70/30 stated split that produces a 90/10 actual split is a stated policy nobody is implementing.
Portfolio Reporting That Drives Decisions
- Resource allocation against strategy — does spend reflect stated priorities?
- Forecast value vs actuals across recently completed projects — is the portfolio delivering?
- Concentration risk — are too many projects depending on the same scarce resources?
- Pipeline strength — what is in flight, what is being prepared, where are the gaps?
- Stop rate — how often does the portfolio actually stop a project, and on what evidence?
- Strategic coverage — are there strategic priorities that have no funded portfolio response?
The Senior PfMP and Why It Signals Something
PMI's Portfolio Management Professional (PfMP) credential is held by considerably fewer practitioners than PMP. The smaller number partly reflects the fact that fewer roles operate at portfolio level, but it also reflects how few practitioners deliberately develop the discipline. Senior portfolio leaders whose careers continue to advance are typically operating with portfolio thinking that has been deliberately practiced — and the credential, while not the source of the capability, signals the deliberate practice.