Nobody hands you a manual when you step into your first big portfolio role.
You get a spreadsheet, a room full of competing priorities, and a calendar full of stakeholder meetings where everyone wants their project to be the most important thing happening in the organisation.
I learned most of what I know about portfolio management the hard way. After years of governing portfolios from £10m to £30m+, I can tell you that the hardest parts are never the ones people warn you about.
Here is what I wish someone had told me on day one.
- You are not managing projects. You are managing people with agendas.
Every methodology you study, weighted scoring models, strategic alignment frameworks, portfolio prioritisation matrices, assumes that decisions will be made rationally. They will not.
The minute you publish a prioritised list of projects, someone senior will appear in your inbox asking why their initiative is ranked fourth. Not because fourth is wrong. Because it is theirs.
Portfolio management is political navigation as much as it is project governance. The weighted scores are your evidence. They are not your weapon. Learn to present them as a shared tool, not a verdict.
The leaders who do this well are not the ones with the best frameworks. They are the ones who understand what each stakeholder actually cares about and can speak to that directly.
- The hardest decision you will ever make is killing a project that everyone loves.
Zombie projects are real. They are projects that no longer make business sense but continue to consume resources because too much political capital, emotional investment, or sunk cost sits behind them.
Nobody warns you that your job will sometimes require you to be the person who says: this needs to stop.
It will feel like admitting failure. It is not. Stopping a project that is no longer delivering value is one of the highest-value decisions a portfolio leader can make. Every resource freed from a zombie project is a resource available to something that actually matters.
The way to make this easier: make the decision criteria visible and agreed before a project gets into trouble. When everyone has signed up to the same definition of “this project should continue”, the conversation about stopping becomes a data discussion rather than a personal one.
- Green status reports are the most dangerous thing in your portfolio.
You cannot know the details of every project personally. You rely on the people running them to tell you the truth about how things are going.
Most of the time, they will not. Not because they are dishonest. Because they are optimistic. Because they believe they can fix it. Because they do not want to be the one who raised the red flag.
The most expensive risk in a large portfolio is a polite team.
Develop a radar for when the data is hiding the reality. Ask questions that go beyond the status report. When three projects are green and you know they share a key resource, dig in. When a project has been amber for six weeks with the same mitigation action, push harder. Your job is not to read the dashboard. It is to understand what the dashboard is not telling you.
One practical fix: make it safe and normal to raise risks early. Celebrate the team that spots a problem in week three rather than week ten. Culture shapes what gets reported.
- Saying yes to everything is the fastest way to deliver nothing.
Early in my career I believed that hard work could overcome resource shortages. I was wrong.
I said yes to too many projects, assuming we could always find a way to make it work. What actually happened was that nothing was done well or on time. Projects suffered from resource shortages. Deadlines were missed. Quality dropped. And the team burned out trying to keep pace with a portfolio that had been filled without any real consideration of what it would take to deliver it.
The busy fool trap is real. Doing everything means excelling at nothing.
The most important word in a portfolio leader’s vocabulary is no. Not no to ambition. No to projects that cannot be resourced properly, that are not aligned to strategy, or that exist primarily because someone senior wants them to.
You are a steward of organisational resources. Act like one.
- Your BAU work will eat your portfolio alive if you let it.
This one took me longer than I would like to admit to get right.
Business as usual work, the maintenance, the support, the keeping the lights on, is invisible until it is not. It does not appear in most portfolio dashboards. It does not get discussed in most portfolio reviews. And it consumes a significant portion of your team’s capacity every single week.
Define clearly what BAU means in your organisation. Separate it visibly from your change and transformation work. Understand what proportion of your total capacity it consumes before you commit to anything else.
And keep your portfolio simple. One intake channel, not nineteen. A small number of meaningful categories, not a taxonomy that requires a glossary to understand. Every column in your portfolio view should earn its place. If a stakeholder cannot act on the information in a column, remove it.
A portfolio that is simple, visible, and honest is more valuable than one that is comprehensive and impenetrable.
- The things that save you: one playbook, one source of truth, one way in.
After years of getting this wrong and then getting it right, here is what actually works.
One intake channel. Every request for new work enters the portfolio through a single defined process. No back channels. No “can you just squeeze this in”. One door.
One source of truth. One tool, one view, one place where the portfolio lives. Not twelve spreadsheets and a SharePoint site nobody can find.
A playbook. Written down. What BAU means, what change means, how things get prioritised, what each column represents and why it exists. Visible to everyone. Reviewed regularly.
Clear definitions of done. Closed projects get archived. The portfolio reflects reality, not history.
None of this is complicated. All of it requires discipline to maintain. That discipline is your job.
UserGenix 
Leave a comment