Every organisation I work with has a project list. Very few have a portfolio strategy. The difference is not a tool. It is a decision that leadership has or has not made.
The project list trap
It usually starts with good intentions. Someone creates a central overview. Finance adds budget columns. IT adds resource columns. PMO adds RAG status. The list grows. Filters are added. A PowerPoint is built for the board.
This is called portfolio management. It is not.
A project list tells you what exists. A portfolio strategy tells you what should exist and what should stop existing. The first is administration. The second is leadership.
What portfolio management actually requires
Which initiatives are we funding because they create value and which because stopping them is uncomfortable?
If we could only run 60% of our current projects, which 60% would we choose?
Who has the authority — and the accountability — to make that decision?
The third question is the hardest. Because it requires someone to say no. And in most organisations, the governance model does not make clear who that someone is.
The AI acceleration problem
The speed of AI-driven change means that project portfolios are growing faster than leadership capacity to evaluate them. Everything feels urgent. Everything has a business case. Nobody wants to be the person who stopped the wrong initiative.
The result: too many projects, too few decisions, and a portfolio that reflects political history rather than strategic intent.
The solution is not a better tool. It is a clearer steering logic — who decides, on what basis, with what frequency.
One test for your portfolio
How many projects on your current list would survive a real prioritisation conversation?
If the answer makes you uncomfortable - that discomfort is the signal.
Reply - I am curious what you find.
Cordula Buss · Plan A2C · Structure First
Helping Finance and programme leaders build steering logic that works.