Insight

Low on the list, first in line

You put your changes in order of contribution, and at the bottom sits one that delivers almost nothing. It is also the one three heavy changes are waiting on. Scoring it higher to get it moving looks like the solution, but then your list no longer holds. Contribution and sequence are two things.

in order of contribution change A change B change C change D change E at the bottom: almost no contribution so later, it seems
Frame 1 · The list

In order of contribution

You weigh your changes and put them in order. At the top what delivers the most, at the bottom what delivers the least. That is how it should be, and for most changes it works.

change E change A change B change C three heavy ones are waiting on it
Frame 2 · Who is waiting

At the bottom sometimes sits an enabler

Change E contributes almost nothing, and three heavy changes cannot start before it is finished. On the list it sits at the bottom. In reality it is holding the other three back.

score raised change E change A change B change C change D why was this at the top? nobody can look that up any more
Frame 3 · The temptation

Raising the score solves nothing

The quickest fix is to give E a higher contribution so it moves up. Then it sits at the top for a reason that is not in the score, and afterwards nobody can look up why. One such move and your list is no longer a yardstick.

change contribution enabler A high no B high no E low yes two columns, not the same score twice
Frame 4 · Two columns

Contribution is a score, enabler is a property

Keep them apart. The contribution stays what it is, and next to it sits whether other changes are waiting on it. Two columns filled in independently of each other, and both traceable.

the same list, a different order change E first, because A, B and C are waiting change A change B change C change D the score stays what it was the reason sits next to it
Frame 5 · The list reads differently

Scoring low and still going first

Now the same list shows a change with a low contribution sitting at the front, with the reason next to it. For a board that is a more convincing picture than a number somebody set too high.

How much does this contribute? Who is waiting on this change? the second question orders the list
Frame 6 · The question

Not how much does this contribute, but who is waiting on it

The first question sets the weight, the second the sequence. Ask only the first and you get a list that holds and a plan that jams.

The list holds and the order does not

A portfolio weighs its changes and puts them in order of contribution. That is the right exercise and for most changes it produces a workable order. Except for that one at the bottom, which delivers almost nothing and which three heavy ones are waiting on. On the list it comes last. In reality it has to come first.

What an enabler is

An enabler is a change other changes depend on. A migration that has to happen before anything new can be built on it. An interface three other teams need. A clean-up nobody sees and that everything else comes after.

Such changes score low on contribution, and rightly so, because on their own they deliver little. Their value sits in what they make possible, and that is something other than what they deliver.

Why raising the score is a bad idea

The quickest way to get such a change moving is to give it a higher contribution. Then it moves up the list and the problem is solved. Except that it now sits there for a reason that is not in the figure.

Three months later somebody asks why this was at the top, and the answer can no longer be found. Worse, the next time somebody wants something moved up, they now know how it is done. One raised score turns a yardstick into a negotiation.

Two columns instead of one

The solution is not complicated. The contribution stays what it is, and next to it comes a second property: is anything waiting on this change, and if so what. Two columns, filled in independently of each other.

With that, your list shows a change with a low contribution sitting at the front, with the reason next to it. For a board that is a more convincing picture than a number somebody set too high, and it is traceable as well. Anyone looking back later sees why.

What this means in practice

When we set up a portfolio practice we settle in advance what initiatives are weighed on, and what is kept alongside as a separate property. Dependencies belong in that second group. That way the score keeps meaning what it says. Read how we set up governance →

The question that brings it into view

Dependencies rarely surface on their own, because every team looks at its own change. They surface with one question, asked to everyone at the same time: who is waiting on this change, and what happens if it moves a quarter.

The answer is more often surprising than not. A change everyone thought stood on its own turns out to be the way in for two others. And a change described as blocking turns out to block only a part that can also come later.

Why this matters

A priority list that looks only at contribution is a list of what you would most like to do. The order in which it can be done is a different list. Cram those two into one column and you get a ranking nobody dares to steer by any more. Keep them apart and you can explain both.

Which change on your list is holding the others back?

In a conversation we lay your running and planned changes side by side and look at which depend on each other, and what that does to your order.