Get a portfolio view you would be willing to defend in front of the people it describes.
A PMO is accountable for telling the truth about a portfolio it does not control. Status arrives as a color typed in under deadline pressure by someone with fifteen minutes and no incentive to alarm anyone. Roll a hundred of those up and you get a report that is precise, confident, and wrong in exactly the places that matter. The job is making accurate reporting the path of least resistance.
What goes wrong from this seat
Green on the outside
The update is due Thursday at five. The owner has a release on Friday and fifteen minutes to fill in the field. Green is the answer that generates the fewest follow-up questions, so green is what gets typed. Nobody lied; the form rewarded speed over accuracy. If a status field is faster to complete dishonestly than honestly, the portfolio report mostly measures how busy people were on Thursday afternoon.
Ninety percent for six weeks
Percent complete is an estimate of effort spent dressed up as an estimate of work remaining. It moves quickly through the easy middle and then stalls, which is why so many projects sit at ninety for a month and a half. Ask instead for the next dated milestone and whether that date moved since the last update. A slipping date is information; a stable percentage is not.
A portfolio with no line to the strategy
Forty active projects, each with an owner, a budget, and a status color, and nobody can say which of the company's three priorities each one serves. The portfolio becomes a list of things in flight rather than a claim about where capacity is going. Map every project to an objective as it enters the portfolio; the ones that map to nothing are the conversation worth having.
The week spent collecting
Monday to Wednesday chasing owners, Thursday assembling, Friday distributing, and no time left to notice that three projects are competing for the same two specialists. Collection crowds out analysis, which is the part only the PMO is positioned to do. Anything you have to chase for is a signal that the number should be produced where the work happens rather than requested afterwards.
What to look at, and how often
Framework-neutral. Whether you run OKRs, Scaling Up or 4DX, the rhythm below is the part that most often gets dropped.
| When | What |
|---|---|
| Weekly | Exceptions only. Which projects moved a dated milestone since last week, which changed scope or owner, and which are newly blocked. Anything still tracking to plan needs no airtime and no narration. |
| Monthly | The resource picture. Where the same named people appear across several committed projects, and which commitment gives way when they collide. This is the analysis nobody else in the company is positioned to produce. |
| Quarterly | Close the portfolio honestly: what shipped, what was cancelled, and what quietly continued without anyone deciding it should. Re-map the survivors to the new quarter's priorities and retire the orphans. |
| Annually | Review intake itself. How did work enter the portfolio this year, how much of it was ever tied to a stated objective, and what would you refuse to accept next year without one? |