Value-Based Prioritization: Why ROI Alone Is Not Enough

Many organizations say they prioritize by value. In practice, portfolio choices can still be shaped by habit, sponsor influence, short-term pressure or whichever case is argued most forcefully.

The problem is not simply that projects need better scores. Leadership first needs a shared view of what matters, then a disciplined way to compare competing claims on the same funding and capacity.

Value-based prioritization makes those judgements explicit. Financial return can be part of the evidence, alongside strategic contribution, risk, service outcomes and other factors leadership decides matter.

In our Value-Based Project Selection & Prioritization webinar, Dr James T. Brown explores this problem with Stuart Easton and Dan Dures, including what happens when everything is treated as important and capacity is already finite.

Too Many Projects Means Less Productivity

When everything is priority one, leadership has not really made a priority decision. And when more work is started than available capacity can support, queues and competing demands slow delivery. Our Too Many Projects guide looks at the broader overload problem.

In the webinar, James argues against loading an organization to 100% and uses 90% as a practical example of leaving capacity headroom. That is a practitioner recommendation, not a universal utilization threshold. The broader point is simpler: overloaded systems lose flow as work competes for constrained capacity.

When leadership doesn’t make explicit prioritization choices, decisions don’t stop. They happen by default. Work gets picked based on:

• Personal preference
• Who shouts loudest
• Short-term pressure over long-term value

Value-based prioritization addresses the judgement problem, but it does not make capacity disappear. The aim is to make leadership priorities explicit enough to compare competing work consistently, then use those priorities alongside funding, capacity, mandatory commitments and dependencies when deciding what can actually be supported.

Where ROI Fits, and Where AHP Adds Structure

Financial measures such as ROI are useful because they make assumptions about costs and returns explicit. But they answer only part of a portfolio question: the expected financial return under a particular set of assumptions.

• Financial return is not the whole definition of value. Leadership may also care about strategic contribution, service quality, risk, resilience, regulatory requirements or other outcomes.
• Strategic priorities need to be explicit. Two investments can both have credible business cases and still compete for the same resources. Leadership still has to decide which use of funding and capacity better reflects what matters.
• Forecasts depend on assumptions. Costs, benefits, timing and uncertainty still need to be examined rather than treated as objective facts simply because they appear in a financial model.

The point is not to replace financial analysis. It is to put financial evidence inside a broader decision structure when leadership cares about several outcomes at once.

Analytic Hierarchy Process (AHP) provides one way to structure those judgements through explicit criteria, pairwise comparisons and consistency checks.

AHP adds structure by helping leadership:

• Make trade-offs explicit. Leaders compare competing priorities instead of declaring everything equally important.
• Make disagreement visible. Different judgements can be compared and discussed rather than disappearing inside an aggregate score.
• Test consistency. Pairwise comparisons can expose judgements that need another look rather than pretending every first answer is coherent.
• Clarify what “value” means. Broad goals such as safety, customer impact or growth need usable definitions before projects are assessed against them.
• Combine quantitative and qualitative considerations. Financial return can sit alongside strategic contribution, risk and other outcomes leadership decides matter.

AHP does not by itself decide which portfolio should be funded. It makes leadership judgement explicit and comparable. Funding, capacity, mandatory requirements and dependencies still determine which combinations are feasible. Some of the binding constraints may sit beyond headline budget and headcount.

A practical example comes from the American Planning Association, where board-defined criteria and weights gave executives a common basis for assessing competing work and made sponsor-protected projects more visible. The case illustrates the decision process rather than proving a universal performance uplift.

What Usually Makes or Breaks an AHP-Based Approach

AHP can still produce a poor decision process if the problem is badly framed or weakly owned. The practical issues are usually around who defines value, how criteria are written and whether the exercise is being used to explore a choice or justify one already made.

• Leadership disengagement. If senior decision-makers don’t own the value definition, the model becomes window dressing.
• Ambiguous criteria. Rushed or fuzzy definitions spark debate later, when the stakes are higher.
• Over-engineering. Too many criteria or sub-criteria turn a decision tool into bureaucracy.
• Predetermined outcomes. Using AHP to rubber-stamp decisions already made kills trust fast.
• Tool-first thinking. Spreadsheets and templates can’t fix unclear decision logic.

The practical lesson is to settle decision ownership and the definition of value before worrying about models, tools or rollout.

Does Value-Based Prioritization Save Time?

Structured prioritization can require more effort upfront than an informal scoring exercise. Its value is not guaranteed speed. It is that leadership judgement becomes explicit enough to reuse, challenge and revisit.

• Definitions can be reused. Criteria and priorities do not need to be reinvented for every decision while the underlying strategy remains relevant.
• Consistency checks focus discussion. Attention can move toward judgements that genuinely need another look.
• Disagreement becomes visible. Leaders can discuss the trade-off itself rather than arguing about unexplained scores.
• Overload still requires a portfolio choice. Better prioritization helps show what matters, but leadership still has to decide what will actually receive funding and capacity.

The point is to create reusable decision logic, not to promise that every decision will be faster.

When Several Worthwhile Options Still Compete

Defining value is only one part of a portfolio decision. Leadership still has to decide what to support when worthwhile commitments compete for the same funding and capacity.

If you are working through a live choice like that, we can explore what is changing, what is constrained and what would be worth testing in a 30-minute Decision Review. There is no fee, the conversation is confidential, and no preparation or sensitive project details are needed.

💚 If you enjoyed this article, please consider following us. It’s a small gesture that means a lot to us and encourages us to keep sharing what we learn. See the ways to follow us below ↓