Look up PMO roles and responsibilities and you will find a tidy org chart. A head of PMO, a portfolio manager, a resource manager, a methods lead, a few analysts, each with a list of duties.
That structure works. A PMO staffed this way produces consistent plans, honest status reports and a governance process that stops money leaking into projects nobody approved.
Read the job descriptions side by side, though, and one decision is missing from all of them. Every PMO role is defined against individual projects. The decision that sets the speed of the whole portfolio is which project gets the constraint first. The constraint is the one team, skill or asset whose capacity limits how much the organization can finish, the group every project ends up queuing for. Map PMO roles and responsibilities against that decision and you find several people involved and nobody accountable for it. A decision with no owner still gets made. It just gets made by default.
What are PMO roles and responsibilities?
PMO roles and responsibilities are the defined jobs inside a project management office and the duties attached to each. Typically a head of PMO owns governance and the function itself, a portfolio manager owns the project list, a resource manager owns allocation, a methods lead owns standards and tools, and analysts own reporting. Together they make delivery consistent and visible.
In a typical mid-sized PMO, the list looks like this:
1. Head of PMO. Owns the PMO's mandate, chairs governance boards, handles escalations and reports to the executive team.
2. Portfolio manager. Maintains the list of approved projects, runs intake and scoring, and tracks the portfolio against budget.
3. Resource manager. Fields requests for people, resolves allocation conflicts and keeps a plan of who is assigned to what.
4. Methods lead. Sets the lifecycle, templates and estimating standards, administers the planning tools and trains project managers.
5. PMO analysts. Collect status from every project, build the RAG dashboard and prepare the packs for steering meetings.
6. Project managers. Often outside the PMO but governed by it, they plan and deliver their own project and request the people it needs.
Every one of those duties is worth doing. Look at the object of each one: a project, a request, a status report, a standard. None of them is the flow of work through the portfolio as a whole.
Who in the PMO is accountable for delay?
Run a simple test on your own PMO. Take one recurring decision, "which project gets our scarcest specialists next week?", and write down who is responsible and who is accountable for it.
Here is how that test went at Harbour, an illustrative organization with a PMO of 6 people and 24 active projects. Its 5 data engineers are needed by 14 of those projects, so they are the constraint.
The project managers request the engineers. The resource manager allocates them, one request at a time, mostly in the order the requests arrive. The portfolio manager ranked all 24 projects at intake, months ago. The head of PMO arbitrates when two sponsors escalate. Four roles touch the decision, and not one of them is accountable for the result. So the engineers end up spread roughly evenly across all 14 projects, which is what first-come allocation plus escalation produces.
Now put a number on it. Assume 2 of the 14 projects are each worth about $40,000 a month once live. Assume that if those 2 had been given the engineers first, rather than a fourteenth share each alongside 12 others, each would have gone live about 3 months sooner. On those assumptions, Harbour defers 2 × 3 × $40,000 = $240,000 of benefit. We call that drag cost: the value an organization loses while work waits. Change the assumptions and the figure moves. What stays the same is that the more projects share one constrained group, the more the order of work decides the result.
None of Harbour's 6 people did anything wrong. Each did their job as written. The $240,000 sits in the gap between the job descriptions.
Why does a well-staffed PMO still miss it?
Because every role is measured on projects, and portfolio performance is not the sum of project performance. We call the belief that it is the Project Illusion: the assumption that if every project is well planned, governed and delivered, the organization will perform well. In practice the result comes from how projects interact as they compete for the same scarce people.
A PMO's responsibilities follow its measures. The analysts report each project against its own baseline, and no baseline includes the 13 other projects waiting for the same engineers. The resource manager is judged on whether requests are filled, not on whether the right ones are filled first. The portfolio manager's ranking is a snapshot of value at intake, not a sequence for the engineers' next hour. Each measure is reasonable. Together they leave the constraint's queue outside everyone's scorecard.
That is a property of how the roles are drawn, not a failing of the people in them. It also explains why adding headcount to the PMO rarely changes delivery speed. A seventh person built to the same template adds capacity to the jobs that were already covered.
How should PMO roles and responsibilities change?
None of the existing roles needs to go. Each needs one responsibility added, and one role needs to own the outcome.
1. Head of PMO: accountable for flow through the constraint. Name the constraint, and make the head of PMO accountable for how many projects reach it and how long they wait. This is the single "A" the Harbour test was missing. How to Find the One Resource That Sets Your Delivery Speed sets out how to identify it.
2. Portfolio manager: sequence, do not just rank. Turn the intake ranking into an order of work for the constraint, ranked by value returned per hour of the constraint's time. That is the logic of value per constrained resource hour.
3. Resource manager: protect the sequence. Allocate the constraint in the agreed order rather than the order requests arrive, and bring any exception to the head of PMO as a priced choice.
4. Methods lead: build the gate. Add a start criterion so a project cannot begin until there is room for it at the constraint. The case for that discipline is in Start Less to Finish More.
5. PMO analysts: report the queue in money. Add two lines to the dashboard: how many projects are waiting at the constraint, and what that wait costs per month in drag cost.
Who owns prioritization in a PMO?
The objection you are already forming: our portfolio manager owns priorities. That is literally in the job description.
In most PMOs it is, and it covers the question of what enters the portfolio. Once 14 projects are live and all need the same engineers, a different question is settled every week: which of them gets the next hour. If the ranked list does not govern that queue, the queue is governed by whoever asks first or shouts loudest, and the list is a statement of intent rather than a sequence. Owning priorities without owning the constraint's queue is owning half the decision.
Nor does accountability mean the head of PMO overrules sponsors. It means someone prices each ordering, puts the cost of delay in front of the people with authority, and makes sure the choice is made on purpose.
That shift, from running projects consistently to deciding which work creates the most value, is the point where a PMO starts to work as a Value Management Office. It is the same people with one decision added to their job descriptions, the one that was never written down.
Leave a Reply