Mid Year Review

Most advice about a mid year review is too soft. It treats the process like a better conversation, a nicer feedback loop, or a compliance ritual with a few goals attached.

That's why so many reviews fail.

A mid year review should be one of the toughest management forums in your operating calendar. It should force decisions. It should expose where strategy has drifted, where ownership is fuzzy, and where teams are staying busy instead of delivering what matters. If your review ends with vague encouragement and no hard trade-offs, you didn't run a review. You ran a discussion.

In the UK, the mid-year review is commonly used as a six-month checkpoint to compare actual performance against objectives and reset priorities for the next six months, as outlined in Indeed UK's guidance on mid-year reviews. That's useful, but most organisations still waste the moment. They talk about performance without fixing the system that drives performance.

The problem usually isn't honesty. It's governance. It's weak follow-through. It's leaders refusing to stop work that no longer matters. It's managers accepting “amber” updates that hide delivery failure. It's OKRs being reviewed as paperwork instead of used as a mechanism for execution.

If that sounds familiar, your mid year review doesn't need polish. It needs a reset.

Why Your Mid Year Review Needs a Reset

Most organisations make the same mistake. They assume the mid year review is mainly about feedback.

It isn't.

Feedback matters, but it's not the centre of the exercise. The centre is execution control. The meeting should tell you whether your plan still makes sense, whether teams can deliver it, and whether your leaders are making the trade-offs required to hit second-half priorities.

The real failure isn't the meeting

The main failure mode is not the conversation itself but a weak operating system. Many guides focus on feedback, but rarely answer how to use a mid-year review to expose execution gaps and stop OKRs becoming a box-ticking exercise. That matters even more in a tighter labour market, with the ONS reporting a 4.2% unemployment rate in the March to May 2025 period in the UK, which raises the cost of misalignment and weak follow-through, as noted in this midyear advancement review discussion.

When talent is expensive and capacity is tight, bad prioritisation hurts twice. You waste effort on work that shouldn't continue. Then you ask the same people to absorb the consequences.

Practical rule: If your mid year review doesn't result in changed priorities, clarified ownership, or stopped work, it's probably theatre.

Leaders confuse activity with control. They collect updates. They ask how people are feeling. They note blockers. Then they leave the room without fixing role ambiguity, resource conflicts, or impossible target stacks.

What broken reviews look like in practice

You can usually spot a failing process fast:

• Priorities stay crowded: Teams leave with the same overloaded roadmap they had before the review.
• Accountability stays vague: Nobody can say who owns the recovery plan for a slipping objective.
• OKRs stay cosmetic: Objectives sound ambitious, but key results don't drive decisions.
• Managers stay reactive: Problems are noticed late because nobody challenged the signals early enough.

A lot of this sits behind the issues covered in why OKRs fail. The pattern is familiar. Leaders write goals. Teams inherit them. Reviews happen. Nothing changes.

That's not a review problem. That's a management problem.

Stop confusing healthy performance with constant pressure

There's another trap here. Some leaders think a hard-edged review means more pressure, more stretch, more output. Usually it means the opposite. It means removing noise, making fewer priorities explicit, and giving teams a realistic path to deliver. That's why Firacard's take on productivity is worth reading. It's a useful reminder that relentless busyness is not the same as meaningful progress.

A good mid year review doesn't ask, “How do we get everyone to push harder?”

It asks, “What are we doing that we should stop, what must improve, and who is accountable for making that happen?”

The Pre-Work That Drives Real Insight

A mid year review succeeds or fails in the preparation.

If leaders walk in with loose opinions, stale dashboards, and no clear recommendation, the session turns into theatre. People defend effort, explain away missed targets, and hide behind activity. You leave with better commentary and the same execution problems.

The fix is simple. Treat pre-work as governance, not admin. The goal is to enter the room with enough evidence to make decisions on priorities, ownership, resourcing, and trade-offs.

Build a decision pack, not a presentation

Your prep material should force clarity. It should show what is working, what is slipping, what is blocked, and what decision is required. Start with a practical OKR checklist for review readiness, then build a short pack for each team or function.

Each pack should include:

• Current OKR status: What is on track, at risk, off track, or no longer relevant.
• Evidence of progress: Measurable output and outcome evidence. Cut narrative-only reporting.
• Dependency risks: The teams, approvals, systems, or leadership decisions blocking delivery.
• Capacity constraints: Overloaded roles, split focus, hiring gaps, or skill shortfalls.
• Priority conflicts: Competing asks from senior stakeholders that force the team into impossible trade-offs.
• Manager recommendation: A written view on what should continue, change, or stop in H2.

Require that last item.

A manager who arrives without a recommendation is not ready for a review. The meeting needs judgement, not neutrality.

Ask questions that expose operating problems

Weak pre-read questions produce weak reviews. “What went well?” gets polished summaries. It does not expose misalignment, weak ownership, or a plan that broke months ago.

Use questions like these instead:

