Governance is effective when the organisation knows who can make which decision, on what evidence and with what accountability.
Many portfolio governance frameworks begin with committees, terms of reference and reporting calendars. Those elements matter, but they are not the core.
The core is decision rights.
Who can approve an investment? Who can change its priority? Who can move funding? Who can accept risk? Who can stop a project? Who owns the benefit after delivery? What happens when two executives compete for the same resource?
The supplied Mawson Zoo assignment brief, although hypothetical, makes governance and communication central to a proposed portfolio organisation structure. The supplied EY material similarly calls for executive approval of the portfolio and a decision framework that integrates resources, interdependencies, risks and business cases.
Together they point to a useful principle: portfolio governance is the mechanism by which strategic choice becomes authorised action.
The Strategic Context
Portfolio decisions cut across organisational boundaries.
Projects are often sponsored by functions. Resources are often owned elsewhere. Benefits may appear in another business unit. Risks may accumulate at enterprise level. This means no single project sponsor can optimise the whole system.
Governance provides a legitimate place to resolve those conflicts.
Weak governance usually takes one of two forms.
In the first, authority is centralised but evidence is poor. Senior executives make decisions from inconsistent data and spend time resolving operational detail.
In the second, information is abundant but authority is fragmented. Committees discuss problems repeatedly without anyone being able to reallocate resources or terminate work.
Both create delay.
What Leaders Commonly Misread
The first mistake is equating governance with meetings. Meetings are only useful if they lead to decisions that cannot be made elsewhere.
The second is using escalation as a substitute for delegated authority. If every variance requires executive approval, the portfolio will become slow and executives will be overwhelmed.
The third is assigning accountability without authority. A portfolio leader cannot be held responsible for balance if funding decisions remain distributed across independent functions.
The fourth is separating benefit ownership from investment governance. Leaders who approve expected benefits should know who remains accountable when project delivery ends.
Reframing the Issue
Governance should answer four questions.
Who decides?
What can they decide?
What evidence is required?
What is the escalation threshold?
This can be described as a decision-rights architecture.
A strong architecture distinguishes strategic decisions from delivery decisions. Project teams need freedom to manage authorised work. Portfolio governance should intervene when the decision affects strategic fit, enterprise capacity, material risk, funding or continuation.
Related article: Projects, Programs and Portfolios Are Different Decision Systems
The Essential Portfolio Decisions
A portfolio governance body should have explicit authority, directly or through defined escalation, over decisions such as:
- approving new initiatives;
- setting portfolio priorities;
- reallocating constrained resources;
- changing sequencing;
- approving major changes to investment logic;
- accepting material portfolio risk;
- stopping or deferring initiatives;
- resolving cross-program dependencies;
- confirming benefit ownership.
Not every organisation needs one central committee for all of these. Structure should fit context. But the rights must be clear somewhere.
Governance Must Integrate, Not Duplicate
The hypothetical Mawson Zoo brief asks for consistency across portfolio knowledge areas and a structure supporting governance and communication. That is a useful design constraint.
An organisation should avoid creating parallel forums for strategy, finance, risk and delivery that each make partial decisions on the same initiative.
Instead, decision pathways should connect them.
A financial review might determine affordability. A risk function may advise on exposure. Delivery leaders may assess feasibility. Portfolio governance then integrates those perspectives into an enterprise decision.
Decision Framework
A portfolio governance design can be tested against six criteria.
Authority: Can the forum make the decisions it is expected to make?
Representation: Are the necessary enterprise perspectives present without turning the forum into a crowd?
Evidence: Does the forum receive comparable, decision-relevant information?
Cadence: Is it frequent enough to respond to material change?
Escalation: Are thresholds clear for moving decisions between project, program and portfolio levels?
Accountability: Is ownership explicit after the decision?
A governance forum that fails any of these tests will tend to compensate with more meetings and more reporting.
From Strategy to Execution
Immediately, list the ten most important portfolio decisions made in the last six months and identify who actually made them. This often reveals gaps between formal governance and real power.
In the medium term, create a decision matrix that distinguishes project, program and portfolio authority. Include funding, scope, benefit, risk and resource decisions.
Longer term, align performance measures with decision rights. Executives should not be accountable for outcomes they cannot influence, and portfolio leaders should not be expected to optimise investments without authority over allocation.
Related article: Portfolio Reporting Should Change Decisions, Not Produce More Data
Signals to Monitor
Watch for repeated escalation of the same issue; committees that "note" problems without changing anything; project sponsors bypassing portfolio priorities; resources being reallocated through informal executive influence; benefits with no enduring owner; and decisions delayed because no forum has clear authority.
A further warning sign is when every project has governance but the portfolio as a whole does not.
Questions for the Leadership Team
- Who has authority to stop a project that remains within its delivery baseline but no longer creates sufficient strategic value?
- Which resource conflicts are resolved formally and which are resolved through influence?
- What decisions are repeatedly escalated because delegation is unclear?
- Does our portfolio forum receive enough evidence to compare initiatives?
- Who owns benefit realisation after project closure?
- Where do finance, risk and delivery governance duplicate rather than integrate?
Closing Perspective
Governance should reduce ambiguity about power.
The organisation needs to know who can commit resources, who can challenge assumptions and who can change course when evidence shifts.
When those rights are clear, reporting becomes lighter and decisions become faster. When they are unclear, governance expands in volume while authority remains uncertain.
About EraNorth Insights
EraNorth Insights publishes practical analysis on strategy, projects, operations, transformation and decision intelligence for professional and organisational use. About EraNorth.