Project Governance Is Measuring the Wrong Thing

By Gianni Fracchia

 | 

Written: March 19, 2024

Project governance has a measurement problem that is structural rather than technical. It is costing organizations significantly more than the execution metrics show. The frameworks are rigorous. The stage-gate processes are comprehensive. The reporting is consistent and timely. The metrics tracked across the project lifecycle are accurate. What those metrics cannot tell any governance body is whether the project that is being executed correctly was the correct project to approve in the first place. That question is not in the governance framework. It is the governance gap that most project frameworks have not been designed to close.

Execution quality and investment decision quality are different things. Most project governance frameworks treat them as the same thing, or treat investment decision quality as a precondition that business case approval establishes rather than as a governance variable that requires its own oversight. A project that is delivered on time, within budget, and to the agreed scope is counted as a governance success. A project that was approved against a poorly examined business case, with scope that was never independently challenged and alternatives that were never genuinely assessed, can deliver perfectly against its approved plan and still represent a poor investment. The two assessments are independent. The governance frameworks that track only the first have no mechanism for detecting the second.

The approval decision is where governance has the most leverage and consistently provides the least. Before approval, changing direction costs almost nothing. After it, teams have assembled, budgets have been allocated, vendors have been engaged, and every stage of delivery that follows makes correction more expensive. The governance frameworks that apply their most rigorous oversight to delivery are applying it after the point where the most consequential decision has already been made. The governance frameworks that apply the most rigorous oversight to delivery phases are applying rigorous oversight after the point at which the most consequential decisions have already been made. The stage-gate before the first stage is where governance has the most to offer and consistently provides the least.

The analytical work that precedes most project approvals is produced by the team that wants the investment approved. The investment committee reviewing that work is not reviewing an independent finding. It is reviewing an argument. The governance framework that cannot distinguish between those two things is not examining investment decisions. It is ratifying them.

The consequence is a project portfolio that cannot be defended on analytical grounds. Each initiative in it was approved. Each approval followed the governance process correctly. What the portfolio cannot demonstrate, for any initiative within it, is that the approved direction was the best available option for the investment it consumed, because that question was never put to an analytical team positioned to answer it honestly. The portfolio record is comprehensive. The analytical foundation it rests on is not.

The governance characteristic that produces better investment decisions is independence, not process. The organizations that consistently make sound investment decisions do not simply add an analytical step before approval. They add an analytical step conducted by a team with no stake in the outcome. That distinction is the entire difference. Analytical work produced by the proposing team, however thorough, is positioned to confirm. Analytical work produced by an independent team is positioned to challenge. The governance framework that specifies the former has addressed analytical presence. The framework that specifies the latter has addressed analytical quality. They are not the same specification and they do not produce the same outcomes.

Independence is the operative condition. Analytical work conducted by the proposing team, or reviewed by the investment committee only at the approval meeting without prior circulation, is not positioned to challenge the direction it was commissioned to support. It produces documentation. Independent analytical work, reviewed before the approval meeting by a team with no stake in the outcome, is positioned to challenge. It produces findings. The governance frameworks that specify that a business case must exist before approval have addressed analytical presence. They have not addressed analytical independence. Those are different governance specifications with different outcomes.

The project governance frameworks in most organizations were not designed to measure investment decision quality because investment decision quality was not recognized as a distinct governance concern. Execution quality was the concern, and the frameworks addressed it well. What those frameworks could not see is that a significant portion of project execution problems are not execution problems at all. They are the delivery-phase expression of investment decisions made without adequate analytical foundation. Scope instability, benefit shortfalls, and strategic misalignment are not failures of project management. They are consequences of an approval decision that was not analytically prepared to make the commitments it made.

Project governance frameworks were built to answer one question: was the project delivered correctly. That question is worth answering. It is not the question that determines whether the investment was sound. The investment was determined to be sound at the approval meeting. The governance process that made that determination reviewed an argument produced by the team that wanted it approved. The execution metrics that would later reveal the consequence of that determination began only after the commitment had been made. The framework that measures delivery quality with precision while remaining structurally blind to investment decision quality is not a rigorous governance framework. It is half of one. The half that matters most is the half it was not designed to include.

Consulting and Speaking

For consulting or speaking engagements, visit the Contact page.