1. Which objectives still matter enough to defend with time, budget, and leadership attention?
2. Which key result looks healthy in reporting but has a weak delivery path?
3. Where is progress blocked by another team, a missing decision, or an unresolved dependency?
4. What work is still running only because nobody has explicitly stopped it?
5. What changed since goal setting that should force a reset for the second half?

These questions do two things. They surface execution risk early. They also show whether the manager is managing the system or just reporting from it.

The quality of a mid year review is set by the quality of the unresolved questions brought into the room.

If the pre-work only proves effort, you will miss the actual issue. The review has to show where plans are outdated, where targets were unrealistic, and where accountability has gone soft.

Separate evidence from performance theatre

Keep the pre-read short. A few pages per team is enough if the content is sharp. Long decks usually hide weak thinking.

A useful pack puts the operating picture in plain view:

Watch for watermelon reporting. Green on the outside. Red underneath.

If a team says an objective is healthy but cannot show movement, ownership, and a credible path through blockers, classify it as a risk. Do not reward confidence without proof. That is how weak governance survives until Q4.

Running the Review A Timed Facilitation Agenda

A good mid year review isn't an open discussion. It's a facilitated decision forum.

That means time-boxing matters. So does sequence. Don't start with feelings and drift into metrics later. Start with evidence, diagnose the gap, then force choices.

A practical benchmark comes from Robert Walters, which recommends 45 to 60 minutes per team member so there's enough space for performance reflection, feedback, wellbeing, and next-step planning, as outlined in Robert Walters' guide to conducting a mid-year performance review. That tells you one thing clearly. This is not a quick check-in.

If you need a repeatable structure for this cadence, The OKR Hub's OKR review meeting guide outlines how teams can run review forums around progress, analysis, and decisions.

Use a firm 60-minute structure

Here's the format I'd use for a single-team review.

Facilitate for truth, not politeness

The chair matters. If the facilitator can't challenge ambiguity, the meeting will slide into passive reporting.

Use direct prompts:

• On progress: What has moved since the last cycle?
• On relevance: If you were setting this objective today, would you still choose it?
• On blockers: Is this a capability issue, a priority issue, or a governance issue?
• On ownership: Who has to act next, and by when?
• On trade-offs: What work will be deprioritised to make this achievable?

Notice what's missing. There's no invitation for endless explanation. Teams often use detail to avoid accountability. Cut through it.

Don't ask teams to “share updates”. Ask them to defend the current use of time, budget, and leadership attention.

Keep the room under control

Three meeting behaviours wreck reviews.

First, leaders rescue underperforming objectives with optimism. Second, stakeholders smuggle in new priorities without dropping old ones. Third, managers let weak evidence pass because the conversation feels uncomfortable.

Counter that with explicit rules:

• No new priority without a trade-off
• No status colour without evidence
• No unresolved owner for a major action
• No meeting close until decisions are written down

If needed, park coaching topics for separate follow-up. A mid year review should not turn into a general development conversation. There's a place for that. This isn't it.

End with decision language

Close using verbs that create movement:

• Continue
• Pivot
• Stop
• Escalate
• Reassign
• Simplify

Avoid soft closing phrases like “monitor”, “keep an eye on”, or “revisit later” unless they come with an owner and a date. Those phrases usually mean nobody decided anything.

Making Decisions Pivot Continue or Stop

Most mid year reviews fail at the moment that matters most. Leaders see a slipping objective, everyone agrees it's a problem, then nobody wants to make the hard call.

So the goal survives. The scope stays fuzzy. The team keeps grinding. Six months later, the same issue returns with a larger bill attached.

That's poor leadership. Reviews should force a choice.

If your teams already score progress formally, use that discipline to support this decision through a consistent OKR scoring approach. But don't confuse scoring with deciding. The score is input. The decision is the point.

Continue means recommit, not drift

Choose continue when the objective still matters, the path is still credible, and the issue is mainly execution discipline.

A continue decision should answer three questions:

If those conditions hold, continue. But don't continue passively. Recommit resources. Tighten the recovery path. Raise review frequency if needed.

Pivot means change the route, not the ambition

Choose pivot when the objective still matters but your current approach is wrong.

Common reasons include:

• The key results measure the wrong thing.
• A dependency has changed and the original plan no longer works.
• The team has learned enough to see a better route.
• External conditions have shifted and the current method is now inefficient.

A pivot is often the best answer when leaders are honest enough to admit the plan was incomplete. It keeps strategic intent while changing the method.

A pivot is not a softer version of failure. It's what competent leadership looks like when the facts change.

The danger is fake pivots. That's when teams relabel the same work and call it adjustment. Don't allow that. A real pivot changes scope, measures, sequencing, or ownership.

Stop means free capacity on purpose

Choose stop when the objective is no longer worth the effort. Not because the team is tired. Because the work no longer earns its place.

Stop when:

• The goal is obsolete.
• The value is too low relative to the effort.
• Another priority now matters more.
• The route to impact is no longer credible.
• The organisation is only continuing because nobody wants to admit sunk cost.

