A governing body earns its place when it changes the quality and direction of decisions, not when it becomes the final audience for a monthly status pack.
Program boards are often populated by the most senior people involved in an initiative. That can create an illusion of strong governance.
Yet a board that listens to presentations, notes risks and asks for another update next month may provide visibility without governance.
Programs need something more demanding: a forum where executives test whether the investment remains strategically valid, resolve conflicts that cannot be solved lower down, accept or reject material risk, redirect resources and intervene when benefits are threatened.
The difference is behavioural, not cosmetic.
The Strategic Context
Hanford’s 2005 IBM governance paper describes steering committees as mechanisms through which affected business segments can understand issues, assess impacts and adjust direction, resources or timing. It also recommends periodic strategy reviews during program execution.
The Week 10 study notes extend governance into risk and issue escalation, change control, quality governance, decision-point reviews, component transition and closure.
BCG and PMI’s 2013 PMO paper adds a complementary message: senior leaders need meaningful, forward-looking information tied to strategic impact so they can make course corrections. The PMO should enable those decisions rather than drown executives in activity data.
These sources converge on one point: governance is an active intervention system.
What Leaders Commonly Misread
The first misreading is that visibility equals control. A board can understand that a program is in difficulty and still fail to govern if it cannot or will not change anything.
The second is that a “green” dashboard proves the investment is healthy. Delivery measures can remain within tolerance while benefits weaken, stakeholders disengage or strategic assumptions change.
The third is that escalation is evidence of program-management weakness. In a well-designed program, escalation is a normal mechanism for decisions that exceed delegated authority.
The fourth is that seniority automatically improves decisions. A board without clear evidence, decision framing and accountability can become an expensive audience.
Related article: Portfolio Reporting Should Change Decisions, Not Produce More Data
Reframing the Issue
A program board has four essential jobs.
Protect strategic legitimacy
The board should test whether the program still deserves investment. Strategy, regulation, technology, customer conditions or operating priorities may have changed since approval.
Protect outcome integrity
The board should focus on whether the combined program remains capable of producing intended outcomes and benefits, not merely whether projects are meeting individual plans.
Resolve enterprise trade-offs
Cross-functional resource conflicts, competing priorities and operating-model choices often cannot be resolved by the program manager alone.
Intervene at thresholds
When risk, cost, benefit, schedule or stakeholder conditions cross agreed limits, the board must decide whether to accept, mitigate, redesign, defer or stop.
If the board performs none of these functions, it is closer to a reporting committee.
The Governance Pack Should Be Built Around Decisions
A common failure mode is a pack organised by workstream. Each project reports status, schedule, cost, risks and actions. The board receives a large amount of accurate information but little integration.
A decision-grade pack asks different questions:
- What changed since the last meeting?
- Which assumptions are now weaker or stronger?
- What threatens benefits across components?
- Which interdependencies need executive intervention?
- Where is the program outside delegated tolerance?
- What decisions are required today?
- What happens if we defer those decisions?
This is not an argument for less evidence. It is an argument for evidence organised around executive judgement.
BCG and PMI’s historical “minimum sufficiency” example is useful here. The idea is to focus executive attention on a small number of meaningful milestones, indicators, changes and exceptions rather than reporting every activity. The exact number is contextual; the principle is focus.
Decision-Point Reviews Should Reopen the Investment Question
Program governance is weakest when approval is treated as permanent.
A decision-point review should ask whether the program should:
continue unchanged, continue with conditions, redesign, re-sequence, reduce, pause or stop.
Those options make governance consequential.
The review should integrate evidence from benefits, costs, risks, stakeholder conditions, dependencies and strategic alignment. A component can be on time and still deserve termination if it no longer contributes sufficient value.
Related article: Strategic Alignment Must Be Re-Earned Throughout the Program
Decision Framework
Use a Board Value Test before each governance meeting.
| Governance question | Evidence required |
|---|---|
| Is the strategic case still valid? | Strategy changes, external signals, sponsor view |
| Are outcomes and benefits still achievable? | Benefit evidence, adoption, operational readiness |
| What has materially changed? | Exceptions, assumptions, dependencies, stakeholder shifts |
| What exceeds delegated authority? | Tolerance breaches, major risk or change |
| What decision is required now? | Options, recommendation, trade-offs, consequence of delay |
| Who owns implementation? | Named accountable executive or program leader |
If a meeting contains no material decision, leaders should ask whether a meeting was necessary or whether information could have been handled asynchronously.
From Strategy to Execution
Immediate action: redesign the next program-board agenda around decisions and strategic exceptions. Put required decisions first. Move routine status to appendices or dashboards.
Medium-term capability: establish decision-point reviews aligned to meaningful program transitions, not only calendar cycles. Define evidence standards for continuation, major changes and benefit confidence.
Long-term positioning: develop governance leaders who are comfortable stopping work, challenging sunk-cost logic and revisiting strategic assumptions. Program boards need judgement capability, not only organisational authority.
The PMO can support this by improving information quality and integrating cross-program dependencies, but it should not absorb accountability that belongs to business leaders.
The Board Must Protect the Program From Its Own Momentum
Large programs create constituencies. Teams are formed, suppliers mobilised, budgets committed and careers attached to delivery. Momentum can become a reason to continue.
Governance exists partly to resist that bias.
A strong board can ask questions the delivery system may find uncomfortable:
What if the original solution is no longer the best route to the benefit? What if the benefit has become smaller? What if another portfolio priority now creates more value from the same capacity? What if transition risk is greater than expected?
These are investment questions, not delivery criticisms.
Signals to Monitor
Watch for board meetings where decisions are repeatedly described as “noted”, major issues return month after month, executives ask for detail that should be resolved below board level, or recommendations arrive without alternatives and consequences.
Another warning sign is a board that never stops or materially redirects anything. That may reflect exceptional program quality, but more often it indicates that governance has become a confirmation mechanism.
Monitor decision latency, percentage of actions owned by executives versus the program office, and whether board interventions measurably change risk, benefits or strategic alignment.
Questions for the Leadership Team
- What decisions has this board made in the past quarter that materially changed the program?
- Which evidence tells us whether the investment remains strategically justified?
- Are we reviewing project performance or governing program outcomes?
- Which issues keep returning because the board has not made a definitive choice?
- What would cause us to pause, redesign or stop a component?
- Does our reporting create operational insight or simply demonstrate administrative control?
Closing Perspective
A program board should not be judged by attendance, pack quality or meeting cadence.
It should be judged by whether it makes better enterprise decisions at the moments when the program cannot safely decide for itself.
Related article: Program Governance Begins With Decision Rights, Not Committees
References
- Hanford, M. 2005, ‘Defining program governance and structure’, IBM Developer. Historical practitioner source; the publisher notes that the content is no longer maintained.
- University of South Australia, Week 10 Study Notes on Governance and the PMO, supplied course material based on PMI 2017.
- Keenan, P. et al. 2013, Strategic Initiative Management: The PMO Imperative, Boston Consulting Group and Project Management Institute.
Recommended Internal Links
[Related article: Program Governance Begins With Decision Rights, Not Committees][Related article: Strategic Alignment Must Be Re-Earned Throughout the Program][Related article: Portfolio Reporting Should Change Decisions, Not Produce More Data]
About EraNorth Insights
EraNorth Insights publishes practical analysis on strategy, projects, operations, transformation and decision intelligence for professional and organisational use. About EraNorth.