Programme Governance Frameworks That Scale

What Programme Governance Is (and Isn't)

Governance is not control. It's not micromanagement. It's not a layer of bureaucracy that slows delivery.

Good programme governance is the framework of decision rights, cadences, and information flows that ensures:

• The right people make the right decisions at the right time
• Risks are surfaced early and managed proactively
• Resources are allocated to the highest-value work
• Delivery stays aligned with strategic objectives
• Accountability is clear and consequences are real

The Three Pillars

1. Decision Rights (Who Decides What)

Unclear decision rights cause delays, conflict, and rework. Define explicitly:

Programme Board / Steering Committee decides:

• Programme scope changes (adding/removing projects)
• Budget allocation and reallocation between projects
• Strategic priority changes
• Go/no-go decisions for major milestones
• Escalated risks that exceed programme manager authority

Programme Manager decides:

• Resource allocation within approved budget
• Delivery approach and methodology
• Vendor selection within delegated authority
• Risk mitigation strategies within approved contingency
• Operational decisions that don't affect scope, budget, or timeline

Project Managers decide:

• Sprint-level scope and priority (within project boundaries)
• Technical approach and architecture (within agreed standards)
• Team-level resource allocation
• Day-to-day delivery decisions

Document this as a RACI or Decision Authority Matrix and get it approved by the steering committee at programme initiation.

2. Governance Cadences (When Decisions Happen)

Build a rhythm that creates regular decision points without overwhelming teams:

Weekly: Programme Sync (45 min)

• Attendees: Programme Manager + Project Managers + key leads
• Purpose: Delivery health, cross-project dependencies, blocker resolution
• Output: Updated RAID, resolved blockers, escalation items for steering

Fortnightly: Steering Committee (60 min)

• Attendees: Sponsor + senior stakeholders + Programme Manager
• Purpose: Strategic decisions, budget approvals, risk escalations, milestone sign-off
• Output: Decisions made, resources committed, direction confirmed
• Pre-read: Sent 48 hours in advance (dashboard + decision papers)

Monthly: Programme Health Review (90 min)

• Attendees: Programme Manager + Project Managers + Finance + HR
• Purpose: Deep-dive on programme health, resource utilisation, financial performance
• Output: Corrective actions, resource adjustments, forecast updates

Quarterly: Strategic Review (half day)

• Attendees: Executive sponsor + C-suite + Programme Manager
• Purpose: Programme alignment with strategy, benefits progress, investment decisions
• Output: Continued funding approval, strategic direction adjustments, portfolio alignment

3. Information Flows (What Information Goes Where)

Design information flows so each governance level gets the right signal:

Upward (to steering): RAG status, milestone progress, budget performance, top risks, decisions needed. One page maximum. No detail — just signal.

Downward (to projects): Strategic context, priority changes, resource decisions, approved changes. Clear and timely — teams shouldn't learn about direction changes through rumour.

Lateral (between projects): Dependency status, shared risk updates, integration progress, resource sharing. Direct communication between PMs — not routed through the Programme Manager.

Scaling Governance

Small Programme (2-3 projects, <30 people)

• Lightweight governance: fortnightly steering, weekly PM sync
• Programme Manager may also manage one project directly
• Minimal documentation: one-page status, shared RAID, dependency board
• Decision-making is fast and informal within clear boundaries

Medium Programme (4-8 projects, 30-100 people)

• Full governance structure: weekly sync, fortnightly steering, monthly health review
• Dedicated Programme Manager (not also a PM)
• PMO support for reporting, financial tracking, and governance administration
• Formal change control for scope and budget changes
• Structured dependency management with weekly review

Large Programme (8+ projects, 100+ people)

• Multi-layer governance: project-level, programme-level, portfolio-level
• Programme Management Office (PMO) with dedicated staff
• Formal stage gates between programme phases
• Earned value management for financial control
• Regular independent assurance reviews
• Benefits realisation tracking with dedicated benefits manager

Governance Anti-Patterns

Governance theatre: Meetings happen, reports are produced, but no decisions are made and no actions are taken. Fix: every governance meeting must produce at least one decision or action. If it doesn't, cancel it.

Decision bottleneck: All decisions flow through the steering committee, creating a 2-week delay for routine approvals. Fix: delegate routine decisions to the Programme Manager with clear authority limits. Reserve steering for strategic decisions only.

Information overload: Steering committee receives 50-page packs that nobody reads. Fix: one-page summary with RAG + decisions needed. Detail available on request, not pushed by default.

Governance without teeth: Decisions are made but not enforced. Projects ignore steering direction without consequence. Fix: track decision implementation. Escalate non-compliance. Governance without accountability is just theatre.

Over-governance for the context: A 3-project programme with the governance overhead of a 20-project programme. Fix: scale governance to complexity. Start light and add structure only when problems demonstrate the need.

Measuring Governance Effectiveness

• Decision cycle time: Days from "decision needed" to "decision made." Target: <5 business days for routine, <2 for urgent.
• Steering committee attendance: Key decision-makers present. Target: >80% attendance at every meeting.
• Decision implementation rate: % of steering decisions implemented within agreed timeframe. Target: >90%.
• Escalation resolution time: Days from escalation to resolution. Target: <5 business days.
• Governance overhead: % of programme capacity consumed by governance activities. Target: <10%.

If governance overhead exceeds 15% of programme capacity, you're over-governing. Simplify.

---

Download the [Delivery Dashboard template](/templates) for a governance-ready programme health reporting format.