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.
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.
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.
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.
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.
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.
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 →
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.
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.
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.