Programme management office, built to be handed over

PMO Consultancy We build it, then we leave.

A programme management office is the control function that tells a board whether a portfolio of change is actually going to land. Intology designs, mobilises and runs PMOs for UK organisations, then transfers them to your own people. We are not a resourcing firm and we do not want to still be sitting in your PMO in three years.

Most PMOs fail in one of two directions. They collect status reports nobody acts on, in which case they are an expensive administrative burden. Or they enforce process so rigidly that delivery teams route around them, in which case the reporting is fiction. A PMO earns its place only when it changes what the leadership team decides.

Designed for handover Senior practitioners only No permanent PMO headcount

What a programme management office is

A programme management office, usually shortened to PMO, is the function that plans, tracks, governs and reports a programme of change on behalf of the people accountable for it. It holds the plan, the risks, the dependencies, the finances and the decision record, and it gives the sponsor and the board a single reliable view of where delivery stands.

The word covers three different things, and confusing them is the most common reason a PMO gets stood up with the wrong mandate.

Project Management Office

Supports a single project. Concerned with the plan, the risk log, the actions, the budget and the reporting for one piece of work. Usually temporary, and closed when the project closes.

Programme Management Office

Supports a programme, meaning a group of related projects delivering one outcome. Concerned with dependencies between projects, benefits, resource contention and the sequencing decisions that no individual project manager can make alone.

Portfolio Management Office

Supports the whole change portfolio across an organisation. Concerned with prioritisation, capacity, investment allocation and whether the portfolio as a whole still matches the strategy. Permanent, and usually reporting to the executive.

Most organisations asking for a PMO need the second of these. Some think they need the second and actually need the third, because the real problem is that the organisation is running more change than it has the capacity to absorb. Establishing which one you need is the first hour of the conversation, not an afterthought.

What a PMO does

The functions vary with mandate, but a PMO that is earning its keep is doing most of the following:

  • Planning and schedule management, including the integrated plan across projects
  • Risk, issue, assumption and dependency management, actively worked rather than logged
  • Financial control: forecast, actuals, variance and the reforecast cycle
  • Resource management and capacity planning across the portfolio
  • Governance: board and steering committee papers, decision records, stage gates
  • Reporting: a single, honest, current view of delivery status
  • Benefits definition and tracking through to realisation
  • Standards, templates, tooling and assurance of delivery quality

A PMO that only does the last two is an administration function. A PMO that does the first six is a control function, and that is the difference between a cost and an asset.

PMO roles and responsibilities

A PMO is a small number of clearly defined roles. Padding it with people who have no decision rights is how PMOs get a reputation as overhead.

PMO Director or Head of PMO

Owns the mandate. Sets what the PMO is for, holds the relationship with the sponsor and the board, and has the standing to tell an executive that a date is not achievable. Without this authority the PMO is a reporting desk.

PMO Manager or Lead

Runs the function day to day. Owns the governance cycle, the reporting calendar, the quality of what reaches the board, and the working relationship with delivery leads.

Planning and controls analyst

Owns the integrated plan, the dependency map, the risk and issue process and the financial tracking. This is the role that spots the problem six weeks before it lands.

Reporting and MI analyst

Owns the data, the toolset and the production of reporting. Increasingly this role automates what used to be manual collation, which is where most of the efficiency in a modern PMO comes from.

On a mid-sized transformation those four roles are typically two to four people, not a department. If the proposed PMO is larger than that, ask what each additional person is deciding.

When a PMO is the right answer

The trigger is usually one of these:

  • The organisation is running several related projects and nobody can say what the combined position is
  • The board receives status reports it does not believe
  • A programme has slipped twice and the reasons given are different each time
  • An acquisition, carve-out or restructure has created more change than the existing governance can carry
  • A private equity sponsor wants portfolio-level visibility across a hold period
  • An internal PMO exists but is producing administration rather than decisions

If two or more of those are true, the question is not whether to have a PMO. It is what mandate to give it and who it reports to.

How Intology sets up a PMO

A PMO can be designed and mobilised in six to ten weeks. Handover to your team follows, and the timing of that is agreed at the start rather than negotiated at the end.

Stage 1

Mandate and scope

We establish what the PMO is accountable for, who it reports to and what decisions it is expected to change. This is written down and signed off, because an undefined mandate is the root cause of most PMO failure.

Stage 2

Current state and portfolio baseline

We map what is actually running, what it is costing, who is working on it and what depends on what. On most first engagements this exercise finds projects the executive did not know were live.

Stage 3

Operating model and governance design

We design the meeting cycle, the decision rights, the stage gates, the escalation routes and the reporting calendar. Governance is designed around the decisions that need making, not copied from a framework.

Stage 4

Controls, tooling and reporting

Planning, risk, dependency, financial and benefits controls are built, along with the reporting that sits on top of them. We use the tooling you already own wherever it will do the job.

Stage 5

Mobilisation and running the cycle

Intology runs the PMO through the first governance cycles, alongside your people rather than instead of them, so the process is proven under real conditions before anyone signs it off.

Stage 6

Capability transfer and handover

