Read Full Story — Construction
A firm running seven to eight medium and large projects at once had left each project to the initiative of its own project manager; centralized portfolio-level visibility had never been established.
Since each project manager used their own Excel format or tracking method, senior management had to meet individually with each project manager to understand a project's real status. A budget overrun or schedule slip on a project was usually noticed only at the point where the project manager was already trying — and failing — to solve it alone, meaning far too late.
A three-phase structure was built that provided visibility rather than control:
A single status report template was designed, to be filled out the same way across all projects under three main headings: budget, schedule, and risk.
The newly established central PMO collected and consolidated reports rather than making decisions for project managers; its role was deliberately limited to providing visibility, not control.
The monthly portfolio meeting dedicated time only to at-risk (red) projects; this directed senior management's time to where it was most needed.
After ten months, senior management could track the entire portfolio through a single consolidated report. Risk-bearing delays began to be noticed the moment they emerged, rather than at the point where a project manager had already exhausted their own attempts to fix them.
In a multi-project portfolio, the real risk is not one project being poorly managed, but the overall state of the portfolio being invisible. A light, standard reporting discipline is a foundational step that should come before any heavy software investment.
Share this content:
Comments (0)
No comments yet. Be the first to write one.