Every manager who has run more than one goal-setting cycle eventually hits this question: the business has changed since the goal was set, and now the goal doesn't quite make sense anymore. Do you adjust it, or hold the line? Both instincts are defensible, and getting this wrong in either direction has real costs.
This question comes up more often than most teams expect, and it rarely has a clean textbook answer, because the honest truth is that both flexibility and consistency are legitimate values in goal-setting, and they sometimes pull in opposite directions. The goal of this article isn't to argue for one extreme or the other - it's to give managers a practical way to tell, case by case, which value should win out.
The Case for Adjusting
Goals are set with the information available at the time, and sometimes that information changes meaningfully before the cycle ends. Google's OKR guidance treats OKRs as a living planning tool rather than a fixed contract, precisely because a goal built around launching in a market that a strategic pivot has since deprioritised isn't just hard to hit - it's actively misleading if left unchanged, because hitting or missing it no longer tells you anything useful about the employee's actual contribution. Refusing to adjust in cases like this isn't discipline, it's just tracking the wrong thing on principle.
The Case Against Adjusting
The opposite risk is real too: a team that adjusts goals every time progress looks difficult isn't practicing flexibility, it's avoiding the discomfort of an honest miss. If "this is harder than expected" becomes grounds for lowering the target, goals stop meaning anything, and the scoring exercise becomes theatre rather than a genuine signal of progress.
A pattern of frequent adjustment, especially adjustments that only ever make goals easier, is usually a sign of a deeper goal-setting discipline problem, not a sign of appropriate responsiveness.
A Simple Test: Has the Underlying Business Context Changed?
The cleanest way to tell a legitimate adjustment from an excuse is to ask whether something outside the employee's control and outside normal execution difficulty has genuinely changed - a strategic pivot, a market shift, a dependency that was cancelled, a merger or reorg. If the honest answer is "no, it's just turning out to be harder than we thought," that's usually not grounds for adjustment. Difficulty was always part of the deal; a stretch goal is supposed to be hard.
How to Adjust Without Undermining the Process
Document why, not just what
When a goal is adjusted, record the reason alongside the change - "target reduced from X to Y because the Q2 pivot deprioritised this market" - rather than quietly editing the number. This protects the integrity of the record and makes clear the change wasn't arbitrary or a way of avoiding a miss.
Get a second opinion before adjusting
A manager unilaterally softening their own team's goals, without any check from HR or a peer manager, creates an obvious incentive problem. A brief conversation with someone outside the immediate reporting line - even just a quick gut-check - adds a useful layer of accountability before a target changes.
Set a cutoff point
Adjusting a goal in week two of a twelve-week cycle is very different from adjusting it in week eleven. Many teams set an informal rule - adjustments are fine through roughly the midpoint of a cycle, but past that point, a goal is either hit, missed, or explicitly cancelled rather than quietly changed near the finish line.
Don't let adjustment become a habit
One adjusted goal in a cycle, for a clear and documented reason, is normal. If half a team's goals need adjusting every single cycle, the actual problem is upstream - goals are being set without enough information, or without enough buffer for known volatility - and that's worth fixing directly rather than normalising constant mid-cycle changes.
How Employees Perceive Mid-Cycle Changes
It's worth remembering that a goal adjustment isn't purely a process decision - it's also a signal employees read closely, whether or not that's intended. An adjustment that's clearly justified and transparently communicated tends to build trust; it shows the company is responsive to real change rather than rigid for its own sake.
An adjustment that feels arbitrary, or that only ever seems to happen for certain people or certain teams, does the opposite - it quietly teaches employees that goals are negotiable if you push hard enough, which undermines the seriousness of the whole goal-setting exercise for everyone watching, not just the person whose goal changed.
This is one more reason documentation matters as much as the decision itself. An adjustment that's visible, dated, and explained, even briefly, reads very differently to the rest of the team than one that simply shows up as a changed number with no context attached.
Adjusting Company-Level Goals vs Individual Goals
The considerations above apply somewhat differently depending on the level of the goal. Company-level objectives changing mid-cycle is a bigger, more visible decision - it should involve leadership broadly and be communicated clearly to the whole company, since individual goals across many teams likely ladder up to it. An individual's personal goal changing is a smaller, more localised decision, but it still deserves the same basic discipline: a documented reason and, ideally, a second opinion, even if the conversation involved is shorter and less formal than a company-wide strategy shift would require.
Where Talstack Fits
Talstack's Goals module keeps a visible history when a goal is adjusted, rather than silently overwriting the original target, so the reason for a change stays attached to the record for anyone reviewing it later - a manager, HR, or the employee themselves. Combined with 360 Feedback and Talstack's HRIS, that history makes it easier to distinguish a legitimately adjusted goal from a pattern of goals quietly softened to avoid a difficult conversation.
What Fast-Growing African SMEs Should Watch For Specifically
Companies growing quickly - a funding round, a new market entry, rapid hiring - face a particular version of this problem: the pace of genuine business change is high enough that mid-cycle adjustment requests will come up more often than they would at a stable, mature company.
This isn't necessarily a red flag on its own, but it does mean the discipline around documenting and validating adjustments matters more, not less, in a fast-growth context. Without that discipline, a genuinely dynamic business environment becomes a convenient cover for goals that quietly get renegotiated every time they look difficult, and the distinction between the two becomes impossible to reconstruct later.
A useful practice for fast-growing companies specifically is keeping a lightweight running log of company-level changes as they happen - a pivot, a new priority, a major client win or loss - separate from the goal-tracking system itself. When a goal-adjustment request comes in, that log becomes a quick, objective reference: did something on this list actually happen around the time of the request, or is the adjustment being justified by a change that isn't actually documented anywhere else.
Quick Checklist: Deciding Whether to Adjust a Goal
- Confirm something outside normal execution difficulty has actually changed
- Rule out that the request is really about difficulty, not changed circumstances
- Get a second opinion before finalising the adjustment
- Document the reason for the change, not just the new number
- Check whether you're past your team's informal cutoff point for adjustments
- Look for a pattern - is this a one-off, or does this happen every cycle
A Note on Goals Tied to External Market Conditions
Goals tied to external market performance - sales targets sensitive to currency fluctuation, growth targets affected by a competitor's aggressive pricing move, revenue goals exposed to a shift in consumer spending - deserve particular care in this framework, because African markets in particular can see meaningful macro shifts within a single quarter.
A sales target set assuming stable exchange rates, for instance, may genuinely need revisiting if a currency moves sharply enough to materially change customer purchasing behaviour mid-cycle. The same test still applies - has something genuinely external changed, versus is the goal just proving hard - but it's worth building in more headroom for market volatility when setting goals in the first place, rather than relying entirely on mid-cycle adjustment to absorb it after the fact.
Copy-Paste Script: Proposing a Mid-Cycle Goal Adjustment
Subject: Proposing an adjustment to [goal name]Hi [Manager/HR name],I want to flag that [goal] may need adjusting. Here's why:What changed: [specific business change - pivot, dependency loss, reorg, etc.]Why it affects this goal: [brief explanation]Proposed adjustment: [new target, or proposal to close out the goal early]I wanted a second opinion before making this change, since I know it's easy for adjustments to become a habit rather than a genuine response to changed circumstances. Let me know your thoughts.[Manager name]
Frequently Asked Questions
Is it ever okay to lower a goal mid-cycle?
Yes, when the underlying business context has genuinely changed - a strategic pivot, a lost dependency, a reorg - but not simply because the goal is proving harder to achieve than expected.
How do you know if a goal adjustment is legitimate or just avoiding a miss?
Ask whether something outside normal execution difficulty has actually changed. If the honest answer is no, the goal is just hard, and that's the point of a stretch goal - it shouldn't be adjusted.
Should managers be able to adjust goals on their own?
It's better practice to get a second opinion - from HR or a peer manager - before finalising a mid-cycle adjustment, to avoid the obvious incentive for a manager to quietly soften their own team's targets.
Is there a point in the cycle after which goals shouldn't be adjusted?
Many teams use the rough midpoint of the cycle as an informal cutoff - adjustments past that point tend to look more like avoiding an honest miss than responding to genuine changed circumstances.
What if most of a team's goals need adjusting every single cycle?
That's usually a sign of an upstream goal-setting problem - goals set without enough information or buffer - rather than something to solve by simply making adjustment routine.
How should a goal adjustment be documented?
Record the reason for the change alongside the new target, not just the updated number, so anyone reviewing the goal later can see it was a considered response to changed circumstances rather than a quiet edit.
Does a mid-cycle adjustment affect how the goal should be scored?
Generally, score against the adjusted target once a change is properly documented and approved, but note in the record that an adjustment occurred so the full context is visible to anyone reviewing performance later.
