Why Your IT Portfolio
Reporting Is Failing Leadership.

The problem with most IT portfolio status reports is not the data. It's the question they're designed to answer. They tell you what happened. But the leaders sitting in the steering committee need to know what to decide.

The update/decision gap.

After managing a large IT project portfolio at MAN Truck & Bus, I spent a lot of time redesigning how we reported upwards. The original process produced a 40-page deck every two weeks that nobody read in full. The key steering questions, which projects need escalation, where is the budget going, what should we stop, were buried somewhere on slide 24.

The fundamental issue: reporting and governance had drifted apart. The reports were written by project managers updating their status. They were consumed by a steering committee that needed to make resource allocation and de-prioritisation decisions. These are completely different jobs.

Three questions that actually matter.

After running the redesign, we landed on a structure built around three questions that leadership was actually trying to answer in every steering meeting:

1. Where are we at risk of missing commitments? Not a list of red projects. A clear signal of which projects, if they fail, will materially affect something the organisation has committed to: a regulatory deadline, a cost saving target, a capability needed by another team.

2. Where is the budget actually going vs. where we planned it to go? Budget variance isn't interesting as a single portfolio number. It's interesting by strategic priority bucket. Are we overspending on maintenance while underfunding transformation? That's a governance question, not an accounting one.

3. What decisions do we need to make today that can't wait until next cycle? This is the hardest one to get right. It requires someone, not the project managers, to look across the whole portfolio and identify escalations that are time-sensitive. This became the PMO's main value-add.

What we changed.

We moved from a project-status-first to a governance-question-first structure. The main output became a single Power BI dashboard with three views mapped to those three questions, fed by data from Jira and our financial system. The 40-page deck became a 6-slide steering pack: two pages of exception reporting, two pages on budget, two pages of recommended decisions.

Report preparation time dropped by roughly 40%. More importantly, the average steering meeting went from a review session to an actual decision-making forum. Projects started getting stopped faster when they needed to be. Budget got reallocated within cycle rather than waiting for annual planning.

The key structural move was separating the data collection job (project managers updating Jira and finance fields) from the insight synthesis job (PMO reviewing signals across the portfolio and framing escalations). Once those roles were clear, the reporting almost organised itself.

If you're redesigning your portfolio reporting.

Start by sitting in on your next three steering meetings without any report in front of you. Write down the questions leadership actually asks, not the ones you anticipated. Then redesign your reporting structure so it pre-answers those questions. You'll probably find the current report answers about 30% of them well, ignores 40%, and provides a lot of information leadership doesn't need at all.

The goal isn't a prettier dashboard. It's a governance meeting where decisions happen.