A Project Management Office rarely runs on one job title. Even in a small PMO, distinct responsibilities, governance, portfolio oversight, delivery, tend to fall to different people, whether or not the org chart says so explicitly. Understanding where each role starts and ends is what stops a PMO from either duplicating work or leaving a gap nobody owns.
This guide walks through the five core roles most PMOs need, what each one is responsible for, and how the structure tends to shift as an organisation grows.
1. Head of PMO / PMO Director
Owns: The PMO function as a whole, its governance standards, its mandate, and its relationship with executive leadership.
The Head of PMO sets the operating model the rest of the function follows: whether the PMO is supportive, controlling, or directive, what governance every project must pass through, and how the function reports its value to the board. In smaller organisations, this role and the PMO Manager role below are often the same person. As a PMO matures, they tend to split, with the Head of PMO focused on strategy and executive relationships, and the PMO Manager running day-to-day operations.
Reports to: C-suite sponsor (CEO or COO), or an Operational Director.
What they say to themselves. "My job isn't running projects well. It's proving this function is worth its seat at the table."
2. PMO Manager
Owns: Day-to-day portfolio oversight, the governance process, and preparing the strategic view for leadership.
This is usually the busiest role in the function. The PMO Manager maintains the project list, runs the ideas pipeline and gate process, chases status updates, and is the person who can list every active project in the organisation from memory. The harder part of the job is being able to show which of those projects are still linked to a strategic objective, without a week of manual spreadsheet work every time someone asks.
Reports to: Head of PMO, or directly to an Operational Director in smaller structures.
What they say to themselves. "I can see every project. I cannot always tell you if any of them still matter."
3. Portfolio Manager
Owns: One or more portfolios, specifically the grouping of programmes and projects against a shared strategic outcome, and the budget and progress tracking at that level.
Where a PMO Manager often holds responsibility across the whole organisation's portfolio structure, a Portfolio Manager is typically focused on a specific portfolio, for example a Customer Digital portfolio or a Financial Restructure portfolio, tracking whether the programmes and projects inside it are collectively still delivering the outcome that portfolio exists for.
Reports to: PMO Manager or Head of PMO.
What they say to themselves. "Every project in my portfolio might be green. I still need to know if the portfolio is winning."
4. Programme Manager
Owns: A group of related projects, tracked together because they contribute to a shared outcome that no single project could deliver alone.
A Programme Manager sits between portfolio and project. Their job is coordination: managing dependencies between projects inside the programme, resolving conflicts over shared resource, and reporting progress up to the portfolio level. Where a Portfolio Manager asks whether a strategic outcome is being achieved, a Programme Manager asks whether the specific set of projects assigned to deliver it are actually working together to do so.
Reports to: Portfolio Manager, or directly to the PMO Manager in flatter structures.
What they say to themselves. "Each of my projects is on track individually. Are they actually adding up to the outcome we grouped them for?"
5. Project Manager
Owns: An individual project's delivery against its schedule, budget, and scope.
The Project Manager is the role most people picture when they hear "project management," and for good reason, it is the layer closest to the actual work. Their job is to deliver a defined piece of work within the governance standards the PMO has set, escalating risk and status up through the programme or portfolio level as needed.
Reports to: Programme Manager, or directly to a Portfolio Manager or the PMO Manager on projects run outside a formal programme.
What they say to themselves. "I hit every milestone on this project. Whether it should have been funded is someone else's question, not mine, and that's fine, as long as someone is actually asking it."
How these roles fit together
| Role | Scope | Core question | Typically reports to |
|---|---|---|---|
| Head of PMO | The whole PMO function | Is this function proving its strategic value? | C-suite sponsor |
| PMO Manager | The organisation's full project and portfolio list | Is our governance working, and is the portfolio aligned? | Head of PMO |
| Portfolio Manager | One or more portfolios | Is this strategic outcome being achieved? | PMO Manager |
| Programme Manager | A group of related projects | Are these projects delivering the shared outcome together? | Portfolio Manager |
| Project Manager | A single project | Is this piece of work on time, on budget, on scope? | Programme Manager |
Read from top to bottom, the questions move from strategic to operational. Read from bottom to top, each role's answer feeds the one above it: a Project Manager's status rolls into a Programme Manager's coordination view, which rolls into a Portfolio Manager's strategic assessment, which rolls into the PMO Manager's organisation-wide governance report, which the Head of PMO uses to answer to the board.
How PMO structure changes as an organisation grows
Small PMO (fewer than 50 employees, few concurrent projects). One person, often called a PMO Manager or Project Manager, typically covers governance, portfolio oversight, and delivery together. A formal programme layer is rarely needed yet.
Growing PMO (50 to 500 employees, moving past owner-led decision making). This is where the roles above start to separate. A dedicated PMO Manager takes over governance and reporting, Portfolio and Programme Manager roles emerge as the number of concurrent initiatives grows past what one person can track by hand, and Project Managers are hired or designated per initiative.
Mature PMO (large or complex portfolios). A Head of PMO role separates from day-to-day PMO Manager duties, multiple Portfolio Managers each own a specific strategic area, and Programme Managers coordinate dedicated teams of Project Managers.
Most UK mid-market organisations sit in the middle category, which is exactly where role clarity starts to matter most, since this is the stage where informal ownership (whoever happens to be tracking a spreadsheet) needs to become a defined structure before growth outpaces it.
How software supports these roles without duplicating effort
A common failure mode as these roles separate is that each one ends up maintaining a slightly different version of the same information: a Project Manager's status update, re-entered by a Programme Manager into their own tracker, re-entered again by a Portfolio Manager into a portfolio deck, re-entered a third time by the PMO Manager into a board report.
Software that structures Objectives, Portfolios, Programmes, and Projects as a connected hierarchy avoids this. A Project Manager updates status once, at project level. That status rolls up automatically into the programme view a Programme Manager uses, the portfolio view a Portfolio Manager uses, and the organisation-wide dashboard a PMO Manager and Head of PMO use for executive reporting, without anyone re-entering the same data at a different altitude.
Project Director is structured to support exactly this handoff: a Business Unit sits above Portfolios, which sit above Programmes, which sit above Projects, with each level inheriting the strategic context of the one above it, so every role in the PMO is working from the same underlying data, viewed at the altitude relevant to their job.
Frequently asked questions
Can one person hold more than one PMO role? Yes, and it is common in smaller organisations. A single PMO Manager often covers portfolio, programme, and governance responsibilities together until the volume of concurrent projects makes that unsustainable, at which point the roles typically separate.
What is the difference between a PMO Manager and a Portfolio Manager? A PMO Manager usually holds broader responsibility across governance and the organisation's full portfolio structure. A Portfolio Manager is typically focused on one or more specific portfolios, managing the programmes and projects within them against a defined strategic outcome.
Do all PMOs need a Head of PMO role? Not necessarily. Smaller PMOs often combine this responsibility into the PMO Manager role. A dedicated Head of PMO tends to emerge once the function is large enough, or strategically important enough, to need a role focused specifically on executive relationships and the PMO's mandate.
Who is accountable if a portfolio drifts from strategy? Ultimate accountability usually sits with the Head of PMO or the C-suite sponsor, since they hold the executive relationship the portfolio is meant to serve. Day-to-day responsibility for spotting and flagging that drift typically sits with the Portfolio Manager or PMO Manager closest to the data.
The practical takeaway
Five roles, one connected structure: strategic accountability at the top, individual delivery at the bottom, and a PMO Manager, Portfolio Manager, and Programme Manager forming the connective layer in between. Getting the boundaries between these roles clear, and giving each one visibility into the level above and below without re-entering the same status three times, is what turns a PMO from a group of job titles into a function that can actually answer for its portfolio.
See whether your portfolio still matches your strategy. Take the 14-day evaluation.