Your team takes the function. We pair, we document, we step back progressively, and we agree the point at which we are done. The measure of success is that the PMO still works six months after we leave.

PMO as a service, and interim PMO leadership

Not every organisation needs to build a permanent function. Where the change is time-bound, a PMO as a service arrangement gives you the controls, the governance cycle and the reporting for the life of the programme, run by Intology, and closed down cleanly when the programme closes.

Where the function exists but the leadership does not, we provide interim PMO leadership: a senior practitioner running your PMO through a difficult period, a leadership gap or a recovery, while your permanent successor is recruited and brought up to speed.

Both are priced and scoped to a defined end point. We will tell you which of the three shapes fits, and if the honest answer is that you need a permanent hire rather than a consultancy, we will say so.

Where the PMO ends and independent assurance begins

A PMO and a programme assurance function are not the same thing, and an organisation that treats them as interchangeable ends up with neither.

The PMO is inside the delivery line. It plans the work, tracks it, reports it and escalates. Its reporting is the programme's own account of itself, which is exactly what it should be, and it is also why the PMO cannot mark its own homework.

Assurance sits outside the delivery line. It tests whether the plan is credible, whether the risks are the real risks and whether the reported status would survive scrutiny. Intology keeps the two structurally separate: we do not assure a PMO we are running, and we do not run a PMO we are assuring.

Where you need the independent view rather than the control function, that is programme assurance. Where a programme has already gone wrong, it is usually programme recovery.

What you receive

Every engagement leaves a documented, operating function rather than a set of recommendations.

  • A written PMO mandate agreed with the sponsor and the board
  • A baselined portfolio: what is running, what it costs, who is on it and what it depends on
  • An integrated plan with the cross-project dependency map
  • A governance model: meeting cycle, decision rights, stage gates and escalation routes
  • Risk, issue, assumption and dependency processes that are worked rather than logged
  • A financial control and reforecast cycle
  • A benefits framework tracked through to realisation
  • A reporting pack the board will actually read, built on your existing tooling
  • A capability transfer plan with a named handover date

Who we work with

Intology works with FTSE-listed companies, PE-backed businesses, mid-market organisations and UK public sector bodies, typically £25m to £2bn revenue or equivalent public sector budget. Over fifteen years we have delivered more than one hundred programmes for over fifty clients.

Engagements are staffed with senior practitioners only. The person designing your governance model has sat on the other side of it as a programme sponsor, and the people in your steering committee are the people doing the work.

Frequently asked questions

The questions UK sponsors and transformation directors most often ask before commissioning PMO support.

What is a programme management office?+
A programme management office, or PMO, is the function that plans, tracks, governs and reports a programme of change on behalf of the people accountable for it. It holds the plan, the risks, the dependencies, the finances and the decision record, and gives the sponsor and the board a single reliable view of delivery status.
What is the difference between a project, programme and portfolio management office?+
A project management office supports one project and usually closes with it. A programme management office supports a group of related projects delivering one outcome, and handles the dependencies and sequencing decisions no single project manager can make. A portfolio management office supports the whole change portfolio across an organisation, and is concerned with prioritisation, capacity and investment allocation.
What are the main functions of a PMO?+
Planning and schedule management, risk and dependency management, financial control, resource and capacity planning, governance and stage gates, delivery reporting, benefits tracking, and delivery standards and assurance. A PMO doing only reporting and standards is an administration function rather than a control function.
What roles sit in a PMO?+
Typically a PMO Director or Head of PMO who owns the mandate, a PMO Manager who runs the function day to day, a planning and controls analyst who owns the integrated plan and financial tracking, and a reporting analyst who owns the data and the reporting production. On a mid-sized transformation that is usually two to four people rather than a department.
How long does it take to set up a PMO?+
A PMO can be designed and mobilised in six to ten weeks, depending on portfolio size and how much of the current state is already documented. Handover to the client team follows, with the timing agreed at the start of the engagement.
Do you leave people in our PMO permanently?+
No. Intology is not a resourcing firm. Every engagement is designed for capability transfer, with a named handover date agreed at the outset. Where a permanent hire is the right answer rather than a consultancy, we say so.
We already have a PMO but the board does not trust its reporting. Can you help?+
Yes, and it is a common request. We review the mandate, the controls and the reporting chain, and establish whether the problem is the data, the process, the mandate or the authority of the people in the roles. It is most often the mandate.
What is the difference between a PMO and programme assurance?+
The PMO sits inside the delivery line and produces the programme's own account of itself. Assurance sits outside it and tests whether that account would survive scrutiny. Intology keeps the two structurally separate: we do not assure a PMO we are running, and we do not run a PMO we are assuring.
How is PMO consultancy priced?+
Design and mobilisation is scoped and fixed-priced against portfolio size and complexity. PMO as a service and interim PMO leadership are priced to a defined end point, agreed before the engagement starts.

Running more change than you can see?

Tell us what is in flight and who is accountable for it. We will tell you honestly whether you need a PMO, a better governance cycle around the one you have, or an independent look at why the reporting is not trusted. The initial conversation is free and carries no obligation.