How Projects Create Value Through Governance

Ask a delivery team what governance gives them and the answer is usually a list of things it takes: a monthly pack that costs two days to assemble, a forum that reviews everything and decides nothing, a set of slides nobody reads before the meeting. When governance is working well it is close to invisible. When it is working badly it is the most visible thing on the project. That imbalance is why the link between governance and value is so easy to miss.

The short answer is that governance creates value by holding the decisions a project cannot legitimately make for itself, and by making them at the point where they can still change the outcome. A delivery team can build the right thing efficiently. It cannot, on its own authority, decide that the right thing has changed, that the remaining money would produce more benefit somewhere else, or that a commitment made eighteen months ago no longer serves the organisation. Those decisions sit outside the team by design. How well and how quickly they are taken has as much influence on whether a project was worth its cost as anything the team does day to day.

Decision rights come before reporting lines

Reporting is a component of governance, not the point of it. Information exists so that someone with authority can act on it, so the useful question about any governance arrangement is what can be decided here, by whom, and how fast.

This is where Section 2.1.1 of the PMBOK® Guide is helpful. Sitting inside the Governance Performance Domain, it treats value creation as something governance actively contributes to rather than something that happens elsewhere and is later reported on. Governance covers authorisation, integrated planning, oversight of execution, assessment of change and closure, and each of those is a point at which a project either stays pointed at something worth doing or drifts away from it.

The practical version of that idea is decision rights. Every project has a set of choices that exceed the project manager's authority: changing a benefit commitment, releasing the next tranche of funding, accepting a lower scope in exchange for an earlier outcome, stopping a workstream. Governance is the arrangement that says who holds each of those, what evidence they need, and how long it should take. When those things are clear, value is protected quietly. When they are vague, the project defaults to completing what it was told to build, because completing is the only action nobody has to authorise.

Value moves while the project is being delivered

Business cases are written with the information available at the time, and the world does not hold still to accommodate them. Markets shift, a regulation lands, a supplier fails, a technology becomes cheaper, another part of the organisation solves half the problem first. The benefit a project was funded to produce can grow, shrink or move to a different beneficiary while the delivery plan carries on unchanged.

Consider a county council replacing three legacy case-management systems with a single platform. Most of the benefit case rests on removing duplicate data entry across two of those three services. Eight months into a two-year programme, a national decision moves one of those services into a shared regional arrangement inside eighteen months. The delivery team spots it almost immediately, because their integration analyst is in the meetings where it is discussed.

What happens next has very little to do with delivery competence and almost everything to do with governance. The team cannot stop building that module, redirect the money into the migration work that still pays back, and re-baseline the benefit case. Someone else has to do that. If the programme board has a standing threshold that says a material change to the benefit case comes to them at the next available meeting, the decision can be taken in six weeks and around a third of the remaining spend is redirected to work that still produces something. If there is no such threshold, the question waits for the annual planning round, the module is built, and it goes live for a service that transfers a year later. In both versions the project manager did the same job. Only one of them created value.

What good governance actually has to get right

The difference between those two councils is not the existence of a board. Both have one. Four questions separate governance that contributes value from governance that consumes it.

The first is who can say no, and how large a decision they can take alone. If nobody in the room can commit funding or release scope, the meeting is a briefing.

The second is what evidence would change the decision, and who produces it. Governance that reviews progress against plan sees only whether the project is on track. Governance that also reviews whether the benefit case still holds can see when being on track has stopped mattering.

The third is how long it takes to get from evidence to instruction. Decision latency is measurable and rarely measured. A board that meets monthly but takes three months to conclude anything has an effective cycle time of a quarter, and every option that expires inside a quarter is closed to that project.

The fourth is what happens to the money when the answer is to stop something. If stopping a workstream means the funding disappears instead of moving to the next best use, the organisation has quietly made stopping irrational, and its governance will never see a proposal to do it.

None of these require a heavier process. Most of them are answered in a page and revisited when the project changes shape.

Governance can also destroy the value it exists to protect

The failure mode runs both ways, and the over-governed project is at least as common as the under-governed one. Escalation thresholds set so low that routine decisions travel up three levels. Assurance that arrives after the decision has become irreversible. A board with fourteen attendees, none of whom individually holds the authority to conclude. Reporting whose production cost exceeds the value of the decisions it informs.

Proportionality is the discipline here, and it is the reason tailoring matters as much in governance as in scheduling or documentation. A safety-critical or heavily regulated programme genuinely needs formal, evidenced, auditable decision-making. An internal improvement project with a modest budget and a single sponsor does not. The governance question in adaptive delivery is not whether to have it but where to attach it: to release and funding decisions, and to periodic reviews of whether the product still justifies the investment, rather than to change requests on a scope baseline nobody is maintaining.

Reasoning about decisions you do not hold

The current PMP® Examination Content Outline places the establishment of project governance in the Business Environment domain, including defining success metrics and setting out escalation paths and thresholds, while value-based delivery sits among the Process tasks. The two are deliberately connected. Exam scenarios tend to describe a situation where something has changed and ask what a project manager does about it, which is a question about authority and evidence before it is a question about technique. Candidates who have only worked inside one governance culture often find this the hardest judgement to build, and it is one of the areas PMP® exam preparation sharpens quickly, because it forces you to reason about decisions you do not personally hold.

On a live project, none of this needs a governance review to start. Write down the three decisions most likely to be needed in the next six months, name the person who can take each one, and find out how long the last comparable decision took. If any of the three has no owner, that is the gap worth raising, and raising it is a more valuable contribution than any status report you will produce this quarter.

Andre Malowney

Interested in going further?

Recognising when a decision belongs above you, and presenting it with the evidence that lets someone else take it quickly, is a judgement that develops fastest against realistic situations rather than definitions. Omega's PMP® Exam Preparation works through governance and value decisions in that form, for both the exam and the projects you go back to afterwards.

The Governance Performance Domain in the PMBOK® Guide Eighth Edition is the fuller treatment of how authorisation, oversight and change assessment connect to project value.

Ad · Amazon affiliate link.

References

A098: PMO Value: What Should a Project Management Office Actually Deliver?
A090: Project Governance Explained: Who Decides What, and Why
A091: Project Governance vs Organisational Governance: What's the Difference?
A014: Intended Value vs Realised Value
A013: Value Delivery in Project Management: What It Means in Practice

PMP and PMBOK are registered marks of the Project Management Institute, Inc.