Blog
Minimum Viable PMO: Start With Value, Not Scale
A Minimum Viable PMO does not start with an organisation chart, a methodology handbook and a new tool. It starts with a single management question that nobody can answer reliably today. A recent GPM case report describes how a CIO’s question about projects, risks and required action became the starting point for a lean PMO service.
The first service must improve a decision
In this case, project information scattered across the organisation was brought together in a simple CIO list and prioritised by impact and urgency. It was only through actual use that the next gaps became visible: traceable evaluation logic, clear questions and transparent scores. The roadmap grew out of real decisions rather than desk-based design.
This is in line with PMI’s current “Bridging the Gap” study. Drawing on a survey of 1,905 PMO and senior leaders and more than 40 in-depth interviews, PMI asks PMOs to focus more strongly on strategy, value and the expectations of their internal customers. The 2025 Practice Guide from PMI also places measurable value and continuous improvement at the centre.
For building a PMO, this leads to four principles:
- Problem before structure: Which recurring management decision is currently suffering from poor visibility?
- One service before a catalogue: Start with the smallest dependable answer to that question.
- Use before perfection: Test the service on real projects and improve only what genuinely supports decisions.
- Expansion before tool purchase: New processes or software need a proven bottleneck, not just an available checkbox.
A concrete pattern for IT portfolios
In a fragmented IT portfolio, I would not start with a complete PMO model. The first service would be a single decision-ready portfolio view: project owner, next committed milestone, current forecast, greatest risk and the next management decision required.
A view like this belongs in a fixed steering rhythm, backed by a decision log. Every red indicator has to lead to an option, a decision owner and a due date. If the list only reports status and triggers no decision, it remains reporting, not yet an effective PMO.
What project leaders should do now
Formulate one management question, choose a lean service to answer it, and set a review after four weeks: Which decision became earlier, clearer or possible at all? Then make a deliberate decision on whether to deepen the service or add the next one.
The metric that matters is not how many PMO processes have been introduced. It is how much decision friction the first service removes.