Why so many PMOs disappoint
Many organisations already have a PMO, and many complain about it. The criticism is almost always the same: the project office collects, consolidates and circulates, but nothing changes in the way projects are decided. Project managers see it as an administrative burden. Leadership sees it as yet another dashboard, rarely up to date on the day it is needed.
The cause is rarely the competence of the people. It lies in the mandate. A PMO asked to “monitor projects” produces monitoring. A PMO asked to inform three specific decisions (which projects to launch, which to strengthen, which to stop) organises itself around those decisions, and everything else follows: the information to collect, the frequency of check-ins, the format of reports.
This is the starting point of our work. Before talking about method or tools, we clarify with you the decisions the PMO must make possible and the level of the organisation at which they are taken.
The three PMO models and how to choose
There is no single PMO model, but a family of structures whose role varies according to the power given to them.
- The supportive PMO provides templates, good practice and help on request. It suits organisations where projects are autonomous and the priority is to harmonise practices without adding weight.
- The controlling PMO checks the application of a common framework: milestones, mandatory deliverables, phase reviews. It suits situations where differences in practice create risks or prevent consolidation.
- The directive PMO manages projects directly and assigns project managers. It suits critical programmes, when leadership wants single accountability for delivery.
To this first reading is added that of scope: a project, a programme or the entire portfolio. A directive enterprise PMO has nothing in common with a supportive PMO attached to a single project. The choice is made on simple criteria: the maturity of project managers, the risk level of the portfolio, the culture of the organisation and, above all, the real support of leadership. For a detailed definition of these notions, see our glossary entry on the definition of the PMO.
Our approach: start small, on real decisions
Our consultants work within your teams; decisions remain yours. We advise against deploying a complete framework in one go. A methodological framework delivered as a single block is often bypassed. We prefer a path in three stages.
A short assessment. Interviews with leadership, project managers and business teams, review of existing governance bodies and materials. The findings fit in a few pages: what works, what is missing, and the action priorities.
A minimal foundation on a pilot scope. A common project sheet, a risk register, a progress check-in at a fixed pace and a dashboard reduced to the essentials. The aim is for a first steering committee to decide on the basis of this foundation, and for everyone to see the difference.
Gradual extension. Widening the scope, adding resource and dependency management, then linking with project portfolio management when the organisation is ready to make trade-offs between projects rather than simply monitor them.
Throughout the engagement, we work in pairs with your teams. A PMO designed by consultants and handed over to a team that did not build it does not survive their departure.
What a good PMO dashboard contains
The temptation is to measure everything. A useful dashboard answers few questions, but it answers them reliably.
- Where are we? Progress against committed milestones, not declared percentage of completion.
- What are we risking? The few major risks, their owner and the action under way.
- Do we have the means? Effort consumed and effort remaining, pressure on scarce skills.
- Is it still worthwhile? A reminder of the expected value and the assumptions on which it rests.
- What needs to be decided? The trade-offs requested of the committee, framed as choices.
The last line is the most important. A dashboard that asks for no decision is an activity report. When contractual commitments weigh on the project (penalties, payment milestones, obligations of result), we recommend including them in the risk register on the same footing as technical risks.
The mistakes we help you avoid
- Tooling before organising. A portfolio management tool deployed on unclear processes freezes the disorder and discourages teams.
- Asking the same of every project. A three-month project and a three-year programme do not justify the same level of formality. We propose a framework with several levels of requirement.
- Confusing PMO with control. A project office perceived as a police force only receives tidied-up information. It must provide a service to project managers in order to obtain honest data.
- Forgetting change. Setting up a PMO alters working habits and balances of power. We address this dimension with the methods of change management.
How to measure the success of a PMO
Success is not read in the number of reports produced. From the framing stage, we agree with you on a few observable signs: the share of projects whose status is known and up to date, the time between a problem appearing and the decision that deals with it, the share of committee decisions actually applied, and the perception of the project managers themselves. This last point is often neglected. A PMO that project managers call on spontaneously has already won the essential battle.
These indicators are tracked during the engagement and after we leave. They also serve to adjust the set-up: a PMO is a living structure, whose mandate evolves with the maturity of the organisation.