What is project governance?

Project governance is one of those terms that gets used constantly in PMO work and understood rarely. Most people treat it as a synonym for bureaucracy — the approvals, the paperwork, the committee that slows everything down. That’s not governance. That’s bad governance.

Done well, governance is what makes the difference between an organisation that delivers change reliably and one that keeps starting projects it can’t finish, overspending on work that doesn’t land, and asking the same lessons-learned questions at every retrospective.

So what actually is project governance?

Project governance is the framework of structures, processes, and accountabilities that ensures projects are initiated, executed, and closed in a way that serves the organisation’s interests — not just the project team’s.

It answers three fundamental questions:

• Are we doing the right projects? — Are our projects aligned to strategy, properly prioritised, and worth the investment?
• Are we doing them right? — Are projects being run consistently, to appropriate standards, with adequate controls?
• Are we getting the benefits? — Are completed projects delivering what they promised, and are we learning from the ones that didn’t?

If your organisation can answer all three confidently, your governance is working. Most can’t.

Why governance matters — and why it so often fails

Without governance, organisations tend toward the same set of failure modes. Projects get started without clear sponsorship. Scope expands without anyone formally approving the change. Problems get hidden in status reports because there’s no safe escalation path. Projects finish without anyone checking whether the benefits ever materialised.

The failure isn’t usually a lack of capable people. It’s a lack of clarity about who is responsible for what decision, at what point, with what information. Governance provides that clarity.

The reason governance fails is usually simpler than people think: it gets designed for show rather than function. Committees that meet to hear updates rather than make decisions. Approval processes that add three weeks without adding value. Stage gates that every project passes regardless of readiness. The governance exists, but it doesn’t govern.

The difference between governance and management

This distinction trips people up constantly. It’s worth being clear about it.

Management is the day-to-day running of a project. Planning, tracking, risk management, team direction, stakeholder communication. The project manager does this.

Governance is the oversight of management. Ensuring that management is happening appropriately, that decisions are being made at the right level, that the project remains aligned to its original purpose. The project board, steering group, and PMO do this.

A project manager who is also doing their own governance — making investment decisions, approving their own scope changes, assessing their own risks — has no governance. They’re marking their own homework.

What good governance looks like in practice

Good governance isn’t invisible, but it shouldn’t be the main event. In a well-governed organisation:

• Every project has a named sponsor who is genuinely accountable for its success
• Decision rights are clear — everyone knows what they can approve themselves and what needs escalating
• Status reporting is honest because there’s a safe environment for raising concerns early
• Projects that are failing get stopped or reset, not allowed to limp to an inevitable bad conclusion
• Completed projects are reviewed and the lessons actually influence how the next one is run

The test of good governance is not whether the governance structures exist. It’s whether the organisation makes better decisions because of them.