Changing or killing a goal mid-cycle
Changing or killing a goal mid-cycle is a governed decision, not an improvisation: named triggers that open the question, a ladder of response from rescope to stop, one named decider, and the reasons written down and kept.
The obvious bit
Two failures sit either side of this, and most companies pick one and stay there.
One is rigidity: everyone knows by week five that the goal is wrong, and it runs to week thirteen anyway, because stopping is not a thing that happens here. The other is churn: goals change whenever someone senior has a new idea, and within two cycles nobody believes any goal is real.
Both are the same missing thing. Nobody decided in advance what would justify a change.
What opens the question
Four triggers, named before the cycle starts. Anything else is a preference, not a trigger.
The belief was disproved. The bet rested on something specific, and the evidence came back against it. This is the good case, and it should feel like a result rather than a failure.
The resource went. The capacity the goal was set with has been taken for something else. The goal did not fail; it was defunded, and pretending otherwise teaches everyone that stated capacity means nothing.
The world moved. A competitor, a regulation, a customer loss that changes what matters.
A dependency failed. Something the goal was standing on did not arrive.
Notice what is not on the list: it is going badly, and someone changed their mind. Difficulty is not a trigger, and neither is enthusiasm.
The ladder of response
Stopping is the last rung, not the first. In order:
Rescope. The outcome still matters, the target was wrong. Adjust the target and say so openly.
Re-resource. The goal is right and starved. Give it what it needs or admit you will not.
Re-time. The outcome needs longer than the cycle. That is allowed, and it is the whole point of letting a goal take as long as the outcome takes.
Stop. The bet is dead. Close it, write the reasons, and let the hours flow to the next most valuable goal.
Who decides, and what gets kept
One named person per goal, agreed at the start. Not a committee, and not whoever happens to raise it. Vague decision rights are why stopping does not happen: everyone can see it should, and nobody owns saying so.
And the record matters as much as the decision. Which trigger fired, what was tried, what we now believe. Without that you have not stopped a goal, you have deleted one, and someone will propose it again inside two years.
Our opinion
How you treat the first stop sets the pattern for every one after it. Call a stop with reasons a decision, then treat the person who made that call even slightly differently, and the policy has already lost to what people watched happen.
So the first one is worth doing loudly and well. It is the cheapest culture change available to a leadership team, and it costs nothing but nerve.
One line to keep: a goal should change when the evidence changes and at no other time, and the difference between those is written down in advance.
Is stopping a goal early a failure? +
No. A goal stopped for reasons you can articulate and keep is a decision. It frees the capacity for the next thing and leaves the reasoning behind so nobody repeats the attempt blind.
What stops this becoming goal-of-the-week chaos? +
Named triggers and one named decider. If the only thing that opens the question is a trigger agreed before the cycle started, a new idea mid-cycle joins the queue for next time rather than replacing the current goal.
Who should decide? +
One person per goal, agreed at the outset. Committees do not stop things, because nobody in a committee owns the sentence.
From the ZOKRI OKR Handbook, the methodology we install and maintain. Written by Matt Roberts.
A UK-based strategy and OKR consultant and two-time SaaS founder with a venture-backed exit, Matt turns strategy into execution for teams scaling from tens to thousands. He co-founded ZOKRI in 2018, having previously co-founded Linkdex, a venture-backed enterprise SaaS platform he led to a trade sale. He writes the methodology behind these notes.
We install the triggers, the ladder and the decision rights, then coach the first real stop, because that is the one everyone learns from.