What a portfolio review should actually produce

Portfolio reviews have a reputation for producing documents rather than decisions. The difference is entirely in what you insist the review has to output before it is allowed to finish.

1. One list, including the work nobody counted

The first output is a single list of everything: projects in flight, work approved and not started, requests waiting, and the initiatives running inside business units that IT has not been told about.

The last category is usually the surprise. Between a quarter and a third of what is actually happening often sits outside the official list, and nothing can be balanced against work you cannot see.

2. A ranking, using a method people agreed to first

The ranking matters less than the method. Agree how items will be scored — value, risk, regulatory obligation, dependency, effort — before anything is scored, and agree it with the people whose work is being ranked.

This is not consensus-seeking for its own sake. A ranking produced by an unagreed method gets relitigated in every subsequent meeting, and the review has to be done again.

3. A capacity number

How many people are genuinely available for project work, after run, support and leave. Not the headcount. The number after everything that is already committed.

Almost every review finds the approved portfolio exceeds capacity by a large multiple. Until that gap is on a page, the ranking is decoration — everything stays approved and the sequencing happens by accident, usually by whoever escalates most effectively.

4. Stop decisions

A review that stops nothing has not happened. There will be projects that were right two years ago, projects waiting on a dependency that never arrived, and projects nobody can name a business owner for.

Each one needs an explicit decision — stop, pause with a restart condition, or continue with what it actually needs. Pausing without a restart condition is how a project becomes a zombie.

5. A process that survives the review

The final output is the mechanism: who brings demand in, how it is assessed, how often the list is revisited, and who makes the call. Without it, the portfolio drifts back to the loudest voice within two quarters and the next review starts from scratch.

The process should be small enough that people follow it. A monthly meeting with a defined intake form beats a governance framework nobody reads.

What the review is actually for

Not control. The value is that the business gets to make a real choice between things, rather than approving everything and discovering the trade-off later through delays. A portfolio that says no to something is functioning; one that says yes to everything has delegated the prioritization to chance.