Why ranking isn't enough

Most organizations with too many initiatives try to solve the problem with a list. Sort descending, draw a line. It works — until it doesn't. Here's why combination always beats ranking.

One of the most common conversations we have with leadership teams goes something like this. "We've already ranked all our initiatives. We know which ones matter most. What we need is help delivering them faster."

It's a reasonable claim. It's also, often, the wrong diagnosis.

When we look closer, it almost always turns out the problem isn't in delivery. It's that the ten initiatives that ended up at the top of the list don't work together — and no one has framed this as a portfolio problem.

What ranking does well

Before going further: ranking isn't a bad tool. It's a limited tool.

A ranked list — whether it's done in Excel, a PPM system, or on the back of a napkin — forces an organization to be explicit about what it values. It creates structure where there used to be only opinions. It gives a shared reference point for discussions. All of that is valuable.

The problem starts when you assume the list is the answer. It almost never is.

Three things a list can't capture

Imagine a portfolio of thirty initiatives. You've weighted them by value, strategic fit, and feasibility. The top ten are clearly defined. Decision made — or is it?

Here's what the list doesn't tell you:

1. What depends on what

Initiative number eight on your list might require initiative twenty-three to be done first. Initiative twenty-three was ranked low enough that it fell outside the top ten. Result: number eight is silently blocked, and no one knows until halfway through the year that the deadline won't hold.

Dependencies aren't additive. One blocked initiative can drag four others with it. A list can't compute that.

2. What actually fits

The top ten might require fourteen developers in the same sprint week in March. You have eight. The list doesn't know that. It only knows that those ten initiatives matter most — not that you'll have to choose between them.

Capacity isn't a background assumption. It's an active constraint that changes which combination maximizes value.

3. What competes with what

Two initiatives can both score high — but they might rely on the same data, the same user group, the same vendor. Running both in parallel is inefficient. Running them in sequence takes twice as long. A list doesn't show that they compete — only that each is good on its own.

Ten initiatives that are each "right" isn't the same as ten initiatives that are right together. The difference isn't philosophical. It's operational.

From list to combination

Thinking in combinations rather than rankings means changing the question you're asking.

Ranking's question: Which initiatives matter most?

Combination's question: Which set of initiatives delivers the most value together, given our constraints?

They sound similar. They're not.

The first question has a simple answer — sort descending and draw a line. The second requires accounting for dependencies, capacity, time windows, and how initiatives affect each other's value. It's mathematically more complex. It's also much closer to how portfolios actually deliver.

When does ranking still work?

To be honest: the combination perspective isn't always worth the effort.

If you have ten initiatives that are genuinely independent, roughly the same size, and capacity is plentiful — then a ranked list is fully sufficient. There's no shame in keeping things simple when simple works.

But that scenario is becoming rarer. The larger the portfolio, the more dependencies, the tighter the capacity — the bigger the gap between what the list says and what the portfolio can actually deliver. And that gap gets expensive fast.

What this means in practice

The simplest test we know: look at your last two quarterly reports. How many of the "top-ranked" initiatives delivered on the original plan? How many slipped because of a blocking dependency no one flagged? How many were re-prioritized mid-quarter because capacity didn't hold?

If the answer is "more than we'd like," it's not a delivery problem. It's a portfolio problem showing up in delivery.

And that is what strategy visualization makes possible: seeing the whole portfolio from several perspectives at once, so the combination — not just the ranking — becomes visible. More perspectives, more options, the same portfolio.

It is also what means no initiative has to be removed along the way. They all stay in the picture, ranked in their place, and when it is time to decide, leadership sees the entire portfolio at once and can choose the combination that can actually be defended.