Portfolio management becomes necessary when the organisation can no longer optimise change by governing initiatives one at a time.
Growth creates a predictable governance problem.
An organisation begins with a small number of projects. Senior leaders know the initiatives personally. Resource conflicts can be resolved informally. Strategic alignment is obvious because the project list is short.
Then the volume, value and complexity of change increase.
Projects span functions. Shared resources become constrained. Dependencies multiply. Business cases compete. Executives receive more reporting but have less visibility of the total system.
The hypothetical Mawson Zoo assignment in the supplied material is built around this transition. The organisation has undertaken more projects of increasing value and complexity while the proportion delivering on time, within budget and with expected value has declined. The brief asks for portfolio management that aligns components to strategy, clarifies governance and communication, integrates processes and creates success measures linked to strategic objectives.
Although the case is fictional, the design problem is real.
The Strategic Context
Portfolio management should not be introduced as another administrative layer.
If the organisation adds a portfolio office without changing decision rights, prioritisation or resource allocation, it may simply produce better reports about the same overloaded system.
A transformation should instead create an operating model for enterprise investment decisions.
The supplied EY material offers a practical sequence: translate strategy into initiatives, identify programs and projects, prioritise and balance the portfolio, approve it and feed risk review back into future decisions.
That sequence can be adapted into a staged implementation without reproducing EY's proprietary process design.
What Leaders Commonly Misread
The first mistake is starting with software. Portfolio tools can improve visibility, but they cannot decide strategic priorities or resolve authority.
The second is attempting to design the perfect future-state process before making obvious decisions about low-value or duplicate work.
The third is creating governance without removing old governance. This produces more forums, more reporting and slower decisions.
The fourth is defining success as implementation of the portfolio process itself. The purpose is better strategic outcomes, not process compliance.
Reframing the Issue
The transformation should be framed around four capabilities.
Visibility: What work exists, what it costs and what strategic objective it supports.
Choice: How initiatives are selected, prioritised, deferred and stopped.
Control: Who has authority over funding, risk, dependencies and resource conflicts.
Learning: How delivery evidence and realised benefits change future investment decisions.
A portfolio-management implementation is successful only when these capabilities improve.
Stage 1: Establish Portfolio Truth
Before optimising the portfolio, create a credible inventory.
Identify:
- active projects and programs;
- material operational initiatives consuming the same capacity;
- sponsors and owners;
- strategic objectives;
- committed and forecast spend;
- critical resources;
- benefits;
- dependencies;
- major risks.
The goal is not perfect data. It is enough truth to expose obvious gaps and conflicts.
At this stage, organisations often discover unauthorised work, duplicate initiatives and strategic objectives with no meaningful delivery support.
Stage 2: Establish Decision Rights
Define which forum can:
- approve new work;
- set priorities;
- reallocate resources;
- accept material risk;
- stop or defer initiatives;
- resolve cross-functional conflicts.
This should be accompanied by delegated thresholds so executives do not become bottlenecks.
Related article: Portfolio Governance Is a Decision-Rights System
Stage 3: Create the Decision Framework
The supplied EY material combines strategic alignment, economic value and decision factors such as resources, risk and interdependencies.
An organisation can adapt that logic to its context.
The criteria should be few enough to use consistently and rich enough to expose trade-offs.
For example:
- strategic contribution;
- expected benefit;
- regulatory or safety necessity;
- risk;
- capacity requirement;
- dependency complexity;
- time to value;
- reversibility.
Scores may support comparison, but leadership judgement should remain explicit.
Stage 4: Rebalance the Existing Portfolio
Do not apply the process only to new proposals.
The current portfolio must be challenged.
This is often where the transformation creates its first real value. Low-value work can be stopped. Projects can be resequenced. Resources can be released. Duplicate efforts can be merged.
Without this step, the new framework sits on top of historic commitments.
Stage 5: Connect Risk and Benefits
Portfolio management should then move beyond selection.
Project and program risk information should feed portfolio decisions. Benefits should remain visible after delivery.
The organisation begins learning which investments create value and which assumptions repeatedly fail.
Related article: Risk Belongs in Portfolio Decisions Before Projects Fail
Decision Framework
A staged implementation should pass five tests.
Strategic test: Does the new system visibly change the connection between strategy and funded work?
Authority test: Can decision-makers actually move resources?
Capacity test: Does the portfolio reflect real delivery and change limits?
Evidence test: Are decisions based on comparable information?
Outcome test: Can leadership measure whether portfolio choices are improving strategic value?
The hypothetical Mawson Zoo brief specifically requires success measures linked back to strategic objectives. That is the right discipline for any implementation.
From Strategy to Execution
Immediate action: build the portfolio inventory, identify the largest conflicts and clarify interim decision authority.
Medium-term capability building: establish prioritisation, resource views, benefit ownership, risk escalation and a regular governance cadence.
Long-term strategic positioning: integrate portfolio review with strategy, budgeting and organisational capability planning so that portfolio management becomes part of how the enterprise is run rather than a specialist process.
Avoid launching every maturity element at once. The transformation itself can overload the organisation.
Signals to Monitor
Early positive signals include fewer unowned initiatives, faster resolution of resource conflicts, clearer stop decisions and improved traceability between strategy and investment.
Warning signs include a growing reporting burden, unchanged approval behaviour, portfolio staff becoming data administrators, senior leaders bypassing priorities and software implementation becoming the primary measure of progress.
Questions for the Leadership Team
- What problem are we expecting portfolio management to solve that existing governance cannot?
- Which decisions must change for the implementation to create value?
- What current work would be challenged if the new framework were applied today?
- Who will have authority to stop or defer initiatives?
- What minimum data is required for credible portfolio decisions?
- Which strategic measures will demonstrate that portfolio management is improving enterprise outcomes?
- How will we prevent the portfolio function from becoming another reporting layer?
Closing Perspective
Organisations do not need portfolio management because they have many projects. They need it when project-by-project governance can no longer optimise the whole system.
The implementation should therefore begin with decisions, not tools.
Build visibility. Clarify authority. Rebalance commitments. Connect risk and benefits. Then mature the supporting processes.
The objective is not a better portfolio office. It is a better allocation of the organisation's future.
About EraNorth Insights
EraNorth Insights publishes practical analysis on strategy, projects, operations, transformation and decision intelligence for professional and organisational use. About EraNorth.