Your OKRs are green.
Can you prove why?

An independent determination of consequential program claims — for leaders who must stand behind results they did not produce.
The KRs Diagnostic examines what the evidence establishes, whether the program caused the reported result, and what value remains after the costs and productive capability consumed.
The Diagnostic →
See if this sounds familiar ↓

You may recognize the cycle.

01 - The board keeps asking where the promised savings went — and nobody can produce the evidence.

02 - Every dashboard is green. Nobody in the room believes them.
‍
03 - You're about to put your name on numbers you didn't produce, from a program you didn't sponsor.
‍
04 - The transformation was declared a success. The business case was never revisited.

05 - The business case is about to become part of the purchase price — but the claimed improvements have not been independently established.

06- The board has asked what the reported success actually proves. The reporting cycle has closed; the question has not.
‍
07 - Everyone close to the numbers already knows which one won't survive scrutiny. So do you.

The question that matters remains unanswered: which of these numbers are still true?

The pattern has a name: the green spiral

The green spiral runs the same way in organization after organization:

01 - Introduce a new methodology. The organization needs a better way to execute.
‍
02 - Create new terminology. The new language gives the work a shared structure.

03 - Install new rituals. Meetings and reporting cycles make progress visible.

04 - Build new metrics. Indicators give the organization numbers to track.

05 - Expand dashboards and reporting. More activity becomes measurable and easier to communicate.

06 - Discover contradictions. The reported progress no longer fits what people see in the operation.

07 - Add governance to contain the contradictions. Reviews, controls and escalation paths are introduced.

08 -  Continue, because stopping would expose the prior failure. More process is added. The next reporting cycle begins.

Each cycle can report green. None, by itself, establishes whether the claims are true.

The organization becomes more sophisticated at representing progress without necessarily becoming more capable of producing it.

If this resembles the last few years inside your organization, you may not need another framework. You may need to know which of your numbers are still true.

The framework can be explicit. The operating model may not be.

Organizations introduce goals, metrics and reporting systems to make performance more visible. But the formal framework does not necessarily make the rules governing performance explicit.

Who controls resources? How are priorities resolved when they conflict? What evidence counts? How are criteria applied? What happens when reported progress contradicts operating reality?

When these rules remain implicit, a goal-setting problem can be a symptom of a deeper operating problem. More metrics and more reporting may make the system easier to describe without making it more capable of producing, detecting or correcting the results it claims.

The question is not whether the organization has goals. It is whether the operating conditions, evidence and decision rules support the conclusions being reported.

Visibility is not the same as control

Organizations often introduce goals, metrics and dashboards because leaders cannot see enough of the work happening across the business to make confident decisions.

But visibility into selected objectives is not a comprehensive view of organizational activity. And a more complete view of the work does not, by itself, resolve competing priorities, allocate scarce resources or establish whether reported results are real.

Those are different capabilities: seeing the work, deciding what should happen, and establishing what the work actually achieved.

When they are treated as one problem, an organization can become better at reporting activity without becoming better at choosing, executing or verifying the results that matter.

The numbers may be real. The explanation may still be unproven.

Five distinctions matter when a consequential decision depends on reported results:

1. A metric can be measurable without meaningfully representing the outcome.
2. Selecting a key result does not make it evidence of that outcome.
3. Implementing an initiative does not establish that the intended result occurred.
4. A real result is not automatically attributable to the program.
5. An attributable result is not automatically worth its full cost, including capability and capacity consumed.

These are different questions. A green dashboard does not answer all of them.

A reported answer is not an independent examination.

A green status is a report. A plausible explanation is a hypothesis. Neither, by itself, establishes that a program produced the reported result or that the resulting value justifies the cost.

Two things must be distinguished.

‍The claim: What does the organization say happened, what does it attribute the result to, and what value does it say was created?

‍The examination: How were the question, criteria, evidence, reasoning and conclusion constructed and tested?

A polished answer does not establish that a defensible examination produced it. A defensible examination does not guarantee a favorable or conclusive answer. It may establish that the evidence is insufficient, that the criteria conflict, or that the question cannot yet be answered responsibly.

‍The KRs Diagnostic examines the basis for reliance on the claim—not just the answer the organization has reported.

‍
The signed Determination Memo records what the evidence supports, what remains unresolved, the boundaries of the examination, and what the conclusion can responsibly inform.

One question.
One independent determination.

Does the evidence support what this program claims—and would the claim survive scrutiny from someone with no stake in the answer?

The KRs Diagnostic examines the claim, the evidence behind it, the causal explanation, the economics, and whether the measures remain valid for the organization as it exists now.

