The Monday Morning Test: Why Some OKRs Are Only Ceremony
Photo: Sebastiaan ter Burg from Utrecht, The Netherlands, CC BY 2.0, via Wikimedia Commons
UK organisations have become proficient at the visible routines of OKRs. There are slides, colour-coded trackers, weekly check-ins and quarterly reviews. None of this is inherently wrong. The difficulty is that ritual can imitate management. In late 2026, when many teams are being asked to deliver more with tighter budgets, the distinction matters. An OKR that does not alter decisions is not a goal-setting system; it is a performance of goal-setting.
Seven signs of OKR theatre
-
The owner is named but not empowered. If the owner cannot move budget, people or deadlines, the role is symbolic. Ownership without decision rights is a caption, not accountability.
-
Key results measure activity. Workshops held, updates published and actions completed can be useful operational metrics, but they do not show whether the intended outcome is closer. Activity is easy to report; progress is harder to prove.
-
Check-ins produce colours but not choices. A review that ends with green, amber and red but no change to priorities is a reporting meeting. It may be well attended, but it is not managing the work.
-
Nothing is stopped. If a new objective is added without an existing commitment being paused, reduced or removed, the organisation is not prioritising; it is accumulating.
-
The dashboard is more developed than the decisions. If more time is spent formatting the tracker than deciding what to do differently, the tracker has become the product.
-
Compliance is rewarded. Teams are praised for completing templates on time rather than for evidence that an objective changed a customer outcome or removed an internal constraint.
-
The objective cannot survive pressure. If the first difficult quarter causes an objective to disappear without a decision, it was decoration rather than priority.
The Monday morning test
The test is deliberately blunt. For each objective, ask three questions in the existing weekly meeting. First, what will be different on Monday morning because of this objective? Second, which existing commitment will be delayed, stopped or reduced to make room for it? Third, who can say no to work that conflicts with it?
A real objective should produce a specific answer to at least one of these questions. If the answers are vague, the objective is probably ceremonial. The test is not a scorecard to be completed for its own sake. It is a prompt for a decision. If the team cannot name a decision the objective has forced since the last review, that absence is the finding.
Why theatre persists
Theatre persists because it is safer than trade-offs. A polished review creates an impression of control without requiring anyone to cancel a project or disappoint a stakeholder. OKRs can also become reputational: an objective on a leadership slide may be easier to maintain than a difficult conversation about capacity. Tooling can reinforce the pattern by making tracking feel like progress.
The answer is not to abandon OKRs. It is to make them decision-bearing. A smaller set of objectives with clear owners and visible trade-offs is more useful than a comprehensive set that changes nothing.
Examples from UK organisations
In a UK scale-up, a weekly OKR stand-up had become a status forum. The sales objective was reported as on track because activity was high, while the support team had received no additional capacity for the new enterprise customers the objective was meant to win. The Monday morning test exposed the gap: no existing commitment had been stopped. The leadership team paused a lower-priority project and moved two people into onboarding.
In a public-sector transformation team, a dashboard on resident response times was reviewed monthly but had not changed service design. Applying the test led to a revised triage process and the removal of a weekly report that consumed manager time. In both cases, the value came from a decision, not a better slide.
A modest standard
An OKR is real when it changes at least one of the following: the allocation of time, money or people; the sequence of work; the definition of done; or the point at which an issue is escalated. This is a modest standard, but many objectives fail it.
The test should be used in existing forums, not in a new meeting. Five minutes per objective is enough to ask whether the goal is shaping this week's work. If it is not, the team has two honest options: change the objective so that it does, or retire it.
In 2026, UK teams do not need more OKR ceremony. They need goals that survive contact with Monday morning. The test is uncomfortable because it exposes the difference between activity and progress. That is precisely why it is useful.
