When Being Right Isn't Enough

Governance  |  IV&V  |  Executive Visibility 

When Being Right Isn’t Enough.

THE SITUATION

I was the head of a governance function responsible for connecting strategy to execution, managing portfolio risk, and providing independent program oversight across a large, complex portfolio. Over the course of nine months, I identified and raised the same material program risks with executive leadership three times. The data behind each assessment was correct. The analysis was sound. The timing was early enough to act.

The clients left anyway.

This was not a failure of information. It was not a failure of communication. What failed was the structure around the oversight function — a structure that had no mechanism to require a documented response, no independent validation of the competing explanations being offered, and no way to make the pattern of overrides visible to someone with the authority to act on it.

WHAT I SAW

What I recognized — and what took longer for the organization to acknowledge — was that the problem was not the quality of the oversight. It was the architecture around it.

The governance function was operating exactly as designed. It was surfacing risks, producing accurate data, and raising issues through the appropriate channels. But the structure had never been built to make that information matter. The person providing the oversight had less organizational trust than the person being overseen. There was no requirement that leadership formally address a flagged risk — only that they receive it. And there was no mechanism to make a pattern of overrides visible before the outcome made them undeniable.

Governance theater is not the result of bad intentions. It is the result of structures designed to demonstrate oversight rather than deliver it.

The distinction between a governance structure that performs and one that functions is not visible from the outside. Both produce the meetings, the reports, and the documentation. Only one produces decisions that change before the cost of the wrong decision becomes irreversible.

WHAT I DID

After this experience, I built a structural response to the problem it revealed. The three elements that were missing became the foundation of how I design oversight functions:

First, a documented response requirement. When the oversight function raises a material risk, leadership must formally address it — not override it informally and move on. A flag that can be dismissed without a response is not oversight. It is a suggestion.

Second, structural separation. The team inspecting the work cannot manage the team delivering it, and the oversight function cannot report to the area it evaluates. This sounds obvious. It is violated constantly — gradually, for practical reasons, and almost always at exactly the wrong moment.

Third, pattern visibility. A single override is a judgment call. Three overrides, each followed by the outcome the oversight function predicted, is a pattern. Someone with the authority to act on that pattern must be able to see it before the outcome makes it undeniable.

WHAT CHANGED

The clients who left did not come back. That cost was real and it was permanent. But the structural lessons from that experience have shaped every governance function I have built since.

Organizations I have worked with after implementing these three structural elements have demonstrated a measurably different dynamic: risks raised by the oversight function receive formal responses rather than informal dismissals, escalation patterns become visible rather than buried in meeting notes, and leadership teams develop the organizational habit of treating independent oversight as a strategic asset rather than an administrative function.

The most significant outcome is one that is difficult to quantify but easy to recognize: the moment when a senior leader stops defending against the oversight function and starts relying on it. That shift — from tolerance to trust — is what governance built on structure rather than personality eventually produces.

WHAT THIS ILLUSTRATES

Executive Decision™ Framework:

Organizational Visibility + Governance by Principle

This story sits at the intersection of two pillars of the Executive Decision™ Framework. Organizational Visibility is not just about having data — it is about having a structure that ensures the data reaches the right people with the authority to act on it, before the cost of inaction becomes the lesson. Governance by Principle means building oversight that outlasts the people who built it and the relationships that would prefer it silent.

The PMO leader in this story was doing everything right. The organization had built a stage and called it a governance structure. Those are not the same thing — and the difference between them is measurable, in clients and in cost.