Don't re-commit the OKR you keep missing

How many quarters can an OKR slip before it stops being a commitment and becomes a standing agenda item? At one company I reviewed with, the answer turned out to be three. A specific product launch sat in the Q3 deck marked in progress. It had been marked in progress in Q2. And in Q1. At that company, the original commitment was made 9 months earlier, in the previous January's annual planning. It was now October, and the launch had been re-committed 3 times, each version presented as a sharper estimate, none of them paired with an honest account of why the last estimate had failed.

The system was doing what an unenforced system always does. Aspirational commitments turn into serial deferrals. Every quarterly review noted the slip and rolled the date forward. The team learned, over enough cycles, that a quarterly commitment was a suggestion. The real credibility of any quarter's OKRs came from the team's pattern recognition, not from the language on the slide.

The failure is the missing consequence. An OKR that slips one quarter is recoverable. An OKR that slips two quarters has stopped being a commitment and become a discussion topic. An OKR that slips three is a line item nobody expects to hit. Most companies run it this way because enforcement is uncomfortable: it forces explicit conversations about why the slip happened, who owns it, and what the alternatives are. The discomfort is the reason the conversation never occurs, and the absence of the conversation is the reason the slip repeats.

You pay for unenforced OKRs in two places. First, in calibration. The team learns that a commitment made at review doesn't have to be defended at the next review, so the discipline of forecasting accurately erodes — there's no penalty for forecasting wrong. Second, in strategy. OKRs are supposed to tell the team what the company is prioritizing. When they slip without explanation, the team concludes the stated priorities aren't the real ones.

The intervention is uncomfortable and it works. Treat a slipped OKR as a binary: kill it out loud, or fund it with full priority for the next quarter. The kill is direct. We committed to X. We didn't deliver. The reason is Y. We're not attempting it again, because Z. The team hears the reasoning and re-learns that a commitment means something.

The harder discipline comes earlier: commit to fewer OKRs. Most companies commit to too many. The first rule of OKR design is that the set should be concentrated enough that missing any one of them is a serious failure. Three OKRs a quarter, held as real commitments with real cost for missing them, ship more than twelve held as wishes.

So be honest about what the system is for. If it's meant to align the team on a few priorities and force focus, it needs enforcement. If it's meant to give every function a slate of quarterly line items the company can point at in a board deck, then it isn't steering the company — it's describing it. Pick one on purpose, not by drift.

The OKR that has slipped three times is the OKR you've already decided not to deliver. Your calendar decided it. Say so before the fourth quarter does.