Practical guide
How to use benefits evidence to prioritise a project portfolio
Compare the value and uncertainty of realistic project options, consider what the organisation can deliver and preserve the reasons for the resulting choices.
Wovex
Summary
Use benefits evidence to prioritise a project portfolio by agreeing the decision criteria and constraints, then comparing credible project options on a consistent basis. Consider expected financial and non-financial improvements, timing, confidence, dependencies and the capacity needed to realise them. Examine how plausible assumption changes affect the choice. Record the decision and trade-offs, with accountable people retaining responsibility rather than treating a score or forecast as the answer.
Agree the decision and the practical constraints
Define what the portfolio review must decide. Choosing the next initiatives to start is different from deciding which existing work to reshape or which benefit needs further investigation. Identify the options that people are genuinely able to change.
Agree the relevant objectives, decision criteria and constraints before comparing the options. Include delivery capacity and the operational work needed to realise benefits, alongside available funding. A promising project may depend on people or changes that the organisation cannot support at the proposed time.
APM describes portfolio management in terms of selecting, prioritising and controlling programmes and projects against strategic objectives and capacity. Benefits evidence contributes to that judgement; it should sit alongside the other information needed for a realistic portfolio choice.
Assemble evidence that can be compared fairly
Comparison area | Evidence to make visible |
|---|---|
Intended improvement | What should improve, for whom, and how it relates to the agreed objectives. |
Financial treatment | Whether the claim is expenditure reduction, avoided cost, released capacity or another stated treatment. |
Non-financial value | The relevant units or qualitative evidence, with enough context to interpret them. |
Timing and confidence | When improvement is expected, the assumptions and how strong the supporting evidence is. |
Dependencies | Other initiatives, adoption work or operational changes needed for the benefit. |
Capacity and commitment | Remaining delivery and operational effort, with the commitments needed for each realistic option. |
Use a consistent scope and time horizon where a comparison requires them. Keep material differences visible when a simple common basis would obscure the real decision. Different kinds of non-financial value can remain alongside one another rather than being forced into an unexplained monetary total.
Check shared benefit claims before adding values across initiatives. A contribution to a shared improvement is not necessarily an additional benefit that can enter the portfolio total again.
Compare realistic options rather than headline promises
Consider the choices available for each initiative: proceed as proposed, change the scope, defer part of the work or stop pursuing an expectation. For work already underway, include what remains to be committed and the consequences of changing course.
Separate a forecast from an observed result. An attractive estimate with weak evidence should be recognisable as such, just as a modest but well-supported improvement should remain visible. Avoid making incomplete evidence look precise through a detailed ranking.
Where a scoring method is used, explain the criteria and assumptions that shape its interpretation. A score is an aid to discussion. It does not establish causal attribution, resolve a mandatory constraint or remove responsibility for the decision.
Test what could change the preferred choice
Before agreeing a priority, test the assumptions that could materially affect it.
Identify the assumptions most important to each option’s benefits and timing.
Examine plausible changes in demand, adoption, delivery capacity or dependencies.
Check whether the relative appeal or feasibility of the options changes.
Identify the evidence that would resolve a material uncertainty.
Record what would trigger reconsideration of the chosen option.
For a fictional service portfolio, one initiative may promise a larger improvement but require a scarce specialist team and substantial operational adoption. Another may offer a smaller, better-supported improvement with fewer dependencies. The discussion should expose those conditions before treating the larger headline value as the preferred choice.
A useful outcome may be to sequence the work differently or resolve one assumption before making a wider commitment. Keep the reason visible rather than presenting the result as an automatic consequence of the numbers.
Use Wovex to support the comparison
Wovex supports initiative option comparison and portfolio prioritisation using financial, non-financial, strategic and risk-related criteria. It also connects benefits and measures with tracking and review outputs that can inform the evidence used in those discussions.
Ask for a demonstration using the options and constraints relevant to your portfolio. Inspect the assumptions, supporting evidence and how an appropriate change affects the comparison. Confirm the required plan, permissions, configuration and any applicable add-on for the proposed scope.
Keep the decision with the accountable people. Software can structure a comparison and make its basis easier to inspect; it does not establish a guaranteed best investment or remove uncertainty about future benefits.
Preserve the reasons and revisit them deliberately
Record the selected option, the main alternatives, the trade-offs and the evidence available at the time. Include important exclusions, dependencies, uncertainty and the person responsible for following up the decision.
Connect the next review to material changes rather than repeatedly reopening every assumption without purpose. A revised forecast, lost capacity or an unmet adoption dependency may justify reconsideration. Explain what changed and how that affects the decision.
Use later results to test the original reasoning and improve future comparisons. An unexpected outcome does not by itself show that the earlier decision was unreasonable; reviewers need to understand the information and uncertainty that shaped it. Keeping that context makes the portfolio’s value choices easier to explain.
Sources and context
APM supplies portfolio-management context. The comparison checklist, assumption test and service-portfolio scenario are Wovex guidance; the scenario is fictional. Apply the organisation's decision authorities and confirm the proposed software scope. A score is decision support, not a guaranteed best choice.