We’re working with a number of organisations at the moment to support the set-up of a Project Management Office (PMO). As most people acknowledge, no two PMOs are the same. While there are common themes across frameworks, methodologies and service areas, what works in practice depends on the organisation’s context, maturity and priorities.

Practical pointers for setting up a PMO

Given the range of what organisations expect from a PMO, we thought it would be useful to capture a few practical pointers that apply regardless of the type of PMO you’re setting up. These are also helpful if you want to take stock of an existing PMO or run a reset. They are intended as universal principles to help you establish and maintain a value-adding PMO

1. Start with the why

Before you talk structure, talk purpose. What problem is the PMO there to solve? Too many priorities? Patchy delivery? No visibility? Poor benefits realisation?
If you cannot clearly articulate the ‘why’ in two sentences, you will struggle to make good decisions about services, governance and resourcing.

A useful framing is:

2. Be explicit about who the PMO serves and what ‘value’ means

A PMO serves someone. Sometimes it is the executive and board. Sometimes it is delivery teams. Often it is both, but in different ways. Spell it out, because ‘value’ is different depending on the customer:

If you do not name the customer, the PMO becomes a catch-all and may be judged on conflicting expectations. The old saying ‘you can’t please all of the people all of the time’ is true, but you can try if you know who they are and what they want.

3. Define a small number of services you can deliver well

Most PMOs fail by trying to do everything at once. Start with a minimum viable service catalogue and build maturity in phases.

A practical starting point is typically:

Once those building blocks are in place you can scale into true portfolio services with confidence:

Build credibility before expanding services. When project-level information is clean and consistent, portfolio reporting start to enabling real strategic insights which can then inform decision making at the highest level.

This won’t happen overnight. Manage expectations about maturity.

4. Put governance in plain English and make it easy to follow

Governance should reduce friction, not create it. If it feels like a compliance trap, people will work around it.

Keep it practical:

Good governance is not more meetings. It is fewer meetings, with fewer participants and better, faster decisions.

5. Design reporting that supports decisions, not just status updates

A good report does not just record activity. It tells you what has changed, what it means and what you need to do about it.

It should make it clear:

Done well, status reporting becomes the backbone of your governance rhythm, keeping decisions moving and conversations focused.

6. Agree measures of success up front and revisit them regularly

PMOs get challenged when success is vague. Define success in terms leaders care about and be realistic about maturity stages.

Early measures might include:

Later measures might include:

Importantly, these measures should not be static. Ideally they should be reviewed quarterly. A PMO should evolve with the organisation.

7. Set the PMO up as a capability builder, not just compliance

If the PMO only checks artefacts, it becomes known as a ‘policing’ function, becomes resented and often bypassed. If it builds capability, typically its more likely to become valued.

Capability-building behaviours include:

Over time, this uplift of personal capability transfers into organisational maturity uplift.

8. Tools: choose a toolset that supports the operating rhythm, not a shiny platform

The technology matters, but it should not be the starting point (unless you have no choice, sometimes a tool is the mandated starting point). Tools should ideally reinforce the PMO’s service model and governance rhythm.

A pragmatic approach would be to define:

Then select or configure tools to match.

You typically need four layers:

  1. Work management (delivery execution)
    Where teams plan work and track progress. Key requirement: it must be used consistently, not just by a few teams.
  2. Portfolio view (PMO oversight and prioritisation)
    Where you see the portfolio in one place: status, spend, capacity, dependencies, risks, decisions.
    Sometimes this is a dedicated portfolio tool, sometimes it is a well-designed Power BI view over work management and finance systems.
  3. Document and artefact management
    A consistent place for business cases, charters, plans, RAID logs, stage gate packs. SharePoint and Teams usually do this well if designed properly.
  4. Reporting and dashboards
    May come from a dedicated PPM tool, could be from a dedicated Business Intelligence (BI) layer or could be pulled together manually from different systems.

Implementation principles that should keep you out of trouble

Before buying anything new:

Ask:

Ultimately, a good PMO is not defined by how comprehensive its framework is or how complex its tools are. It is defined by whether it improves decisions, increases confidence in delivery and lifts capability across the organisation. Start small, be clear on purpose, and build maturity in deliberate phases. If you get the fundamentals right the PMO can evolve over time without losing trust or momentumTop of Form

Get in touch

Explore how our pragmatic solutions can help you to deliver more effectively, every time.

CONTACT US