Leaders often avoid this because stopping feels like failure. It isn't. Carrying dead priorities is failure. It confuses teams, absorbs scarce capacity, and punishes the work that matters.

Force the trade-off into the room

When an OKR is under pressure, ask these questions in order:

1. Would we approve this objective today?
2. If yes, is the current approach still the right one?
3. If yes, what must change in execution?
4. If not, what capacity do we recover by stopping?
5. Who will communicate the decision to affected teams?

That sequence prevents drift. It forces reality before emotion.

Common Pitfalls and How to Avoid Them

The visible problem in a mid year review is usually bad reporting. The actual problem is often weaker than that. It's poor management judgement.

That's why templates and forms rarely save the process. A critical issue is manager capability. CIPD's 2024 Good Work Index found that only 36% of UK managers had received management training in the last year, and 43% of employees said their manager lacked the skills to manage them effectively, as cited in this mid-year performance review guide referencing the CIPD findings. If managers can't diagnose performance, challenge vague OKRs, or make trade-offs, your review quality will be patchy at best.

A lot of the warning signs show up in the same places as these common OKR mistakes. The review makes them impossible to ignore.

Pitfall one watermelon reporting

This is the classic pattern. A team reports green because nobody wants escalation. Underneath, deadlines are slipping, dependencies are unresolved, and confidence is weak.

Fix it by changing the evidence standard. Don't accept colour labels without proof of movement, ownership, and next-step clarity.

Pitfall two adding work without stopping work

Executives love this mistake. Something urgent appears, so they add it to the stack. But they never remove anything.

The result is predictable. Teams miss more goals, quality drops, and managers start hiding trade-offs instead of surfacing them. The rule should be blunt. Every new priority requires an explicit deprioritisation decision.

Pitfall three turning the review into therapy

Wellbeing matters. Motivation matters. But if the review becomes a long emotional processing session, the execution issue survives untouched.

Use separate forums for coaching, support, and development where needed. Keep the mid year review focused on delivery, decisions, and operating friction.

Weak reviews rarely fail because people lacked ideas. They fail because nobody converted those ideas into accountable action.

Pitfall four tolerating vague ownership

“Marketing and product will align offline” is not an action. It's avoidance.

Every significant issue needs one named owner. Not two. Not a committee. One person who carries the next move and reports back.

Pitfall five protecting bad goals for political reasons

Some OKRs survive because senior leaders sponsored them. Everyone can see the goal has lost value, but nobody wants the argument.

Review discipline matters most. The meeting has to privilege evidence over sponsorship. If a goal shouldn't continue, stop it. Seniority doesn't rescue weak priorities.

From Review to Rhythm Turning Insights into Action

A mid year review creates value only if it changes how the organisation runs next week.

Many teams falter at this point. They have the meeting, agree on the problems, and leave with good intentions. However, the old rhythm then takes over, and nothing sticks.

Guidance on mid-year reviews is clear about the danger here. The main failure mode is weak follow-through. Reviews need to become a measurable action plan with specific objectives, owners, and timelines, and recommended post-review actions include documenting updated goals and scheduling monthly check-ins, as described in Paycor's guidance on mid-year review follow-through.

Turn decisions into operating rhythm

The output of the review should fit on one page. Not because the issues are simple, but because execution hates clutter.

Your action summary should include:

• Decision made: Continue, pivot, stop, escalate, or reassign.
• Reason for decision: One short explanation tied to strategy or delivery reality.
• Named owner: One person accountable for next steps.
• Timeline: When the next checkpoint happens.
• Success evidence: What output or outcome will show that the action worked.

If that summary doesn't exist, the review will fade into memory.

Cascade into weekly and monthly forums

A review decision is only real when it shows up in the regular management rhythm.

That means updating:

This is the bridge most organisations miss. They treat the mid year review like a standalone event. It isn't. It's a reset point for how leadership attention gets used.

Communicate the trade-offs clearly

Teams can handle difficult decisions. What they can't handle is confusion.

Tell people what changed, why it changed, and what won't be pursued now. If you've stopped a piece of work, say so plainly. If you've pivoted an objective, show what is different. If you've doubled down on a goal, explain the implications for time and focus elsewhere.

Avoid corporate euphemisms. They breed mistrust.

The fastest way to kill momentum after a review is to leave teams guessing which decisions were real.

Build a follow-through habit

One review won't fix a weak operating system. Repetition will.

That means leaders need to inspect execution more often than they rewrite strategy. Monthly check-ins on review actions are not administrative overhead. They are how you stop a hard conversation from becoming another forgotten document.

If your organisation struggles to make that link between strategy, review, and delivery, the issue probably sits deeper than one meeting. It usually means your OKR system, governance cadence, or leadership habits need work.

If your mid year review keeps producing discussion instead of decisions, it may be time to look at the system behind it. I help leadership teams strengthen the link between strategy, governance, and day-to-day execution through practical OKR implementation, review rhythms, and capability building. Start a conversation →