Oluwaseun, you mentioned high staff turnover as a specific challenge. How do you handle knowledge continuity in practice? That seems like the one where the standard PMO toolkit genuinely struggles.

Also worth checking: is there someone they do trust who is already inside the project? The route to an informal influencer is sometimes through a third party rather than direct engagement. Trying to engage directly when someone is resistant can harden the position rather than open it.

The only thing I have seen add to this even slightly: PMO-facilitated handoffs where a project lead spends an hour with the incoming lead before they start. Not a formal debrief, just a conversation. It does not capture everything, but it captures the things the person thought were actually worth remembering. The written report would have had forty items. The conversation has three.

Still does not solve the incentive problem Svetlana raised. Nobody is rewarded for making the next project's life easier.

The donor-driven reporting point resonates with something I have noticed across several different contexts: there is often a gap between what the funder wants to measure and what the project actually needs to manage. The indicators that satisfy a reporting framework are not always the ones that would help you anticipate a problem early. Has anyone found a way to run both systems without one of them becoming purely performative?

That said, there is a version of what you describe where the problem is different: the PMO is producing information nobody specifically asked for, delivered in a format that fits the PMO's logic rather than the decision-maker's. Monthly portfolio reports are a classic example. Useful as an archive, not useful at the moment of a decision.

One thing worth trying: find out what decisions leadership will make in the next 90 days and ask yourself whether your current reporting directly informs any of them. If the answer is no, that is probably where to start.

In the organisations I have worked in, in West Africa and in France, the PMO's most important value is often not visible in any dashboard. It is the conversations you have, the trust you build with senior leaders, the early warning you provide before a problem becomes a crisis.

Of course this is very difficult to measure. But I think it is worth trying. In my current organisation we track something we call 'early escalations': situations where the PMO identified and raised a risk before it became an issue. We count these and estimate the cost that was avoided. It is not perfect but it gives leadership a sense of the value we provide beyond the standard reporting metrics. And it changes the conversation from 'what does the PMO do' to 'what would have happened without it.'

I work in Greece for a construction and infrastructure group and what you describe about political interference is very familiar. In our context it is sometimes the regional government, sometimes a ministry, sometimes a large contractor with political connections. The PMO has to navigate all of this while still keeping the project technically on track.

One thing that has helped us: we maintain two parallel views of every project. The 'official view' for the donors and politicians, and the 'real view' for the delivery team. The official view is always positive in tone. The real view is where we track actual risks, actual delays, and actual resource problems. This sounds dishonest but it is really about audience. The delivery team needs accurate information to make good decisions. The political stakeholders need confidence that the programme is under control. Conflating those two audiences in one report usually serves neither well.

Is this a pattern you recognise from your Ghana context?

The first type is what I call 'outcome governance': are we building the right things, are we allocating budget to the right priorities, are risks visible at portfolio level? This is genuinely valuable and agile teams do not object to it.

The second type is 'process governance': did you fill in the status report, did you follow the template, did you attend the steering committee? This is the type that agile teams experience as the 'process police' problem. And honestly, when I look at it objectively, they are often right to resist it. When we stopped enforcing process governance rigidly and focused almost entirely on outcome governance, the bypass problem largely disappeared. The teams were not trying to avoid accountability. They were trying to avoid bureaucracy.

My name is Rajan Pillai and I am writing from Bangalore, India. I am working now six years in project management, and for the last two years I am specifically focusing on PMO setup and governance at a mid-size IT services company.

We are still what I would call a "young PMO"; we have the structure on paper but making it actually work in practice is where the real challenge is. Many times the project managers see us as the people who send reminders and ask for status reports, not as a partner. I am sure some of you know this feeling very well!

My main interests are portfolio prioritisation and how to demonstrate PMO value to senior leadership. I attended few webinars on this topic but still feeling I am learning by trial and error more than anything systematic.

I found PMO Mastery through a LinkedIn post and I thought, finally a community for people exactly like me. Looking forward to learn from all of you and also to share what I have figured out so far from our own experience.

Happy to connect with anyone who is also working on PMO maturity in a fast-growing tech environment.

Regards,
Rajan