Strategic Portfolio Management (SPM) starts with an uncomfortable reality: there are more worthwhile initiatives than the funding and people to deliver them. So what gets backed, what waits and what gives way? A ranked list won't settle that on its own.
SPM connects those choices to strategic priorities, expected value and the funding, capacity and other constraints the portfolio has to live within. Project and programme management deliver the work and the change it is meant to achieve; SPM asks whether it is the right work in the first place. That creates a continuing loop: assess existing and proposed work, choose a feasible portfolio, make the commitments executable, and reconsider the choice when results, priorities or constraints change or new opportunities emerge.
What is Strategic Portfolio Management?
Strategic Portfolio Management (SPM) is the ongoing practice of choosing and adjusting a portfolio of projects, programmes and other initiatives so that an organisation's combined commitments advance its strategy within funding and capacity limits. That portfolio includes work already underway as well as new proposals: both compete for scarce resources.
SPM and project portfolio management (PPM) both consider the mix of work, not projects in isolation. PPM is often described as selecting, balancing and overseeing projects and programmes, sometimes with a PMO's support. SPM emphasises leadership investment choices across the wider mix of initiatives: which commitments best advance strategy, and what must give way when funding or capacity is scarce. This is a difference of emphasis, not a firm boundary. Good PPM can make these strategic choices too, and the terms are sometimes used interchangeably. Whatever the label, the test is whether strategic priorities, constraints and ongoing commitments inform the decision together.
One project can be an excellent investment and still be the wrong commitment for the portfolio. Its people may already be needed elsewhere; two projects may promise much the same benefit; or funding it may crowd out work that would do more for the strategy. None of those questions is settled by approving each business case separately. They are questions about the combined set of commitments, including work already underway.
Avoiding that combined choice doesn't make the trade-offs go away. They still happen, just later and less visibly: in overloaded teams, delayed work and opportunities that never get pursued. SPM brings those trade-offs forward, where leadership can see what each combination of work would deliver and what it would displace, and keeps them open to review as delivery evidence, benefits and circumstances change.
Who owns the portfolio's trade-offs?
Portfolio decisions cut across functions, but the leaders who control the shared funding and capacity must own the commitments and trade-offs. Finance may approve the budget, Strategy may endorse the strategic fit and a business sponsor may insist on a deadline. None of that proves Delivery has the people to do the work, and telling the PMO to "make the plan work" doesn't settle whose priorities give way. Each function sees a different part of the same decision:
- Finance tests affordability and returns.
- Strategy tests contribution to enterprise priorities.
- Business leaders bring the commitments and opportunities in their own areas.
- Delivery and resource owners test what the organisation can actually support.
The trouble starts when those views are reconciled too late, or not at all: separate approvals can each make sense within their own remit while the competition for shared funding and capacity stays unresolved. That is easy to miss when capital projects, innovation and transformation each have their own portfolio and approval process. An innovation initiative that needs capital investment and supports a wider transformation may pass through all three, each answering its own questions, without ever being weighed against everything else competing for the same money and people. A useful portfolio decision brings together those who can commit funding, set enterprise and business priorities, and confirm scarce delivery capacity, with the same alternatives in front of them and a clear view of what each would displace. Specialist approvals still have a job to do; they just can't stand in for that joined-up choice.
A PMO, where one exists, can assemble the evidence and facilitate the discussion. It should also make the consequential judgements built into the analysis visible, so leaders own them rather than inherit them: which commitments are genuinely mandatory and which are protected by choice, and which funding or capacity constraints are truly fixed. A compliance deadline may be fixed, but additional improvements bundled into the same project are not necessarily mandatory and still compete for funding and capacity. Agreed priorities narrow many disagreements; for those that remain, be clear in advance who makes the final call, so the conflict isn't left for delivery to resolve. Our article on prioritization, governance and collaboration explores how to make those perspectives work together.
To make a credible portfolio choice, those decision-makers need a shared basis for judging the work, not just separate approvals within their own functions.
How do strategic priorities inform investment choices?
Strategic priorities and credible assessments clarify the merits of proposed and existing work. They provide inputs to a portfolio decision, but they do not determine which combination the organisation can actually support.
Set priorities that distinguish alternatives
Strategic goals, set through your strategic planning process, describe the outcomes portfolio decisions should advance. Define what needs to be achieved, rather than naming the projects expected to deliver it.
But a list of goals doesn't tell you what matters most, so have leadership agree how much each one matters before proposed and existing work is evaluated. "Grow in new markets" and "protect service reliability" may both be on it, yet a proposal that does a lot for one may do little for the other. If every proposal can call itself "strategically aligned", the label tells leadership almost nothing. Make goals specific enough to assess contribution.
Identify and assess needed work
A pipeline full of worthwhile proposals can still miss initiatives the strategy needs. Work back from the agreed goals to identify gaps, rather than treating the existing wish list as the full set of options. In Leading Indicators of Strategy Failure, Ben Chamberlain contrasts this project-driven demand with starting from the strategy and breaking it down into the initiatives it requires.
The official list can also miss work that has already started. Projects begun informally still use people and funding the portfolio may appear to have spare, so check what is actually live before counting any capacity as available.
Then score the candidates, including work already underway, against criteria that reflect the goals and their relative importance, along with other factors that matter to the decision, such as risk. Financial return can be one of those factors, informing the assessment alongside wider strategic contribution. This can give reviewers a common basis for judging expected contribution before the initiatives are ranked or combined into a portfolio.
A score of 4 out of 5 looks precise, but what does it actually mean? If "customer impact" means extra revenue to one reviewer and fewer complaints to another, the scores aren't comparable. To make those assessments useful:
- Define each criterion clearly, then agree what weak, moderate and strong contribution look like before anyone starts scoring.
- Use data where it exists and expert judgement where it doesn't.
- Have people score independently first, then spend the discussion where their scores diverge, not where everyone already agrees.
Our Analytic Hierarchy Process (AHP) guide explains how to structure the criteria and build a consistent scoring model.
Use prioritisation to inform portfolio decisions
Prioritisation should test the strength of each initiative's case, not just the influence of its sponsor. Using the evaluation data, compare proposed and existing work by the contribution expected for the money and effort involved, and challenge “pet projects” whose appeal outruns their evidence. A convincing ranking makes the trade-offs clearer, but it isn't a portfolio decision. Leaders still have to decide what gets funded, deferred or stopped.
For a practical process that takes you from ranking to deciding what starts, waits or stops, see our Project Prioritization guide.
How do leaders choose a feasible portfolio?
Compare combinations against real constraints
Prioritisation compares individual initiatives; portfolio selection compares combinations. Shared teams, dependencies and work already underway can make an attractive combination impossible to deliver.
Use the evaluations to judge what each combination could contribute to the weighted strategic goals. Contributions don't always add up neatly: an enabling initiative, such as a data-platform upgrade, can look modest on its own yet be what allows a new digital service to deliver its benefits, so judge the two together rather than as separate entries in a ranking. Then test each combination's funding needs, shared-team demands and dependencies against the constraints. A combination that looks strongest on paper but exceeds available capacity is not a feasible choice.
Several initiatives may each have a credible benefit forecast and a deliverable plan, yet depend on the same business team, such as contact-centre staff, adopting major changes at once. If that team cannot absorb the combined changes, the portfolio's expected benefits may be unrealistic even though the projects can be delivered. The leaders of the affected teams are usually best placed to judge how much change is manageable. Leadership may then need to choose a different mix, reduce scope, stagger the rollouts or fund adoption support, rather than assume those forecasts add up.
With many initiatives, comparing every possible combination by hand becomes impractical. Portfolio optimisation typically uses software-based models to search combinations against agreed priorities and constraints, identifying feasible mixes expected to contribute the most value. Those estimates depend on the evaluations and assumptions behind them. Leadership can then weigh the alternatives, including what would have to wait, change or stop.
Test what would change the answer before committing. Would less specialist capacity, a lower benefit estimate or a different balance of strategic priorities change which portfolio is feasible or preferred? If a plausible change would switch the choice, leadership should see which commitments would move and which assumption drives that, rather than treat one recommended portfolio as settled. Those assumptions are also what to watch once the work begins.
Keep the reasoning behind the choice available for later review, not just the scores. For a significant commitment, record the outcome it is expected to support, the assumptions its case depends on, and what evidence should be available before its next major funding or capacity commitment. A business owner should be able to bring that evidence back, including what is still uncertain.
Example: two investments competing for the same specialists
Imagine two valuable initiatives that both depend on the same specialist team, which also has to keep day-to-day operations running: a service-improvement programme already underway for reliability, and a newly proposed market expansion for growth. The budget covers both. With its current commitments, the team cannot deliver both over the planning period, and its skills can't be hired in quickly enough to close the gap. Approving both doesn't remove the trade-off; it pushes it into delivery, where delays and firefighting decide what gives way.
Bring the choice forward instead. Here, the PMO might compare two options using the earlier evaluations, remaining cost, specialist-team capacity and dependencies:
- Protect the service programme and defer expansion. This keeps the planned reliability improvements on track but postpones growth.
- Slow the service programme to free capacity for expansion. This brings growth forward while delaying some reliability improvements.
But those might not be the only options. Ask the specialist-team owner what else uses those skills, including departmental work missing from the formal portfolio. If some of that work is discretionary rather than essential, leadership can weigh its value against the strategic work it displaces and consider deferring it. That could make supporting both initiatives feasible, but only if enough of the right capacity can actually be released when each initiative needs it.
If deferring other work isn't justified or wouldn't free enough capacity, and the agreed priorities place greater weight on service reliability for now, leadership might protect the programme. The decision records why reliability wins for now, what service improvement the remaining programme is expected to produce, and which business owner will bring outcome evidence back. It also names two triggers that would reopen the choice: service outcomes falling short of the programme's case, or expansion's case changing materially before the team is committed to the programme's next phase. The roadmap then shows expansion as "not yet", not as a parallel start. If expansion really must start sooner, leaders need to agree what changes or stops to make room.
How do portfolio choices become deliverable commitments?
Choosing which work belongs in the portfolio is only part of the decision. Leaders also need a timetable that fits shared capacity and agreements that change what teams are actually committed to deliver.
Sequence work against actual capacity
Choosing a feasible portfolio mix does not settle the timetable. A set of commitments can fit the year's funding and capacity and still overload one team in a single month, or depend on work that has not finished. Sequencing decides when initiatives start and in what order: it matches demand to capacity and, where possible, lets higher-value work deliver sooner, rather than treating approval as permission for everything to begin at once.
A credible roadmap tests demand by team and period, accounts for work already underway, and makes dependencies and deadlines explicit. Before resequencing work around a team that looks like the bottleneck, check that it really is the constraint. A team can appear to hold up delivery while it is actually waiting for inputs from elsewhere, and asking what it is waiting for can be the quickest way to find out.
If the schedule does not fit, leaders need to decide what starts later, what changes, or whether the portfolio choice itself needs reopening. Sometimes the right answer is "yes, but not yet". And when priorities, estimates or capacity change, revisit the timetable rather than pretending the original plan still works.
Make the agreed allocation executable
In the specialist-team example, protecting reliability means the sponsor and the team's resource owner agree which work gets the team's available time, and funding, resource assignments and every affected plan reflect that same choice. The PMO can keep that shared view visible and flag conflicts, but the leaders who control funding and capacity must resolve them. Otherwise an agreed portfolio can still unravel when teams act on incompatible commitments.
When should leadership reopen a portfolio decision?
Review delivery and value evidence
A project can be on time and on budget and still fail to deliver its expected benefits. Selection scores estimate what an initiative could contribute. Delivery reports show how the work is progressing. Operational outcomes and realised benefits tell a different story: whether the investment is producing the value it was meant to deliver. At review, ask which expectations and assumptions behind the original commitment are supported, challenged or still too early to judge: a benefit that has not yet had time to emerge is not automatically a failure.
Approval shouldn't give a project a free pass to keep consuming resources. As assumptions change, benefits become clearer or new demands emerge, portfolio reviews should compare the benefits still achievable, the funding and capacity the work still needs, what else those resources could support, and the costs of changing or stopping. Money already spent is not, by itself, a reason to continue or to stop. Stage gates can provide checkpoints for deciding whether work should continue, change or stop. In Portfolio Management: Influencing the Weather?, Steve Jenner describes the portfolio as a funnel, not a tunnel: work can still leave after it enters.
Annual planning may set the funding envelope, but portfolio reviews need a regular rhythm during the year. Before any significant commitment of funding or scarce capacity, including the next phase of work already underway, the leaders who own the trade-offs should also check together whether changed priorities, emerging evidence or competing opportunities warrant reopening the choice.
A review that changes the decision must also change the commitments: update the funded mix, each initiative's allocation of scarce capacity and the roadmap, so sponsors and resource owners work from the same choice. If leadership keeps the mix, keep the reason and the conditions for reconsidering it visible. Otherwise a review can change the presentation without changing the work.
Where there is a PMO, its job is to make the choices and consequences visible, not simply report progress. Leadership decides what continues, changes, waits or stops. The business remains responsible for delivering the benefits.
When expected outcomes fall short
Suppose the service programme delivers a release on schedule, but once its effect can be measured, service outcomes fall short of the programme's case: the trigger leadership recorded. The business owner revises the expected benefit of the remaining work, and the PMO compares the updated options and the capacity each needs. Leadership decides to scale back the programme's next phase and bring the expansion forward, recording what changed and why. That new choice also changes the specialist team's agreed allocation and the roadmap. On-schedule delivery didn't settle the question either way; the outcome evidence reopened it.
When a competing opportunity emerges
The programme is on schedule and reliability is improving as expected, but expansion gains a credible, time-sensitive customer opportunity that needs the same specialists. Before committing them to the programme's next phase, leadership asks three questions:
- Could this change alter what the specialists should work on?
- Would the next commitment make the alternatives materially harder to pursue?
- Does a feasible different choice remain?
If the answer to all three is yes, the PMO compares the future benefits, capacity needs, dependencies and disruption of each option. Leadership may still protect the programme. The original approval can have been right, and the programme can be performing well, while its next commitment still deserves another look.
Real example: when strategic priorities change
At the Royal National Lifeboat Institution (RNLI), workshops in the engineering and supply teams brought live projects into one shared view for the first time. The PMO then developed several portfolio options, tested for achievability as well as value, so leaders had credible alternatives to choose between. When COVID-19 shifted priorities, the PMO reweighted the agreed criteria and rebalanced the portfolio rather than starting again. Read our RNLI case study.
How can software support portfolio decisions?
Software can help find and compare the options, but leadership still owns the trade-offs. TransparentChoice software supports specific portfolio decisions by helping PMOs and executive teams structure judgement, search for feasible portfolio choices and retest decisions when circumstances change:
- Use AHP to structure leadership judgement, design criteria and assess projects against agreed priorities.
- Search combinations of initiatives for the portfolios that deliver the most modelled value against agreed priorities, within specified funding, capacity and other constraints, then compare the feasible alternatives.
- Change priorities, assumptions or constraints and retest the portfolio, so leadership can see what stays, what gives way and whether an earlier choice still holds.
To see these steps demonstrated, watch Mastering Project Prioritization, a recorded walkthrough in which Stuart Easton shows LuAnn Piccard how TransparentChoice software applies strategic priorities, project assessments, and funding and capacity constraints to compare feasible portfolio options. If you are evaluating software support for these decisions, see the TransparentChoice software overview.
Related resources
For how a PMO can build the mandate to support these decisions, see our guide to the Portfolio Management Office.
What does it take to make ongoing portfolio decisions work inside a PMO? In How to Incorporate Strategic Portfolio Management into the PMO, Deborah Yates and Stuart Easton discuss how to connect strategy with portfolio decisions, build leadership buy-in, move beyond project reporting and give executives information they can act on.
For how leaders define value and own the resulting priorities, watch Value-Based Project Selection & Prioritization with Dr. James Brown.