OKRs That Survive Contact With the Business

The second quarter problem

OKR rollouts follow a predictable arc. The first quarter is energetic. Workshops are held, objectives are written, everyone can recite the framework. The second quarter is quieter. By the third, the spreadsheet is out of date and the executive has moved on to something else.

The framework is not the problem. The way objectives are written, and the absence of a decision forum to support them, almost always is.

Five rules that make the difference

Write objectives as outcomes, not activities. Implement the new planning system is an activity. Cut the time from forecast change to updated plan from ten days to two is an outcome. The activity version cannot fail, which is precisely why it is popular and useless.

Limit to three per team. Teams that carry seven objectives are running a task list with better formatting. Three forces the trade off conversation to happen at the point of writing, where it is cheap.

Make key results measurable this quarter. If a result cannot move within the quarter, it is a strategic measure and belongs on the annual scorecard, not the quarterly one. Teams disengage fastest from numbers they cannot influence.

Separate commitments from ambitions. Some objectives must be delivered. Others are deliberate stretches where seventy per cent is a good outcome. Label which is which. Mixing them destroys the meaning of both.

Attach a stop list. Every set of objectives should name what the team will stop or defer to create the capacity. Without this, OKRs become an additional workload and are treated accordingly.

Cascade intent, not objectives

The most common structural error is copying objectives downward. The executive objective becomes the divisional objective becomes the team objective, with the numbers divided by headcount. This produces alignment on paper and confusion in practice, because teams inherit a target without inheriting the reasoning.

Cascade intent instead. Give each team the outcome the level above is trying to create and the constraints they must respect, then let them write objectives that contribute to it in a way that fits their work. This is exactly what DIRECT is for in the StratDo® approach: intent first, then OKRs written by the people who will deliver them.

Support them with a forum

Objectives generate trade offs. A team that discovers in week five that it cannot hit two of its three key results needs a place to raise that, and someone with the authority to reprioritise. Without a fortnightly forum that can make those calls, the only available options are silent slippage or a quarterly surprise.

The forum matters more than the software. We have seen OKRs work well on a whiteboard and fail expensively in a purpose built platform.

Review honestly

At quarter end, score the results, then spend most of the time on two questions: what did we learn, and what will we do differently next quarter? A review that only produces a percentage is an audit. REFLECT exists to make it a learning cycle.

Organisations that get through the second quarter intact are almost never the ones with the best tooling. They are the ones whose executives kept turning up to the forum and kept making the trade off calls in the room.