I am Hamidou, from Dakar, Senegal. I recently joined PMO Mastery because I find very few places where PMO professionals discuss the real political dimension of project work.

My question today is about stakeholder mapping. In the organisations I have worked in, in Senegal, Ivory Coast and also in France for some years, the formal org chart almost never tells you where the real power is. The person with the biggest title is sometimes not the one whose opinion actually determines whether your project gets support or not.

There is always an advisor, a trusted colleague, a long-serving director who is not even in the steering committee but who can make leadership change direction with one conversation. If you do not identify these people early, you can do everything right technically and still loose the support of key stakeholders without even understanding why.

How do you map this kind of informal influence? Are there any practical techniques beyond the standard power-interest grid? And how do you engage these informal influencers without making it feel manipulative or political?

I am very curious to hear different perspectives on this, especially from people who work in different cultural contexts.

I want to ask about something that feels very real to me right now. I work in an Italian manufacturing company and honestly our PMO has a bit of a reputation problem. The project managers call us 'the reporting department' behind our backs. And to be honest, I understand why. We spend most of our time chasing status updates and producing dashboards for leadership, while the actual project work happens around us.

I want to change this. I believe the PMO should be a genuine partner to the delivery teams, coaching PMs, removing blockers, connecting people who need to talk to each other. Not just collecting RAG statuses.

For those of you who have made this transition successfully: how did you do it? What was the first concrete step? And how did you get leadership to invest in the PMO differently when they are used to seeing you as a reporting function?

I am also curious: did you loose any team members who were not comfortable with a more active role? That is one of my worries actually.

Grazie for any thoughts!

My name is Ferhat, I am from Istanbul and I run a small PMO function in a mid-sized manufacturing company with about 1,400 employees. We have had the PMO for two years now and technically we are doing fine. Projects are more structured, reporting is consistent, escalations get to the right people.

But here is my problem: leadership is satisfied with us but they do not really engage with us. They receive our reports, they nod, they move on. We are seen as an administrative layer that keeps things tidy rather then a function that shapes decisions.

I have read a lot about how PMOs should become strategic partners, but most of that advice assumes leadership already wants that. What do you do when they are content with you being operational? How do you create appetite for something they are not asking for, without coming across as a department trying to expand its own territory?

I tried proposing a portfolio review session at the executive level last quarter and the response was polite but lukewarm. I think they liked the idea but did not see why they needed to sit in a room for it when they already get the dashboard.

Any experience with this? Would appreciate honest reflections, not just theory.

Ferhat

I am Svetlana, writing from Kyiv, Ukraine, where I work as a senior PMO analyst for a financial technology company. I have been in project management for nine years and I have one frustration that has followed me through every organisation I have worked in: lessons learned sessions that produce beautiful documents that nobody ever reads again.

We do the retrospective, we write the report, we put it in SharePoint, and then the next project team makes exactly the same mistakes six months later. It is almost funny if it was not so frustrating.

I am trying to build a system where lessons learned actually flow into the way we plan and execute new projects. Some ideas I am exploring:

• Mandatory lessons learned review as part of project kickoff, not just at closeout
• A searchable lessons library tagged by project type, phase and risk category
• A short monthly 'lessons digest' sent to all project managers

Has anyone actually made this work? I would love to hear real examples, not just theory. What made the difference in your organisation?

I want to start a discussion about something I rarely see talked about in PMO literature: the specific challenges of building and running a PMO in an African organisational context.

I am based in Lagos and I manage the PMO for a mid-size financial services group with subsidiaries in Nigeria, Ghana, Kenya and South Africa. Many of the frameworks we read about assume certain things like stable resourcing, mature governance structures, reliable digital infrastructure, that are simply not always the reality here.

Some specific challenges I face regularly:

• High staff turnover means institutional knowledge is constantly walking out the door
• Stakeholder engagement is very relationship-based; formal processes are often seen as obstacles rather than enablers
• Connectivity issues mean cloud-based PPM tools are sometimes not practical in certain locations

I would love to hear from others in similar contexts, or from those in other regions who have found ways to make frameworks more adaptable to local realities. What have you done to make your PMO fit the culture rather then the other way around?

This is something I struggle with constantly. We have around eighteen active projects right now and the same core group of subject matter experts are being pulled into almost all of them. The result is that these people are working at 130, sometimes 140 percent capacity while others on the bench are underutilized.

I have tried resource calendars, I have tried capacity planning spreadsheets, I have even tried a simple traffic light dashboard for each SME. But somehow the situation keeps repeating itself.

What has actually worked for you? I am especially curious about how you handle the politics of it - because often the problem is not the tool, it is that project managers go directly to the specialists and bypass the resource pool completely.

Any tips appreciated!

I am Kwabena, joining from Accra, Ghana. I have been managing a PMO that supports large government infrastructure programmes for about seven years now. Roads, water systems, public buildings. The scale is very different from corporate IT projects and I am curious whether others here have experience in this space.

Some things I notice are quite different in infrastructure PMOs:

• The funding is often donor-driven, witch means reporting requirements are extremely rigid and sometimes completely disconnected from actual project needs
• Political interference in project decisions is not the exception, it is the normal operating environment
• Projects can span multiple government administrations, so continuity of knowledge is a constant challenge

For those of you who have worked in public sector or infrastructure PMOs: what frameworks or adaptations have you found most useful? And how do you handle the tension between donor reporting requirements and actually delivering good projects?

Anyone navigating this successfully? I'm particularly interested in what you've had to let go of on the PMO side, and what you've insisted on keeping.

What metrics do you use to show PMO value? Particularly interested in anything that's resonated with a sceptical CFO or board.

I've done this once before but in a very different context. I'd love to hear from people who've built from zero: what did you do in the first 90 days, and what do you wish you'd done differently?