Good governance standardises decision integrity, not organisational shape.
Two organisations can use the same portfolio-management standard, establish committees with similar names and buy comparable reporting tools, yet produce very different decisions. One may escalate the right issues early, challenge weak investments and allocate scarce resources deliberately. The other may create more meetings, more status reporting and more approval gates while difficult decisions continue to drift.
The difference is not necessarily discipline. It is often design.
Portfolio governance sits between enterprise intent and operational commitment. It determines who can authorise investment, who can stop work, what information must be visible, which risks require escalation and how competing priorities are resolved. That means a governance system cannot be judged simply by whether it resembles a recognised framework. It must be judged by whether it helps this organisation make better decisions under its actual conditions.
The Strategic Context
The 2017 edition of PMI's Standard for Portfolio Management, as reflected in the supplied Week 4 material, describes portfolio governance through four broad functions: oversight, decision-making, control and integration. The framework is useful because it clarifies that governance is wider than project assurance. It links authority, performance visibility and strategic alignment across the portfolio.
But the same teaching material makes an equally important practitioner point: there is no single governance recipe that works in every environment. Legal obligations, organisational culture, decision hierarchy, maturity, risk exposure and the nature of the portfolio all influence how governance needs to operate.
That distinction matters at executive level. A highly regulated infrastructure operator should not govern its investment portfolio exactly like an early-stage technology company. A global manufacturer with multiple business units will need different escalation paths from a privately owned firm where investment authority is concentrated around a small leadership team. A defence program dealing with sovereign capability, security and public accountability will require different evidence thresholds from an internal process-improvement portfolio.
Governance therefore has two layers. The first is relatively stable: integrity, transparency, accountability, appropriate authority and strategic alignment. The second must adapt: structures, forums, thresholds, decision cadence, information depth and delegation.
Confusing those layers creates either weak governance or unnecessary bureaucracy.
What Leaders Commonly Misread
A common mistake is to treat governance as a collection of structural artefacts: steering committees, templates, approval gates, dashboards and policies. Those mechanisms matter, but they are not the purpose of governance.
A committee is useful only if the right decisions reach it at the right time. A dashboard is useful only if it changes executive understanding. A stage gate is useful only if leaders are genuinely prepared to stop, reshape or defer an initiative. A policy is useful only if authority, incentives and behaviour make it operable.
The Week 4 material includes a practical warning against “falling in love” with the tool. That is more than a software observation. It points to a broader governance failure mode: organisations can become highly compliant with the mechanics of governance while avoiding the substance of it.
This is particularly dangerous when leadership equates more control with more accountability. Additional approvals can actually blur accountability when everyone participates but no one clearly owns the decision. More reporting can reduce transparency when teams produce so much information that the material issues are harder to see. More centralisation can reduce responsiveness when competent leaders closer to the issue no longer have authority to act.
Related article: Portfolio Governance Is a Decision-Rights System
Reframing the Issue
The better question is not, “What governance structure should we implement?”
It is:
What decisions must this organisation make repeatedly, under what constraints, and where should authority sit for those decisions to be timely, informed and accountable?
That reframing changes governance from organisational furniture into decision architecture.
It also creates a useful design principle: centralise the decisions that require enterprise trade-offs; delegate the decisions that benefit from local knowledge and speed.
The boundary between the two will vary by organisation. Capital allocation, portfolio risk tolerance and major strategic exceptions often require enterprise-level authority. Operational sequencing within an approved envelope may be better delegated. The governance model should make those boundaries explicit rather than allowing them to emerge through politics.
Governance Design Starts With Context
Regulatory exposure changes the evidence threshold
Where legislation, safety obligations, public accountability or contractual requirements are significant, governance must make compliance visible and non-negotiable. That does not mean every decision needs executive approval. It means the organisation must be clear about where discretion ends.
The practical test is whether managers know which constraints are fixed, which are negotiable and which require escalation.
Culture changes how control is experienced
The same governance process can produce very different behaviour in different cultures.
In a low-trust environment, additional reporting may encourage defensive behaviour, late escalation and selective disclosure. In a high-autonomy environment, loosely specified governance may produce inconsistent decisions. Entrepreneurial cultures may resist formal controls until portfolio complexity becomes too high for informal coordination. Bureaucratic cultures may comply with process while avoiding real judgement.
Governance design therefore has to account for how people interpret authority, challenge and failure, not only how the organisation chart is drawn.
Decision hierarchy should follow competence and accountability
The Week 4 material emphasises that decision-making should sit where competence, accountability and authority reside. All three matter.
Authority without competence creates poor judgement. Competence without authority creates delay. Responsibility without clear accountability creates escalation games.
A mature model identifies the major recurring decisions across the portfolio and assigns an explicit owner for each. Examples include component authorisation, funding changes, risk acceptance, benefit reforecasting, major scope changes, termination and resource reallocation.
Related article: The Right Stakeholder at the Wrong Time Can Damage Portfolio Decisions
Maturity changes the amount of structure required
A portfolio-management system that is new or inconsistent may need more explicit rules, common definitions and standard decision criteria. A mature organisation may be able to operate with greater delegation because decision quality is already reinforced through capability, culture and shared practice.
This does not mean mature organisations need less governance. It means they can often rely less on procedural supervision and more on clear principles, trusted information and capable decision-makers.
Portfolio characteristics should influence governance intensity
A portfolio dominated by small, reversible experiments should not be governed like a portfolio of billion-dollar, irreversible infrastructure commitments. Governance intensity should reflect factors such as investment size, reversibility, strategic significance, uncertainty, external obligations, safety consequences and dependency concentration.
The purpose is proportionality. Leaders should spend their scarce attention where a decision could materially change enterprise value or exposure.
Decision Framework
A practical governance design review can be built around five tests.
1. Context test. What features of the organisation materially affect governance: regulation, ownership, geography, culture, maturity, risk and portfolio type?
2. Decision test. What recurring decisions determine portfolio value? Which of them are difficult to reverse?
3. Authority test. For each decision, who has the competence, accountability and formal authority to decide? Where are these currently misaligned?
4. Control test. What minimum information is required to exercise oversight without burying decision-makers in operational detail?
5. Integration test. How does the governance system connect strategy, portfolio choices, programs, projects and operations so that one level does not optimise at the expense of another?
If these questions cannot be answered clearly, adding another committee is unlikely to solve the problem.
From Strategy to Execution
Immediate action should focus on mapping the portfolio's major recurring decisions. For each, identify the current owner, approval threshold, evidence required, escalation path and expected decision time. This exercise often reveals duplication, gaps and informal authority that the organisation chart does not show.
Medium-term capability building should establish common decision criteria, improve the quality of portfolio information and strengthen the competence of people exercising governance roles. Governance forums should be reviewed for purpose, not habit. Meetings that only receive reports should either become decision forums or be redesigned.
Long-term strategic positioning requires governance to evolve with the enterprise. New regulation, acquisitions, geographic expansion, higher-risk technology and larger portfolios can all change the appropriate balance between delegation and control. Governance should therefore be reviewed as the organisation changes, not treated as permanent infrastructure.
The objective is not governance consistency for its own sake. It is consistent decision quality under changing conditions.
Signals to Monitor
Watch for signs that the governance system is becoming disconnected from reality:
- decisions repeatedly occur outside formal forums;
- approval cycles grow while decision quality does not improve;
- leaders ask for more data because existing reports do not reveal the trade-off;
- teams escalate late because bad news is culturally expensive;
- the same issue is approved by multiple groups without one clear owner;
- portfolio decisions are made without reference to capacity, capability or strategic consequences;
- governance tools become more detailed while executive attention becomes more superficial.
These are not administrative irritations. They indicate that the organisation's decision architecture is no longer aligned with the work it must govern.
Questions for the Leadership Team
- Which portfolio decisions are important enough to require enterprise-level authority, and which are unnecessarily centralised today?
- Where do competence, accountability and formal authority currently sit with different people or groups?
- Does our governance design reflect our regulatory exposure, culture and portfolio risk, or have we copied a generic model?
- Which governance activities genuinely improve decisions, and which exist mainly because they have always existed?
- Are teams rewarded for early transparency, or do our behaviours encourage problems to remain hidden until escalation is unavoidable?
- If our strategy or operating model changed materially next year, which parts of our governance system would need to change with it?
Closing Perspective
Governance is not effective because it is formal. It is effective when authority, information and accountability meet at the point where an important choice must be made.
Standards can provide useful principles. Templates can accelerate implementation. Tools can improve visibility. None of them can decide how this organisation should balance speed, control, risk, autonomy and enterprise value.
That remains a leadership responsibility.
About EraNorth Insights
EraNorth Insights publishes practical analysis on strategy, projects, operations, transformation and decision intelligence for professional and organisational use. About EraNorth.