Portfolio Management

Portfolio management governs an organization's entire set of projects and programs — usually unrelated to each other — for strategic fit and resource allocation across all of them at once. It sits above Program Management (which coordinates related projects toward one benefit) and Project Management (a single bounded deliverable): the portfolio doesn't care whether two initiatives are related, only whether the organization's finite capacity is being spent on the highest-value mix of them.

The core question

Not "is this project on time and budget" (project-level) and not "are these related projects delivering the combined benefit" (program-level), but: given everything we could fund, is this the right set of things to be doing, in the right order, given how much capacity we actually have? A portfolio review answers that question, typically on a recurring cycle (quarterly is common), not once at annual planning and never revisited.

Strategic alignment

Every candidate initiative should trace to a stated strategic objective — an initiative with no clear line to any objective is a candidate for not funding, however individually appealing it looks in isolation. A common portfolio artifact scores or maps each initiative against the organization's strategic themes, making visible when investment is concentrated in one theme while others (perhaps equally important) are starved.

Capacity-based sequencing

Unlike a single project's schedule (built around task dependencies), a portfolio's sequencing question is about finite shared capacity — budget, specialist skills, leadership attention — that's spread across every project and program at once. Approving every strategically-aligned initiative that's individually worth doing, without checking whether capacity actually exists to deliver them all concurrently, is the single most common portfolio-level failure: everything gets partially resourced, everything slips, and nothing ships at the pace any one of them could have if sequenced rather than parallelized.

Common portfolio frameworks

• Weighted scoring model — score each candidate initiative against criteria (strategic fit, expected value, risk, cost) with organization- chosen weights, producing a ranked, comparable list.
• Bubble/matrix charts — commonly value vs. risk or value vs. effort, visualizing the whole portfolio at once rather than initiative by initiative.
• Kill criteria — explicit, pre-agreed conditions under which an in-flight initiative gets stopped regardless of sunk cost — without this, portfolio reviews tend to only ever add new initiatives, never remove underperforming ones, because stopping something already invested in feels harder to justify than starting something new.

Common pitfalls

• Sunk-cost-driven portfolio decisions — continuing to fund an initiative because of what's already been spent, rather than what it's now expected to deliver going forward, is exactly the bias explicit kill criteria exist to counter.
• Treating portfolio review as a once-a-year ritual — strategy, capacity, and initiative performance all change continuously; a portfolio locked at annual planning and never revisited drifts out of alignment with reality well before the next review.
• No visibility into actual capacity consumption — approving new work without knowing how much of the organization's real capacity is already committed is how a portfolio ends up over-subscribed without anyone having decided that on purpose.
• Conflating portfolio management with program management — a portfolio manager optimizing resource allocation across unrelated initiatives is doing a different job than a program manager coordinating interdependent projects toward one benefit; see Program Management for that distinction in full.

Learn more

• PMI: The Standard for Portfolio Management
• Management of Portfolios (MoP) — a widely-used structured portfolio methodology.
• Program Management, Project Management — the levels below portfolio management.