Embedding a PMO (Project Management Office) is one of the most important steps an organisation can take to improve how it delivers change. But as many project professionals know, it’s rarely easy.

From low maturity and unclear purpose to cultural resistance and lack of capability, the road to an effective PMO is often bumpy. During a recent Wellingtone community event, we explored real-world lessons and strategies that help overcome these issues. The session featured PMO leaders from different sectors—including guest speaker Jim Hartley from NHS Lincolnshire who shared what’s worked, what hasn’t, and what others can learn.

This blog post summarises those insights into practical steps you can apply, whether you’re setting up a PMO from scratch or trying to embed one that delivers more value.

Why is embedding a PMO so difficult?

Embedding a PMO is hard because it requires more than process change, it needs mindset change across the organisation. Based on feedback from the community and our annual research, here are the most common barriers:

Lack of clarity about the PMO’s role and value
Resistance to governance or standardisation
Fragmented project delivery capability
Multiple, competing priorities
Low stakeholder engagement

In fact, 46% of project professionals say they’re dissatisfied with the current level of project management maturity in their organisation. Without clarity, direction and support, PMOs often become misunderstood or underused. – The State of Project Management 2025

Where should you start when embedding a PMO?

The best place to start is with your people. Before you implement a framework, template, or tool, spend time understanding:

The culture of your organisation
The expectations of key stakeholders
What problems the PMO is being asked to solve

At our community event, PMO leader Jim Hartley shared that he spent over 100 hours in one-to-one meetings before launching any initiatives. This helped build trust and uncover the real issues blocking success. It also shaped a PMO strategy that was grounded in real needs

Do you need a PMO roadmap to be successful?

Yes, a PMO roadmap is essential. Without it, you risk getting pulled in every direction, trying to do everything for everyone.

A good roadmap does three things:

Sets a clear direction for the PMO
Defines short, medium and long-term priorities
Provides a reference point for communicating value

In our event poll, attendees said that without a roadmap, it’s hard to articulate what the PMO does, demonstrate progress, and avoid getting lost in organisational “noise”.

The roadmap doesn’t have to be overly detailed or fixed for years. It should be a flexible plan that evolves as your PMO and business needs grow.

How do you build capability before enforcing process?

Trying to enforce frameworks before building capability is one of the main reasons PMOs fail.

Instead, focus first on training and education. This could be through:

Community learning and sharing events
Formal project management qualifications
A project management academy
Peer learning and mentoring

In one case shared at the event, an internal PMO developed short, context-specific courses to help project managers and senior responsible officers build confidence. This reduced resistance and made it easier to introduce consistent practices later on.

How much standardisation is enough for a PMO?

The goal of standardisation is to enable, not hinder project success.

Instead of enforcing one-size-fits-all templates, consider:

Creating light-touch governance and scalable tools
Aligning documentation across business units without dictating
Standardising reporting requirements while allowing delivery flexibility

Start by asking: “Why are we doing this?” If you can’t answer that clearly, the process may need rethinking.

In large organisations, especially those with multiple PMOs, alignment is more important than uniformity. Work with teams to co-design solutions that meet both local and organisational needs.

What does a value-driven PMO look like?

A value-driven PMO is clear about what it offers, how it helps the business, and how success is measured. One of the most effective tools for achieving this is a PMO service catalogue.

Your service catalogue should explain:

What services the PMO offers (e.g. reporting, training, prioritisation)
Who the services are for
What benefits they provide
How to access them

This transforms the PMO into a service provider, helping internal teams choose what they need, when they need it. It also makes it easier to communicate value and manage expectations.

How should a PMO measure its success?

Start simple. You don’t need perfect baseline data to start tracking value.

Here are a few performance indicators that PMOs can use early on:

% of projects using standard templates
Number of people trained through PMO initiatives
Feedback from project teams and sponsors
Quality and timeliness of reporting
Number of active projects with clear business cases
Usability of the PMO services

As maturity increases, your metrics can evolve to include benefits realisation, strategic alignment, and portfolio balance. But early indicators still matter as they build momentum and prove the PMO is moving in the right direction.

What can you do next to embed your PMO successfully?

Here’s a summary of practical next steps that came out of our community session:

Talk to your stakeholders before building your strategy
Create a roadmap – even if it’s just for 12–18 months
Focus first on capability and confidence building
Keep governance light-touch and aligned to real needs
Develop and share a service catalogue to show value
Track what you can, and build your metrics over time
Communicate often, and never assume people “get” the PMO

Remember: embedding a PMO is not a quick fix. It’s a continuous journey of learning, improvement and alignment.

Final thoughts: why PMOs must think like service providers

The PMO of the future isn’t just about process or tools—it’s about people, service, and strategy. The most successful PMOs are those that think of themselves as service providers, supporting their internal customers with what they need to succeed.

Whether you’re starting from scratch, rebooting your function, or refining your approach, keep this front of mind: the more clearly you can explain what your PMO does, the easier it becomes for people to use and value it.