Most organisations moving to a product operating model already employ the person best placed to become their Portfolio Product Manager: the PMO Lead. The PMO Lead already sees across every investment, runs the reporting cadence, and assembles the evidence senior executives read before they decide. What changes is the question that evidence answers. A PMO asks whether each project is executing to plan. A Portfolio Product Manager asks whether the organisation’s collective investment is producing outcomes at a rate that justifies its current allocation (Hodgson, 2026, Ch. 7).
In Brief
- The PMO Lead is the Portfolio Product Manager's closest predecessor, not its opposite. Both synthesise evidence for executives who make the decisions.
- Neither role allocates investment. In a product operating model, that decision belongs to the Product Portfolio Executive, within an envelope the Board sets.
- The PMO should be retired as a structure and its functions distributed across the portfolio's three accountabilities. Renaming the PMO produces the same steering pack under a new letterhead.
The PMO already performs half the portfolio function
PMOs vary widely in what they do. Hobbs and Aubry’s research identified 27 distinct PMO functions and grouped them into eight categories, including reporting project status to upper management and monitoring and controlling project performance (Hobbs & Aubry, 2007). The same research places coordination between projects, identifying, selecting and prioritising new projects, allocating resources between projects, and benefits management within the PMO’s remit.
In most agencies, then, the PMO is already the organisation’s portfolio view and the secretariat to its investment decisions. The PMO is also used to change. In a study of 11 organisational transformations centred on implementing or reconfiguring PMOs, the authors found that organisations reconfigure their PMOs every few years (Hobbs et al., 2008). Moving to a product operating model is one more reconfiguration, but it runs on a different design principle.
The PMO’s limitation lies in its governing question, not its people. A steering committee pack that reports accurately against the approved plan cannot tell a Deputy Secretary or CIO whether the investment is producing results. The governance machinery works exactly as designed, and the design cannot answer the question that matters (Hodgson, 2026, Ch. 7). Project reporting measures whether work is executing as planned. Portfolio governance measures whether investment is generating value, for whom, and why.
The Portfolio Product Manager holds value direction, not investment authority
In a product operating model, the portfolio tier carries four accountabilities (Hodgson, 2026, Ch. 5):
- Strategic investment sits with the Product Portfolio Executive.
- Value direction sits with the Portfolio Product Manager.
- Operating model effectiveness sits with the Portfolio Product COO.
- Technical integrity sits with the Enterprise Architect.
None of the last three allocates investment. They exist so that the executive who does allocate it can decide on evidence rather than advocacy.
The Product Portfolio Executive makes three decisions:
- Designing the guardrails that define what product lines and Product Managers may decide without escalation.
- Reallocating investment at the quarterly portfolio review.
- Withdrawing funding from products that no longer return value at the rate their investment justifies.
The Board sets the envelope within which the Product Portfolio Executive exercises those decisions. That envelope comprises the investment ceiling, the risk appetite and the strategic boundaries. The Board is drawn back in only when one of four triggers occurs: an investment crosses a defined cost threshold; a change materially alters the organisation’s risk profile; a defined risk threshold is approached or breached; or a product crosses a lifecycle stage boundary (Hodgson, 2026, Ch. 7).
The Portfolio Product Manager enables all three executive decisions. Through monthly synchronisation with Product Managers, the role synthesises the portfolio’s evidence into the quarterly review package. That package covers each product’s Evidence-Based Management (EBM) Key Value Areas, its lifecycle position, its current investment quantum, and the Cost of Delay score for its highest-priority uninitiated work (Hodgson, 2026, Ch. 7; Reinertsen, 2009; Scrum.org, 2024). The executive does not construct this information. The executive reads it, interrogates it, and decides from it.
The boundary matters because crossing it is how the model fails. When a Portfolio Product Manager starts making allocation decisions, governance accountability has been confused with decision authority. Portfolio governance then reverts to the committee model it was designed to replace (Hodgson, 2026, Ch. 7). A PMO Lead understands this boundary better than most, because the PMO has always prepared decisions that others make.
The two roles compared
Set side by side, the two roles share an audience and a reporting rhythm but answer different questions, draw on different evidence, and succeed by different tests.
| Dimension | PMO Lead | Portfolio Product Manager |
|---|---|---|
| Unit of governance | The project: temporary, separately scoped and funded | The product: persistent, funded according to its lifecycle stage |
| Governing question | Is each project on schedule, within budget and within scope? | Does the evidence justify each product’s current allocation, compared with the alternatives competing for the same capacity? |
| Evidence | Red-amber-green (RAG) status, milestone summary, issues register, benefits register | EBM Key Value Areas, lifecycle position, investment quantum, Cost of Delay |
| Cadence | Aligned to steering committees and stage gates | Monthly synchronisation with Product Managers; quarterly portfolio review fed by fortnightly Sprint Review evidence |
| Primary artefact | Steering committee pack | Quarterly review package |
| Relationship to decisions | Assures delivery against the approved plan; decides no investment | Synthesises evidence for the executive’s three decisions; decides none of them |
| Escalation trigger | Tolerance breach against the baseline | Evidence that a product should pause or pull, or a guardrail under strain |
| Success test | Projects closed to time, cost and scope | Every quarterly review produces reallocation decisions |
| Characteristic failure | An accurate pack that changes nothing | The role begins allocating investment and recreates the committee |
The success-test row is where the difference shows most clearly. A quarterly review that produces no reallocation decisions either has a perfect portfolio, which does not exist, or is operating as a reporting exercise rather than a governance mechanism (Hodgson, 2026, Ch. 7).
PMO functions distribute across the portfolio's three accountabilities
Retiring the PMO does not mean discarding its work. Most of what a PMO does has a destination in the product operating model, and each destination follows the accountability the function serves.
| PMO function | Destination | What changes |
|---|---|---|
| Portfolio reporting and benefits tracking | Portfolio Product Manager | Evidence moves from delivery status to outcome measures, and the audience moves from oversight to reallocation |
| Methodology, standards and capability development | Portfolio Product COO | The job moves from enforcing a lifecycle to ensuring the operating model works as designed |
| Cross-project dependencies and shared platform constraints | Enterprise Architect | Dependencies are managed as technical-integrity risks to the portfolio, not as schedule risks to individual projects |
| Project initiation, stage gates and closure | Retired | Persistent products with lifecycle-differentiated funding remove the events these processes governed |
The Portfolio Product COO row resolves a question the PMO transition usually leaves open: who owns ways of working once the PMO has gone? The principle is to govern the level below and stay there. The Portfolio Executive sets structural conditions. The Product COO ensures those conditions operate as designed. The Scrum Master enforces the resulting guardrails at team level (Hodgson, 2026, Ch. 8). Method stewardship survives the transition, but it becomes an operating model accountability rather than a compliance function.
Retire the PMO as a structure; evolve its people into the portfolio function
The PMO should be retired because its governing question is bound to the project as the unit of funding. For as long as the PMO exists as a structure, the organisation keeps producing project evidence and executives keep reading it. Renaming the office changes nothing, because moving to a product model does not simply replace project management with product management. It shifts executive accountability from whether an initiative is on time and on budget to whether an investment is producing measurable outcomes (Hodgson, 2026, Ch. 7).
Evolving the PMO’s people is the faster and lower-risk path. A PMO Lead brings three things a newly hired Portfolio Product Manager would take a year to acquire: the cross-portfolio relationships, the discipline of a reporting cadence, and working knowledge of how executives consume evidence.
Two capabilities must be built on top of that foundation. The first is interpreting outcome evidence: reading EBM Key Value Areas to judge whether a product is creating value, rather than whether work is complete (Scrum.org, 2024).
The second is Cost of Delay, which sequences investment by what the organisation loses each quarter the highest-priority work remains unstarted. Because Cost of Delay is calculated on future value, it removes sunk cost from the conversation (Reinertsen, 2009).
The difficulty is the habit, not the skill. Teams that have produced a RAG pack for years will reach for it under pressure, and executives who have read one for years will ask for it. The test of whether the transition has taken hold is simple: the first quarterly review under the new charter must end with reallocation decisions, not noted updates.
What this means for senior leaders
- Treat the PMO Lead as the leading candidate for the Portfolio Product Manager accountability, and plan the capability build for EBM evidence and Cost of Delay before the first quarterly review.
- Write down, before the transition begins, that the Portfolio Product Manager does not allocate investment. The three allocation decisions stay with the Product Portfolio Executive, inside the envelope the Board sets.
- Assign methodology and standards to the Portfolio Product COO, and dependency and platform constraints to the Enterprise Architect, so that no PMO function is left without an owner.
- Retire stage gates and project closure alongside the PMO. Leaving them in place keeps project evidence flowing, and project evidence cannot answer the reallocation question.
An organisation that makes this transition keeps the people who already understand its portfolio and gives them evidence that can move investment. The quarterly review then becomes the place where funding follows value, rather than the place where the steering pack is noted.
References
- Hobbs, B., & Aubry, M. (2007). A multi-phase research program investigating project management offices (PMOs): The results of phase 1. Project Management Journal, 38(1), 74–86. https://doi.org/10.1177/875697280703800108
- Hobbs, B., Aubry, M., & Thuillier, D. (2008). The project management office as an organisational innovation. International Journal of Project Management, 26(5), 547–555. https://doi.org/10.1016/j.ijproman.2008.05.008
- Hodgson, M. (2026). Evolve: The operating model AI demands. Zen Ex Machina.
- Reinertsen, D. G. (2009). The principles of product development flow: Second generation lean product development. Celeritas Publishing.
- Scrum.org. (2024). The evidence-based management guide: Improving value delivery under conditions of uncertainty. https://www.scrum.org/resources/evidence-based-management-guide
