The Death of Annual Objectives
The Death of Annual Objectives and the Deeper Problem Underneath
Why fixing the calendar isn’t enough, and what actually displaces performance
Annual objectives are dying, and the strange part is how quietly. Leaders feel the drag. Teams sense the absurdity. Almost everyone privately knows the ritual has stopped working, and yet it continues: the January planning theatre, the quarterly check-ins, the year-end autopsies of commitments that stopped mattering by March.
Organisations keep the ritual not because it works but because it’s familiar, and because it offers the feeling of control in an environment where control evaporated long ago. The annual objective was built for a world that no longer exists: One of predictability and slow change, where a twelve-month commitment was a reasonable bet. Today, that same commitment is a fiction, complete with templates and dashboards to make it feel rigorous.
But here’s the part most critiques miss. Killing the annual cycle fixes the obvious failure and leaves a deeper one completely intact. There are two distinct things wrong with how organisations set goals, and almost everyone treating the first never notices the second.
The first failure: Fixity
The visible problem is that a fixed annual objective assumes the environment will hold still long enough for the plan to stay valid. It won’t. Modern organisations sit inside dynamic systems: Interdependent, fast-moving, reshaped by forces that don’t wait for the planning calendar. Conditions move in days. Customer expectations shift faster than governance can follow. Strategy itself has become less a fixed direction than a hypothesis under constant revision.
Set a rigid annual scaffold on a system that reconfigures itself continuously, and the scaffold doesn’t organise the system; it just drifts further out of step with it every week. Leaders end up defending plans that no longer describe reality. The plan becomes an artefact: a faithful record of what the organisation believed at one fixed moment, preserved past the point where the belief was true.
The fix for this one is straightforward, at least in principle: stop treating the calendar as a strategic instrument.
Let goals re-form as conditions change. Hold them quarterly, monthly, continuously: Anchored to outcomes, refreshed against reality.
Fixity is a cadence problem, and cadence problems have cadence solutions.
And this is exactly where most “modern performance” thinking stops: Declaring victory the moment the annual plan is replaced with something live. But a live target has its own disease, and refreshing it more often doesn’t cure it. It just spreads it across the year.
The second failure: Substitution
Here is the harder truth. The moment a measure becomes a target, people begin serving the measure instead of the thing it was meant to represent. The number becomes the mission. The proxy displaces the purpose. And this happens whether the target is annual or live, fixed or continuously refreshed, activity-based or outcome-based, because the mechanism has nothing to do with cadence and everything to do with what a target does to attention.
Attach effort to customer-satisfaction scores, and you get surveys engineered to score well. Attach it to a retention number, and you get the relationships that were easy to keep, not the ones that mattered.
Attach effort to any outcome metric, however thoughtfully chosen, and people optimise the metric, including the parts of it that have drifted away from the actual stakeholder need it was supposed to track.
The map gets served; the territory gets abandoned. Refreshing the map every quarter changes nothing, because the problem was never that the map was stale. The problem is that people are navigating by the map instead of looking at the ground.
This is why organisations that “fix” their goal-setting by going continuous so often feel busier, more measured, more agile, and still don’t satisfy the people they exist to serve. They solved fixity and never touched substitution. The team hits its live, outcome-based, quarterly-updated targets, and the stakeholder is still poorly served, because the targets became the object of work, and the stakeholder became an abstraction behind them.
Why substitution happens and why it isn’t a discipline problem
It’s tempting to read all this as people gaming the system, and to reach for tighter metrics or better-chosen ones. That’s the wrong diagnosis.
People substitute the target for the purpose because the architecture gives them no other choice about what to be accountable to.
When a person’s decision rights, their consequences, and their line of sight all connect them to a number rather than to a stakeholder, the number is the only real thing in their world. The stakeholder is someone else’s concern, or everyone’s, which means no one’s. In that structure, serving the target instead of the purpose isn’t a failure of integrity. It’s an accurate reading of what the system actually holds them accountable for.
This points to the deeper issue, the one that survives every change of cadence: a target, be it KPI, CSF, or OKR, displaces purpose whenever the architecture leaves purpose otherwise unaccountable.
The proxy always becomes the mission when there is nothing more real behind it that the person answers to. Remove that vacuum and the target loses its gravitational pull, because there’s now something it has to serve rather than replace.
The actual cure: accountable connection, not better targets
So the answer to gamed targets isn’t more targets, smarter targets, or live targets.
It’s an architecture that connects the person directly to the stakeholder outcome that gives them ownership of the relationship, line of sight to whether the stakeholder is genuinely well served, and a real consequence when they aren’t.
When that connection exists, the metric reverts to what it was always supposed to be: an instrument that informs judgement, not a mission that replaces it.
People stop chasing the proxy because they’re now accountable to the thing the proxy was only ever pointing at.
This is the difference between measuring performance and designing for it. Measurement asks: Did we hit the number? Design asks: Is the person who owns this outcome structurally connected to the stakeholder it’s meant to serve, and do they bear the consequence if that outcome fails?
Get that connection right, and you don’t really need the target because the outcome takes care of itself. The metric becomes a useful readout rather than the thing everyone is secretly optimising against the spirit of.
Get it wrong, and no goal-setting methodology saves you. You can run annual objectives, quarterly OKRs, continuous living goals, or no formal targets at all, but if the architecture leaves the stakeholder outcome unaccountable, people will serve whatever proxy is nearest to hand and call it performance.
Why it matters now
Retiring the annual ritual is worth doing.
Fixity is real, and a plan anchored to a frozen yearly snapshot will keep lagging the world it’s supposed to navigate. The provocation still holds: if your goals can survive a full year without a single change, your business is either in a coma, lying to itself, or operating in a market no one cares about.
A plan that never needs revising isn’t evidence of discipline – it’s evidence that nothing real reached it.
But don’t mistake the cadence fix for the whole job.
Going continuous solves the failure you can see and leaves the one that actually erodes stakeholder satisfaction untouched.
The organisations that genuinely perform aren’t the ones with the most up-to-date targets.
They’re the ones that built an architecture where the people doing the work are connected – by ownership, by consequence, by direct line of sight – to the stakeholders the work exists to serve.
In that architecture, the target stops being the mission, because there’s finally something more real behind it.
And that, not a better planning cadence, is where performance actually comes from.