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.
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 it08 — 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.
Then someone asks the question the reporting or deliverable was supposed to answer.
Time passes. The relied upon claim survives. The capacity to verify the claim doesn't.
The problem is not necessarily a bad metric, result or claim.THE DISTINCTIONS
It is that someone is relying on it—or is about to— to make a consequential decision before its evidentiary basis is clear.
What would you have expected to see if this claim or program had no effect?
An objective can be a coordination device — a boundary object that lets different communities 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.
Organizations often introduce goals, metrics, and dashboards because leaders need visibility into work, initiatives, and resource demands. Visibility is not the same as control, and making activity visible is not the same as establishing results. Even when visibility improves, competing priorities, unclear decision rights, incompatible incentives, and an inability to stop or redirect work can persist.
The review tests whether the measurement function is real. It names the coordination function as legitimate but different. The finding is about the instrument, not the people who adopted it.
The mechanism that was supposed to produce the outcome has no place in the artifact. The artifact names an objective and key results; it does not name the initiative. So the mechanism migrates: into the objective (written as a project), into the key result (written as a deliverable), or into a funding channel nobody in the review is examining.
That migration is why the dashboard shows progress and the outcome doesn't arrive. It is visible on Monday morning. It is also the most common thing the review finds.
The examination starts with the claim someone will rely on, not with the assumption that every report is wrong. Existing reviews may already answer the question. We identify what they establish, what they leave open, and whether the remaining gap matters to the decision.
The examination informs the consequential decision. It does not replace the decision-maker's judgment, implement the program, or guarantee the business outcome.
OKR Strategist independently checks a specific relied upon claim before an important decision. We explain what the evidence supports, what is missing, and what remains uncertain. We do not control your strategy, make the decision for you, run the program, or guarantee business results.
A finding may support proceeding, proceeding with conditions, re-underwriting the relied upon claim, or concluding that the evidence is insufficient. That last conclusion is not proof that the relied upon claim is false. The decision remains with the authorized decision-maker.
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.
Management by objectives. The Balanced Scorecard. OKRs. Three waves, the same structure — a measurable goal, a review cadence, a claim that the practice causes performance — and the same critique, made in 1970, made again in 2007, never answered.
The review is not a critique of the framework. It is a test of the specific claim in front of your 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.
Sometimes you approved the metric, deliverable or program—and are accountable for the consequences.
The Determination Diagnostic examines what the inherited relied upon claim can support before the successor commits their authority, capital, or reputation to it.
A deadline alone does not establish fit. The decision must be consequential, the relevant evidence must be examinable, and the work must be feasible within an agreed scope.
"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.
Run these two tests before you call.
1. Ask three people to define the objective in one sentence, independently.
If the definitions diverge, you have found the coordination function. The review tells you what that means for the measurement claim.
2. Ask what you would have expected to see if the program had no effect.
If nobody can answer, the program has no claim, hypothesis, or other belief that is contrary to the facts — and no one in the room can tell you whether the program caused anything.
If both tests come back clean, you may not need the review. We will tell you so.