You've already asked someone to check.

You've already had the conversation in the hallway. You've already noticed that nobody can tell you what the number proves — only what it is.

The renewal is coming. The board is asking. The acquirer is closing. The claim you're being asked to rely on was produced by someone else, and you will be the one who signed.

Before you put your name behind it, find out whether it can carry the weight.

Someone else made the relied upon claim. You may have to answer for it.

01 — A contract is up for renewal. You have to approve the next term, but no one has checked whether the claimed savings are real.
‍
02 — You have inherited green dashboards. Now you have to explain what actually improved—and how you know.
‍
03 — Your board, audit committee, or investors ask what the results really prove. You need an answer you can stand behind.
‍
04 — You are buying a business, deploying AI, changing the workforce, or releasing funding—and you will own a decision built on results you did not produce.

05 — The program is called a success, but nobody has checked whether its business case still holds.

06 — Everyone close to the numbers already knows which relied upon claim won't hold up. So do you.
‍
07 — The objective is written as a project. The key result is written as a deliverable. The work that was supposed to produce the outcome is funded somewhere else, and nobody in the review is looking at it.

08 — Three people define the same objective three different ways. Each definition is reasonable. None of them is the same.

09 — You ask what you would have expected to see if the program had no effect. Nobody in the room can answer.

The question that matters remains unanswered: which of these relied upon claims are true?

Green dashboards. No believers.
The review cycle closes. The question stays open.
Risk travels down. Authority stays up.
Success enters the record. The business case never reopens.
Time passes. The relied upon claim survives. The capacity to verify the claim doesn't.

Then someone asks the question the reporting or deliverable was supposed to answer.

The problem is not necessarily a bad metric, result or claim. It is that someone is relying on it—or is about to—to make a consequential decision before its evidentiary basis is clear.

The Green Spiral

The pattern you've seen runs the same way in organization after organization:

‍01 — Introduce a new methodology.
02 — Create new terminology.
03 — Create new rituals.
04 — Create new metrics.
05 — Report progress.
06 — Discover contradictions.
07 — Add more process. More dashboards. More governance. More terminology.
08 — Continue — because stopping would expose that the prior cycle didn't establish anything.

↺ Repeat. Each cycle reports green. None establishes whether anything is true.

What rises with each cycle is investment — process, dashboards, governance, terminology. What doesn't rise is the validity of the claims. The divergence is the spiral.

Each cycle makes the organization more sophisticated at representing progress — not necessarily more capable of producing it.

If that pattern is familiar, you don't need another framework. You need to know which of your numbers are still true.

The spiral is one instance of a broader problem: organizational claims systematically outrun their evidence. That problem has a name in the research — the assurance gap.

Coordination and measurement are different jobs. No artifact can do both.

An objective can be a coordination device — a way for different communities to work together without agreeing on a definition. That is legitimate, and it is why the artifact survives. It can also be a measurement instrument — a construct that is operationalized, tested, and held to a standard. That is also legitimate.

What no artifact can do is both at once. Coordination requires interpretive flexibility. Measurement requires a single enforced definition. The artifact that coordinates cannot measure, and the artifact that measures cannot coordinate.

That is why the dashboard shows progress and the outcome doesn't arrive.

The finding is about the instrument, not the people who adopted it.
‍

The question nobody in the room has asked:

What would you have expected to see if this claim or program had no effect?

The Defense You've Already Heard

"The artifact, framework, or process was fine. The implementation was poor."

You've heard it. You may have used it yourself.

It is the defense that protects the framework by attributing every failure to the person holding it. It works because the construct was never specified — so every failure can be attributed to another layer: implementation, execution, culture, leadership.

The review names the defense, because a claim that cannot be falsified at any layer cannot be shown to work at any layer. Naming the defense is what makes the finding stand.

Two questions the review begins with.

1. Can three people define the objective in one sentence, independently, and agree? If not, the artifact is coordinating, not measuring — and the review will say so.

‍2. What would you have expected to see if the program had no effect? If nobody in the room can answer, the program has no claim, hypothesis, or other belief that is contrary to the facts — and no one can tell you whether the program caused anything.

These are the first questions the review asks. If both tests come back clean, you may not need the review.
‍

Sometimes it works

A founder with a personal goal. A small team with a tight feedback loop and a single decision-maker. No rating layer. In that setting the artifact often does what it says, and the review will say so plainly.

The review is for the scaled setting — where the artifact is doing several jobs at once and where the claim is being relied on by someone who did not produce it. It will name the difference.

One consequential decision.
One determination question.

If your situation is one of these, the Diagnostic is designed for it.

1. Leadership transition. Before a new CFO, COO, or CEO stands behind results they did not produce.
2. Board challenge or formal sign-off. When management's reporting has not answered the question the board needs resolved.
3. Acquisition, investment or renewal. Before claimed improvements or synergies are relied on in a transaction price or another funding decision.
4. AI deployment. Your AI and automation program is about to accelerate decisions against metrics nobody has independently verified.
5. Restructuring and workforce decisions. The business case says the work can be eliminated, consolidated, or automated — while the people who could tell you what capability actually disappears are being removed.
6. The sponsor who's been in the seat. You approved this program. You can no longer establish whether the reporting informs decisions or anticipates the answers the organization wants to hear.

You may inherit the relied upon claim. You inherit the consequential decision. Check what the evidence can show before you put your name behind it.

The examination informs the consequential decision. It does not replace the decision-maker's judgment, implement the program, or guarantee the business outcome.