The OKR framework, as it was originally practiced, drew a sharp line that most companies have since erased. There were committed objectives and aspirational ones, and they were different kinds of promise. A committed objective was a thing you were expected to deliver at 1.0, full stop, and missing it was a real failure that demanded an explanation. An aspirational objective was a deliberate stretch, set so high that landing at 0.6 or 0.7 was the designed outcome, and hitting it fully meant you had sandbagged. Two categories, two contracts, two ways of reading the score.
Then the distinction quietly fell out of practice while the vocabulary stayed. Today most companies have a single undifferentiated pile of OKRs, all scored on the same scale, all spoken about in the same tone, with no marker for which ones are commitments and which ones are reaches. This looks like a simplification. It is actually the removal of the one piece of information that made the score interpretable.
Why mixing the two breaks the score
A score of 0.7 means opposite things in the two regimes. On a committed objective, 0.7 is a miss, a thirty-percent shortfall on something you promised to fully deliver, and it should trigger a serious conversation. On an aspirational objective, 0.7 is a triumph, exactly the ambitious outcome the stretch was designed to produce. When both kinds sit on the same board with no label, a 0.7 is uninterpretable. You cannot tell whether to celebrate it or escalate it without knowing which contract it was under, and the board no longer carries that information.
This is how the 0.7 convention corrupts OKR scoring so thoroughly. The famous "0.7 is healthy" guidance was always advice for aspirational objectives specifically. Applied blindly to committed ones, it quietly tells teams that missing a commitment by thirty percent is fine and expected, which dissolves the entire idea of a commitment. Once everything is scored as if it were aspirational, nothing is actually committed, and the company loses the ability to make a hard promise inside its own goal system.
The deeper loss: you can no longer tell a bet from a dream
Beyond the scoring mechanics, erasing the distinction destroys a planning signal. A healthy quarter has a small number of things the company is genuinely committing to, the table stakes it must deliver, and a separate set of ambitious reaches where it is deliberately aiming beyond comfortable. Knowing the ratio is strategic information. A board that is all commitments is timid. A board that is all aspiration is unaccountable, because nothing on it is a real promise. The mix tells you something true about the company's posture for the quarter.
When the two are blended into one undifferentiated list, that signal vanishes, and the board collapses into the same failure as a goal list that is not a strategy: a flat enumeration with no structure indicating relative weight, risk, or kind of promise. You cannot read the company's intent off it, because the information that would let you has been averaged away.
Why teams collapse the distinction
It happens for a comfortable reason. Maintaining the distinction is uncomfortable, because a committed objective is a place you can unambiguously fail. Aspirational framing is softer; if everything is a stretch, every miss has a built-in excuse. So there is a gentle, constant pressure to relabel commitments as aspirations after the fact, especially the ones that are going badly, because aspiration is the category where falling short is the plan. Over time the committed column empties into the aspirational one, not by decision but by drift, and the company arrives at a board where everything is a hopeful reach and nothing is a hard promise. This is a quiet form of goal theater: the appearance of ambitious goal-setting with the accountability carefully removed.
Putting the contract back
The fix is to make the kind of promise an explicit, visible property of every objective, set at planning time and not editable after the fact to launder a miss. Each objective should declare whether it is committed or aspirational before the quarter starts, and that declaration should be as prominent as the objective itself, because it is what tells everyone how to read the eventual result. A committed objective that lands at 0.7 is a flagged miss that owes an explanation. An aspirational one at 0.7 is a success. Same number, different contract, and the contract is on the board.
This is also where the OKR framework connects back to the rest of the system. Committed objectives are the ones whose underlying work you most need to trace and protect, because a missed commitment is a real problem you want to see coming, not discover at scoring time. Aspirational objectives can tolerate more uncertainty by design. Knowing which is which tells you where to point your attention during the quarter, not just how to grade it at the end.
What to do this quarter
Go through your current board and force every objective into one of two columns: committed or aspirational. Do not allow a third "it depends" category, because the ambiguity is exactly the problem. The exercise is uncomfortable, and the discomfort is the point. You will find objectives that everyone has been treating as soft aspirations but that the business genuinely depends on, and others dressed as firm commitments that are really hopeful bets.
Then check the ratio. If almost everything lands in the aspirational column, your goal system has quietly lost the ability to hold a commitment, and your green scores are not telling you what you think. If almost everything is committed, you are probably not aiming high enough anywhere. Either way, the distinction you restore is worth more than any refinement to the objectives themselves, because it makes every score on the board mean something again.
FAQ
What is the difference between aspirational and committed OKRs? A committed OKR is one you are expected to deliver fully, where missing is a real failure that needs explaining. An aspirational OKR is a deliberate stretch set so high that landing at 0.6 to 0.7 is the designed outcome and hitting 1.0 means you aimed too low. They are different contracts, and the same score means opposite things under each.
Why does blending them break OKR scoring? Because 0.7 is a miss on a commitment and a triumph on an aspiration. With no label on the board, a score becomes uninterpretable. The "0.7 is healthy" guidance was always meant for aspirational objectives; applied to commitments it tells teams a thirty-percent miss is fine, which is how the 0.7 convention corrupts scoring.
Why do companies drop the distinction? Because a committed objective is a place you can clearly fail, and aspirational framing makes every miss excusable. There is constant pressure to relabel struggling commitments as aspirations after the fact, so the committed column drifts empty. The result is goal theater: ambitious-looking goals with the accountability removed.
How do we restore it? Make the kind of promise an explicit, visible property of each objective, set before the quarter and not editable afterward to launder a miss. Then watch the ratio: an all-aspirational board cannot hold a commitment, an all-committed one is too timid. The label is what makes each score on the OKR board mean something again.