A portfolio office can be asked to govern the enterprise while being structurally positioned to influence only one function.
Where should a Portfolio Management Office sit?
The answer is often presented as an organisation-chart question: under the CEO, finance, strategy, operations, technology or another executive function.
That framing is incomplete.
The more important question is:
What decisions is the PMO expected to influence, and does its organisational position give it the authority, neutrality and access required to do so?
The fictional InnovaLast case exposes this tension. The case describes a PMO created to establish mechanisms and controls that give the Managing Director, Board and other stakeholders confidence that the company's strategy can be executed successfully. Yet the organisation chart places the Portfolio Management Office beneath the Chief Information Officer, who in turn sits under the General Manager, Operations.
The mandate sounds enterprise-wide.
The structural position is functionally embedded.
That mismatch is strategically significant.
The Strategic Context
PMOs exist for different reasons.
Some are designed to improve project standards and reporting.
Some provide shared delivery services.
Some govern programs.
Some support capital planning.
Some manage enterprise portfolio prioritisation and benefits.
These are not the same operating models.
A PMO that standardises templates can sit close to the delivery function it supports.
An enterprise portfolio office expected to challenge strategic priorities, compare investments across functions and recommend resource reallocation requires a different level of sponsorship and decision access.
Confusion begins when organisations use one label for all of these roles.
What Leaders Commonly Misread
The first mistake is assuming the PMO's title defines its authority. Calling a function "enterprise portfolio management" does not give it enterprise decision rights.
The second is equating reporting access with governance authority. A PMO can see every project and still be unable to change priorities.
The third is placing the PMO where administrative support is easiest rather than where its decisions belong.
The fourth is ignoring perceived neutrality. If the portfolio office sits inside one function, other executives may view its recommendations as representing that function's priorities even when staff are acting objectively.
The fifth is solving authority problems with more process. When decision rights are weak, PMOs often compensate by increasing templates, gates and reporting. This can create control volume without strategic influence.
Reframing the Issue
PMO placement should be derived from mandate, decision rights and scope.
Ask first:
- Is the office managing delivery discipline?
- Is it coordinating programs?
- Is it advising on portfolio choices?
- Is it controlling investment gates?
- Is it managing enterprise capacity?
- Is it measuring benefits?
- Is it providing assurance to the Board?
Only then decide where it belongs.
Related article: Projects, Programs and Portfolios Are Different Decision Systems
The InnovaLast Structural Tension
In the fictional case, the PMO's charter is broad. It is intended to put in place mechanisms and controls that support execution of strategic priorities, risk management and stakeholder engagement.
At the same time, the case's organisation diagram locates the PMO under the CIO within Operations.
That position may be perfectly appropriate if the PMO primarily manages operational and technology projects.
It becomes more problematic if the office is expected to arbitrate priorities among:
- manufacturing;
- product development;
- marketing;
- business development;
- sales and service;
- facilities;
- ERP;
- regional expansion.
A PMO embedded within Operations may lack formal authority over peers in other functions.
The case does not tell us whether the Managing Director or Board gives the PMO additional enterprise authority outside the chart. Therefore, the correct conclusion is not that the structure is wrong. The conclusion is that the mandate and authority require clarification.
That is a stronger governance diagnosis because it does not invent facts.
Three PMO Models
Delivery PMO
Primary purpose:
- standards;
- reporting;
- project support;
- delivery assurance;
- methods.
This office can sensibly sit within a major delivery function.
Enterprise Portfolio Office
Primary purpose:
- investment visibility;
- prioritisation;
- portfolio balance;
- capacity;
- strategic alignment;
- benefits;
- executive decision support.
This model normally requires close connection to enterprise strategy, finance and executive governance. [FACT CHECK REQUIRED before publication if making claims about current "best practice" organisational placement.]
Federated model
A small enterprise portfolio function sets portfolio governance while delivery PMOs remain in major functions or business units.
This can combine enterprise decision architecture with local delivery expertise.
It also creates interface requirements that must be designed clearly.
No model is universally superior.
The correct design depends on scale, complexity, decentralisation and decision rights.
Authority Matters More Than Proximity
A PMO can sit near the CEO and still be weak if executives are not required to follow portfolio decisions.
Conversely, a functionally located PMO can have significant influence if governance formally grants it enterprise authority.
Placement is therefore only one signal.
Leaders should examine:
- sponsorship;
- committee rights;
- funding authority;
- access to portfolio data;
- escalation routes;
- ability to challenge business cases;
- ability to recommend stopping work;
- ownership of prioritisation;
- role in benefits review.
Related article: Portfolio Governance Is a Decision-Rights System
Independence Versus Embedded Knowledge
There is a real trade-off.
A central enterprise office can provide independence and cross-functional perspective.
An embedded PMO can understand operational reality more deeply and maintain stronger day-to-day relationships with delivery teams.
Organisations should not automatically centralise everything.
The design question is how to preserve operational knowledge while ensuring enterprise decisions are not captured by one function's incentives.
A federated model can help, but only if responsibilities are explicit.
Decision Framework
Use six tests to determine whether PMO structure matches mandate.
1. Scope test
Does the office govern one function, several programs or the enterprise portfolio?
2. Decision test
What decisions can it make, recommend or escalate?
3. Neutrality test
Will other functions view the office as an enterprise mechanism or as an extension of one executive?
4. Information test
Can it obtain comparable financial, risk, benefit and capacity information across the full portfolio?
5. Sponsorship test
Who protects the PMO when it challenges powerful sponsors or recommends stopping work?
6. Outcome test
Is the office measured on reporting compliance, delivery performance, portfolio value or strategic outcomes?
The organisational position should support the answers.
Avoid the Reporting Trap
When a PMO lacks authority, reporting becomes a safe activity.
It can collect status, standardise templates and produce dashboards without confronting the harder questions:
- Why is this initiative still funded?
- Which strategic objective does it support?
- What should be stopped to release capacity?
- Which executive owns the benefit?
- Where are dependencies creating enterprise exposure?
The PMO then becomes visible but not consequential.
Related article: Portfolio Reporting Should Change Decisions, Not Produce More Data
From Strategy to Execution
Immediate action: write the PMO mandate as a list of decisions and accountabilities rather than services and templates.
Medium-term capability building: align governance forums, escalation thresholds, data rights and sponsorship with that mandate.
Long-term strategic positioning: decide whether the organisation needs a delivery PMO, enterprise portfolio office, federated model or some combination. Structure should evolve as project volume and strategic complexity increase.
If the office is expected to govern enterprise transformation, its authority should not depend entirely on informal relationships.
Signals to Monitor
Watch for the PMO producing high-quality reports while priorities remain unchanged; cross-functional executives ignoring portfolio standards; PMO staff escalating every conflict because they lack authority; one function dominating the portfolio agenda; duplicated PMOs emerging because business units do not trust the central office; and strategic decisions occurring outside the formal portfolio process.
Another signal is when the PMO charter speaks about enterprise strategy but its performance measures focus almost entirely on reporting timeliness.
Questions for the Leadership Team
- What decisions is our PMO genuinely authorised to influence?
- Does its organisational position support the scope of those decisions?
- Which executives can bypass portfolio priorities without consequence?
- Is the PMO perceived as neutral across functions?
- What protects the office when it recommends stopping a sponsor's initiative?
- Are we measuring the PMO on process compliance or enterprise outcomes?
- Would a federated model preserve better delivery knowledge while strengthening enterprise governance?
Closing Perspective
PMO design should follow decision architecture.
A portfolio office that exists to support one function can be embedded there.
A portfolio office expected to challenge enterprise investment, capacity and strategic alignment needs authority that reaches across functions.
The organisation chart does not create that authority by itself, but it can either support or undermine it.
The test is simple: when the PMO identifies that the enterprise should change a priority, can the system actually make the change?
About EraNorth Insights
EraNorth Insights publishes practical analysis on strategy, projects, operations, transformation and decision intelligence for professional and organisational use. About EraNorth.