Choosing what to stop: making portfolio priorities deliverable

A priority becomes credible when the organisation makes room to deliver it.

A strategy can be selective while its portfolio remains crowded. Leaders agree a small number of priorities, yet existing projects continue, new requests enter the system and the same specialists appear in several delivery plans. Each initiative may be defensible on its own. Together, they can exceed the organisation's ability to act.

The executive task is to choose a deliverable combination of work. That requires a view across initiatives, a willingness to make trade-offs and a practical way to release capacity when the choices change.

The UK Major Projects Authority's 2014 priorities connected portfolio decisions with resource constraints and interdependencies. That historical reference provides useful context; the approach below is an editorial framework for executive teams. Major Projects Authority priorities.

Start with the whole demand on the organisation

Create one view of the work competing for the people and capabilities needed to deliver the strategy. Include committed programmes, proposed initiatives, essential maintenance and operational obligations. A portfolio that excludes routine demand can overstate the capacity available for change.

Use a consistent short description for each initiative: its intended outcome, accountable sponsor, next commitment, principal dependencies and demand on scarce roles. Capture enough detail to support a choice without asking teams to rebuild every business case.

Record uncertainty. A project with no credible estimate should appear as an unresolved demand, not as a small demand. Distinguish approved resources from resources that teams hope to secure later.

Separate obligations from choices

Some work responds to an obligation or a fixed external deadline. Other work is discretionary, even when its sponsor considers it important. Make this distinction explicit and ask the relevant owner to confirm the basis of any claimed obligation.

An obligation may constrain the outcome or completion date while leaving choices about scope, sequencing and implementation. Examine those choices rather than treating the entire proposed solution as mandatory.

For discretionary work, state the strategic contribution in concrete terms. Which outcome will improve? What evidence supports that expectation? Which other initiative pursues the same outcome? Similar language in different business cases can conceal duplication or an opportunity to combine effort.

Test the capacity that actually limits delivery

Budget is only one constraint. A portfolio may depend on a small group of operational leaders, data specialists, procurement staff or subject-matter experts. Their availability should be tested across the sequence of work, including the periods when operations need them most.

Use time-bounded capacity discussions with the managers who allocate these people. Ask what work they can realistically support and what commitment would have to move if another initiative starts.

In a hypothetical service organisation, two programmes might both need the same operational managers to redesign processes and train teams. Funding both does not resolve the collision. The choice may be to sequence the programmes, narrow one phase or secure suitable additional capacity before proceeding.

Compare combinations, not only individual scores

Agree a small set of decision criteria before ranking proposals. Strategic contribution, urgency, delivery readiness, operational disruption and dependency risk may all matter. Explain what each criterion means so that different sponsors are answering the same question.

A score should organise the evidence, not make the decision automatically. Examine the portfolio created by the ranking. A collection of highly rated initiatives may still share a critical dependency or place too much change into one service at the same time.

Compare viable combinations. One might prioritise early service improvement; another might invest first in the capabilities needed for later change. Set out the consequences of each, including the benefits delayed and the commitments that become more reliable.

Make the decision to pause or stop executable

Use clear decision states: continue within agreed limits, sequence for a later start, pause pending specific evidence, or close. Avoid leaving initiatives nominally active while expecting their teams to infer that they are no longer priorities.

A pause needs a review date, an owner and a condition for restarting. Closure needs a proportionate plan for open obligations, affected stakeholders, useful work already produced and the release of people or resources. Consult the appropriate commercial or specialist functions where commitments require it.

Record the reason for the decision. A project can be well managed and still lose priority because another use of capacity offers greater strategic value. Keeping this distinction visible helps leaders have a more candid discussion about the portfolio.

Control new demand after the prioritisation meeting

The portfolio will not remain stable simply because leaders approved a list. Establish a clear route for considering new requests and changes to existing scope.

For each proposed addition, show its effect on the current commitments. Identify whether it uses genuine spare capacity, requires more resources or displaces another piece of work. Bring that consequence to the person or forum authorised to decide.

Reserve capacity for uncertainty where the operating context warrants it. Do not silently allocate every available hour and then treat an urgent request as a failure of team effort. The size and use of that reserve should be an explicit management judgement.

Review whether the choices are holding

Portfolio review should examine whether the assumptions behind the choices remain credible. Look for unresolved resource conflicts, changes in strategic need, dependencies that are slipping and benefits that no longer justify the remaining effort.

Keep the discussion focused on decisions. If a constraint has emerged, ask which commitment must change and who can authorise that change. Repeated reporting of the same conflict is evidence that the portfolio needs an intervention.

Finish each review with an updated set of commitments that delivery teams and operational owners recognise. A useful portfolio tells people what they should advance, what they can defer and where leadership has accepted a trade-off.

Executive questions

• Which priority lacks the capacity needed to deliver it?
• Where do separate plans rely on the same people at the same time?
• What will we pause or stop if we approve the next initiative?
• Which assumption would cause us to change the current sequence?
• Can teams see the decisions we have made in their actual workload?

JP Associates helps executive teams connect strategic priorities with delivery capacity, test competing commitments and establish a practical basis for portfolio decisions.