Skip to main content
BlogProgramme & Portfolio Governance

Why Programme Governance Fails at Scale, and How to Fix It

Programme Governance Practice2 min read

Programme governance is one of those disciplines that appears straightforward on paper but becomes extraordinarily complex in practice. When budgets are modest and stakeholders are few, a simple RACI matrix and monthly steering committee will usually suffice. But when programmes cross the ₦3 billion threshold, involve multiple delivery agencies, and span several years, the governance machinery that worked at smaller scales almost always breaks down.

The root cause is structural. Most governance frameworks are designed around a single project with a single sponsor, a single delivery team, and a single set of success criteria. When you scale that framework to a portfolio of interrelated projects, you create a web of reporting lines that generates enormous volumes of data but very little actionable insight. Steering committees become rubber stamping exercises. Risk registers grow to hundreds of items with no clear ownership. Decision rights become ambiguous, and escalation paths loop endlessly between committees.

At Coderex, we have seen this pattern repeat across public sector reform programmes, large infrastructure portfolios, and multi-year digital transformation initiatives. The programmes that succeed at scale share a common set of structural characteristics. First, they separate portfolio governance from project governance explicitly. Portfolio governance focuses on strategic alignment, resource allocation, and interdependency management. Project governance focuses on delivery performance, risk mitigation, and stakeholder engagement within a defined scope.

Second, successful large programmes invest in a dedicated Programme Management Office (PMO) with genuine authority. This means the PMO is not simply an administrative function producing status reports. It is empowered to halt workstreams that are off track, reallocate resources across projects, and challenge delivery teams on their assumptions. The PMO reports directly to the Senior Responsible Owner and has a standing invitation to the investment committee.

Third, governance at scale requires tiered decision making. Not every decision needs to reach the steering committee. Effective governance frameworks define clear thresholds: decisions below ₦50M are made at project level, decisions between ₦50M and ₦500M at programme level, and decisions above ₦500M at portfolio or board level. This tiered approach reduces bottlenecks and accelerates delivery without sacrificing oversight.

Finally, the most effective governance frameworks we have implemented embrace transparency as a design principle. Dashboards are visible to all stakeholders, not just senior leadership. Issues are surfaced early and discussed openly. The culture shifts from one where bad news is suppressed to one where early warning signals are valued. This cultural shift is often the hardest part of governance reform, but it is also the most impactful.

Key Takeaways

  • 1Separate portfolio governance from project governance with distinct forums and mandates
  • 2Empower your PMO with genuine authority to halt workstreams and reallocate resources
  • 3Implement tiered decision making with clear financial and risk thresholds
  • 4Design governance for transparency so issues surface early rather than late
  • 5Invest in governance capability building, not just framework documentation