It begins with the evidence and assurance already available. It does not presume that existing controls, audits or reviews are inadequate. It identifies what they establish and whether a material question remains unanswered for the decision at hand.

See the Diagnostic →

The result is a written determination.

01 - Proceed
The claims survive examination within the stated scope — all five tests, on the evidence that exists.
Permits: certify them, price them, build next year's plan on them.
02 - Proceed with conditions
The supported claim depends on named conditions that must remain true or be closed.
Permits: continuation with gates — not open-ended faith.
03 - Re-underwrite
The current evidence cannot carry the investment or business case as presented.
Permits: repricing — rewrite the thesis before more capital follows the old one.
04 - Evidence insufficient
The available evidence cannot verify the claims within the agreed scope.
Permits: the refusal — stop certifying until the evidence chain is rebuilt.

There is no fifth verdict — "probably fine" is not a determination.

The signed Determination Memo records the reasoning, evidence trail, limitations and scope. The verdict is not sold in advance, and the finding is not negotiated to secure approval.

See what the Diagnostic examines →

Built for the person who inherits the decision.

Sometimes the successor inherits more than a business case. They inherit a conclusion whose acceptance criteria were never made explicit, whose evidence trail is incomplete, or whose assumptions no longer hold.

They are expected to stand behind the reported result without having produced it—and may be judged on a decision whose basis they cannot independently establish.

The KRs Diagnostic examines what the inherited claim can support before the successor commits their authority, capital, or reputation to it.

The Diagnostic is designed for consequential decisions such as:
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 & 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.

A deadline alone does not establish fit. The question must be consequential, the relevant evidence must be examinable, and the work must be feasible within an agreed scope.

We are not on anyone's side.
That's the point.

Every alternative available to you has a stake in the answer. Implementation partners need the implementation to continue. Transformation offices need the transformation to have worked. Internal teams need their own reporting confirmed.

None of this makes you complicit. Procurement rewards certainty language, scoring rubrics reward claimed magnitude, and every executive needs a sentence they can repeat upstairs — so you can sincerely need a reliable answer while sitting inside a process that rewards claims that are expensive to challenge. That contradiction is the default condition, not a character flaw. The OKRs Diagnostic resolves it: the challenge becomes cheap, early, and yours — before a trigger event forces it at a price and a moment not of your choosing.

We sell one thing: a verdict we can defend, delivered to the person with the authority to act on it. We have no implementation to protect, no next phase to sell, and no relationship with your vendors.

That independence is not a marketing claim. It's the business model — and it's why a negative finding from us means something a positive finding from an interested party never can.

One caution about the market this creates. As independent verification becomes expected, it will be imitated. A verifier paid by the implementer, certified by the vendor, or auditioning for the repair work is not independent — whatever the report cover says. We call this the captured verifier: the form of independence without its structure. Independence is not a label on the engagement; it is the economics of the firm behind it.

And we hold ourselves to the same test. Every verdict we sign enters an anonymized public verdict record, and the distinction is published annually. If we only ever find failure, you should stop believing us.

A verdict without an implementation incentive.

OKR Strategist does not sell transformation programs, implementation retainers or vendor referrals. A separate Resolution engagement may be considered when a determination identifies work that could help resolve the problem; it is never automatic.

The practice is designed to have no economic reason to prefer “Proceed” over “Evidence insufficient.” The commissioner decides what action to take within the agreed terms. The commissioner does not buy the right to change the finding.

Every signed determination is intended to contribute to an anonymized public verdict record, including supportive findings. The record is designed to make the practice's pattern of conclusions inspectable over time—not to presume that every program fails.

The claim is the unit of examination. Not the presumed intent of the person who produced it.

Bring the decision.
We'll scope the question.

A 30-minute, no-fee scoping call establishes the decision at stake, what remains unresolved, whether the evidence can be examined, and whether the KRs Diagnostic is the right instrument.

If it fits, scope, fee, evidence requirements and delivery assumptions are agreed before the examination begins. If it does not fit, we will say so.

Book a scoping call →

Still working with a narrower key-result problem? The KR Evidence Review is a separate 90-minute working session for one objective and three to five key results, with a written memo.

Can you stand behind the numbers?

Establish what can be proven, what the result means, and what decision you can defend.
The numbers may be inherited. The accountability for relying on them may be yours. Three questions separate a reported result from a defensible decision.
Proof 
Can the claim be substantiated?

What does the evidence actually establish—and what remains unverified?
Attribution
Do the numbers establish that the initiative produced the result?
A result can be real without being caused by the program credited for it.
Consequence
Does the evidence justify the decision economically?
‍
What value remains after accounting for  costs, risks, and capability consumed?