Here is a real objective, lightly disguised, from a retailer's Enterprise Delivery Office: Deliver on the prioritised 2026 store and digital initiatives. Beneath it sat five key activities, all some version of "provide coordinated support" and "strengthen governance." Beneath those, four key results: milestones met on the priority list, every initiative resourced, delivery processes more consistent, leadership better sighted on risk. It passed every quality check the template offered. It cascaded cleanly to three teams. And it is not an objective. It is a task list with a headline.
That's the uncomfortable part. The task list didn't look like a task list. It had the shape of an OKR, the ceremony of one, the tracker row and the quarterly grade. It felt governed. Everything meant to make an OKR rigorous was present, which is exactly why nobody in the room could name what was wrong. When a delivery mandate wears the costume of strategy, the tell isn't sloppiness. It's that the whole thing measures beautifully and changes nothing.
You can spot one from three tells, and once you can spot it, you can rescue it.
The three tells of a delivery mandate
The objective is a verb of delivery. OKRs are an instrument for changing the business, not for running it. "Deliver on the prioritised initiatives" is a mandate to keep it running. The word doing the work is deliver, and the priorities arrived as a list. Someone, somewhere, already chose which initiatives mattered and on what basis, and that choice is the strategy. The OKR imported the output of the choice and skipped the making of it. An objective that opens with "deliver on" is usually a container for a decision made elsewhere, or never made at all. In Design4 terms, it names a benefit to pursue but says nothing about how to win it, the strategic choice that sits between purpose and operations.
The middle answers "how" with activity. Ask the delivery office how it will hit the objective and you get the key activities: coordinate, align, govern, support. Those are things to do. They are not a choice about how to win, and they are not a capability the office has to build. The OKR pillar calls this the misfilled middle. A two-part framework has no vocabulary for strategic choice or capability, so when a team feels the gap they reach for the only thing they can name, tasks. A list of activities appears exactly where the strategy should be, and because it's busy and concrete, it reads as substance.
The results measure the machine, not the world. The key results read: milestones met, every initiative resourced, processes more consistent, leadership better sighted. Now ask the one question that list can't survive. Is any shopper, any store, any customer better off? Not one result describes a changed outcome in the world the retailer serves. They measure the health of the delivery office. That is the Deliver question, are we getting it done well?, quietly standing in for the Discover question, are we getting the benefit? Done becomes worth-doing by sleight of hand.
The rescue
Here's how you put back the middle the OKR skipped.
First: surface the choice the priority list assumed. The delivery office doesn't set retail strategy, true. But its priority list encodes one, whether or not anyone wrote it down. Pull it into the open. In this case the 2026 bet was to win the omnichannel shopper by making click and collect the default way to buy, rather than a niche option bolted onto the website. That's the how-to-win the list took for granted. Name it, and the objective stops being "deliver the list" and becomes "make the bet real."
Second: name the capability the bet requires. A choice with no capability behind it is a slogan. Click and collect only works if stock showing as available online is actually on the shelf when the shopper arrives to collect it. So the capability the office has to build is integrated inventory visibility across web and store. That is the work whose absence would make every milestone meaningless, and it is precisely what "provide coordinated support" never had to name.
Now rewrite it, same office and same quarter:
Objective. Make click and collect the shopper's default, because it wins the omnichannel customer we've chosen to compete for.
Key results. Click-and-collect share of eligible online orders rises from 12% to 30%. Stock shown as available online is on the shelf at collection 98% of the time, from an unmeasured baseline today. Repeat-purchase rate among click-and-collect shoppers climbs six points against store-only shoppers.
And the five key activities? They don't vanish. They demote. Coordinate, align, govern, support: that's the work plan beneath the objective, where a work plan belongs. The rescue isn't adding effort. It's moving the activities out of the objective and putting the choice and the capability back in.
What changes when you do it
Two things change. The office loses the ability to report success while the bet quietly fails, because its results now move only when the shopper's behaviour moves. Green stops being free.
And the cascade changes character. Under a delivery mandate, each team below inherits a smaller slice of the same instruction, "deliver the list," chopped thinner at every level until an individual is grading themselves on a task. That's decomposition, not strategy. Under the rescued objective, teams inherit a share of the capability to build and the outcome to shift, which forces each level to make its own choice about how to contribute rather than copy the box above it. The difference between those two cascades is the difference between an organisation that is busy and one that is winning.
A task list tells you what everyone is occupied with. An objective tells you what you've chosen to make true, and how you'll know it worked. Only one of them is worth grading.
This is the OKR pillar's Missing Middle seen up close: an objective that skipped the strategic choice and the capability, and how to put them back. The same failure wears other costumes in the phase every management system skips and outputs are not outcomes. The Closing the Strategy-Execution Gap course teaches the full chain from benefit to choice to capability to operation.