Leadership Training Activities: 9 That Build OKR Execution

82% of UK managers who entered management positions had received no formal management or leadership training, according to research cited in the Chartered Management Institute's Management and UK 2030 report. That finding explains a pattern I see in most leadership rooms. Leaders can explain an OKR. Fewer can write a testable one, run an honest check-in, or challenge a peer who has missed a commitment.

Most leadership training fails because it teaches concepts, not behaviour. People leave with slides, then return to the same meetings, priorities and avoidance habits. If you're choosing a format, explore adult learning preferences, then favour practice on live work over passive content every time.

The nine leadership training activities below fix misalignment, unclear priorities, slow decisions and weak accountability. Each one uses your actual goals, not invented case studies. Each includes an objective, timing, materials and facilitation notes, so you can run it without building a course around it.

Start where execution is breaking. If goals are vague, start with writing. If goals are clear but nothing moves, start with check-ins and accountability.

1. OKR Writing Clinic Turning Vague Goals into Testable Commitments

Objective: Rewrite live objectives until each one can be judged against evidence at quarter end. Timing: 90 minutes. Materials: Draft OKRs, a visible before and after wall, markers or a shared board.

Most OKR failure starts here. Objectives read like job descriptions, such as "Improve customer experience". Key results describe activity, such as "Launch three initiatives", instead of the outcome that activity should create.

How I Run It

Each leader brings three draft objectives maximum. Before writing key results, that leader states the decision the objective will help make. If nobody can name a decision, the objective is decoration.

• Test ambition: Would hitting this materially change performance, or merely confirm business as usual?
• Reject tasks: Ask what changes for customers, revenue, risk or capacity if the work gets done.
• Name ownership: Put one accountable owner beside every key result before moving on.

Say a scale-up rewrites "Grow enterprise revenue" into a net retention outcome with a baseline, target and date. That rewrite immediately exposes whether sales or customer success owns expansion. A platform goal changes similarly when "Complete migration" becomes accounts moved, with a guardrail for churn. Sequencing gets sharper because success is now observable.

A good key result settles arguments later because the evidence standard was agreed before work started.

Keep the before and after versions visible. Leaders learn faster from the contrast than from another definition.

2. Line-of-Sight Mapping Finding the Gaps Between Company Team and Individual Goals

Misalignment often feels political. Usually it's structural. A company objective has no owner, two teams fund opposite outcomes, or local goals consume capacity without moving a company priority.

Objective: Map every company objective to supporting team objectives and individual key results. Timing: Two hours, with the map built beforehand. Materials: Current OKRs, owners, capacity assumptions and a large visual map.

Decisions the Map Must Force

Build the map before the meeting. Session time is for decisions, not data entry. Mark orphan objectives in a different colour, then require each company objective to leave with one named owner.

Say onboarding time is a company priority, but product, implementation and support each own a fragment. Nobody owns the final metric. Assigning one owner turns three updates into one accountable plan. Another common result is engineering work supporting a product priority already deprioritised by the board. Dropping it frees scarce capacity for revenue work.

• Challenge duplicates: Two teams claiming the same outcome need one owner and explicit contributors.
• Stop orphans: Work with no line to strategy must be justified as essential operations or stopped.
• Track linkage: Repeat quarterly and follow the proportion of team objectives linked to company outcomes.

In the UK Department for Education's Employer Skills Survey 2024, 34% of employers that provided training delivered management training in 2024. That limited coverage makes a shared map valuable. It teaches alignment through an operating artefact, not attendance at another course.

3. Check-In Simulation Running a Weekly OKR Review That Changes Behaviour

A weekly check-in isn't working if people read percentages aloud and leave with the same blockers. I train leaders to run a 30-minute decision meeting, using real key results and uncomfortable evidence.

Objective: Practise moving from status reporting to problem solving. Timing: 60 minutes for the simulation, including feedback. Materials: Pre-read sent 24 hours ahead, current scores, confidence ratings and a decision log.

Three Rules Inside the Room

Start with confidence and evidence, not activity completed. Name the one decision needed this week. Close every item with a next step, owner and date.

• Ban percentage-only updates: Every red or amber result needs a one-line cause and a named action.
• Protect decision time: Background belongs in the pre-read, not in a verbal tour of the dashboard.
• Count decisions: Track decisions made per check-in. Zero decisions usually means reporting has taken over.

Say a COO replaces a long monthly review with this weekly format. A hiring blocker that sat unresolved for weeks gets an owner and escalation path quickly. A product director can surface a design and engineering dependency in week two, while recovery is still cheap.

My guide to running weekly OKR check-ins that drive decisions gives the meeting structure in more detail. Have the chief executive or founder model it first. Leaders copy the behaviour they see under pressure, not the behaviour described in a launch deck.

4. Scoring Calibration Making Confidence Ratings Honest and Comparable

Quarter-end scores often reveal culture before performance. Cautious teams sandbag and finish near perfect. Overstretched teams set impossible targets, score badly every cycle and learn to ignore the process.

Objective: Create a shared standard for scoring ambition and evidence. Timing: 75 minutes. Materials: Past key results, anonymised where needed, scoring sheets and written anchors for low, middle and full achievement.

Run the Disagreement Deliberately

Leaders score the same past key results independently and in writing. Only then compare scores. The spread is the learning, because it exposes different assumptions about ambition, measurement and acceptable evidence.

• Anchor the scale: Write one-line definitions for 0.0, 0.5 and 1.0 before scoring begins.
• Avoid anchoring bias: Nobody speaks until every independent score is recorded.
• Review distributions: Look across teams for patterns, not just individual misses.

Say one function consistently finishes at the top of the scale while another finishes near the bottom on similarly difficult work. Calibration may reveal easy targets in one place and a broken measure in another. That is a system problem, not a motivation speech.

Keep OKR scores out of individual pay decisions during the first year. People won't score accurately if honesty costs money. My detailed guidance on OKR scoring without sandbagging covers the scale and common traps.

5. Pre-Mortem Workshop Stress-Testing Key Results Before the Quarter Starts

Imagine the quarter has ended and the objective failed badly. Your job is to explain why, before optimism hardens into a plan. Psychologist Gary Klein developed the pre-mortem, and I use it because people name risks more openly when failure is framed as already settled.

Objective: Surface dependencies, capacity gaps, unclear ownership and false assumptions early. Timing: 60 to 90 minutes per major objective. Materials: Draft OKRs, silent writing space and a risk log.

From Risk List to Action

Each leader writes the top three failure reasons before discussion. Group them, select the five most material risks, then convert each into a mitigation, an owner or a revised key result.

Say a revenue key result depends on a partner integration with no committed date. Add a fallback key result now, not after the miss. In a regulated setting, the hidden flaw may be a compliance approval nobody has requested. Both problems are cheap in planning and expensive in delivery.

Practical rule: A risk without an owner, trigger date or change to the key result is just commentary.

Repeat the exercise at mid-quarter. Compare predicted risks with actual blockers. That feedback improves planning judgement faster than a generic risk lecture because leaders see which assumptions they consistently underprice.

6. Forced Prioritisation Exercise Choosing Three Objectives From Twelve

Most organisations don't have a strategy problem. They've a focus problem. Twelve priorities means every team can claim alignment while pulling capacity in incompatible directions.

Objective: Force explicit trade-offs and agree a shared top three. Timing: Two hours. Materials: Real proposed objectives, expected outcomes, capacity data and a stop list.

Make the Constraint Real

Set the limit before the session. Each leader cuts the full list to three and explains the reasons. Then the group negotiates one shared ranking, with the chief executive making the final call if consensus fails.

• Name the stop: Every retained priority needs one activity that will stop or shrink to create capacity.
• Expose single champions: An objective supported by only one leader may be local preference, not company strategy.
• Reconfirm mid-quarter: Check whether the top three still deserve scarce leadership attention.

Say a growth-stage company cuts a long list to three and discovers two legacy objectives showing no measurable progress. Stopping them releases a full team. A sales and product dispute can also resolve when both leaders accept one shared objective and one owner.

Employers where more than three-quarters of managers had received people-management training were 10 percentage points more likely to rate productivity highly, in CIPD analysis of UK employers. Broad coverage matters here too. If only executives learn prioritisation, middle managers keep funding everything. My approach to prioritising with OKRs under capacity pressure goes deeper.

7. Accountability Conversation Role-Play Holding Peers to Commitments

Leaders often know a peer commitment is slipping weeks before saying it plainly. Delay feels polite. It also makes recovery harder and teaches teams that red status carries no consequence.

Objective: Practise direct, respectful challenge using real execution scenarios. Timing: 75 minutes in pairs or trios. Materials: Recent missed commitments, impact evidence and an observer checklist.

A Structure Leaders Can Use Under Pressure

State the observable facts. Name the impact on the company objective. Ask for the other person's perspective and recovery plan. Agree the next check date.

• Use a recent case: Hypothetical role-play lets leaders stay polished and vague.
• Separate fact from interpretation: "The review slipped twice" lands better than "You don't care".
• Measure follow-through: Track red results that receive a named action within 48 hours.

Say a product leader tells a peer that two delayed design reviews have put a shared result at risk. The useful outcome isn't an apology. It's a revised date, explicit owner and agreed escalation if the date slips again.

An Acas research review cited an estimated annual cost of £28.5 billion to UK employers from individual workplace conflict, reported in Acas research on managerial capability. Clear expectations won't remove conflict, but they stop avoidable ambiguity becoming personal friction. Pair this with accountability in the weekly OKR rhythm so practice meets live commitments immediately.

8. After-Action Review Learning From Each Quarter's Results Without Blame

End-of-quarter reviews often become score announcements followed by a rush into next quarter. That wastes the most useful evidence a leadership team owns. I use the After-Action Review, developed by the US Army, because it examines the system without turning learning into blame.

Objective: Explain the gap between intent and result, then change the next cycle. Timing: 90 minutes. Materials: Original OKRs, scores, decision log and one shared lessons document.

Four Questions, No Theatre

Ask what the team set out to achieve. Ask what happened, why the gap existed and what will change next quarter. Limit discussion to the three most important objectives so causes get proper depth.

• Interrogate the system: Ask what conditions made this outcome likely before discussing individual responsibility.
• Record usable lessons: Write the change, owner and forum where it will be checked.
• Reopen lessons next cycle: Start planning by testing whether last quarter's fixes happened.

Say a missed onboarding objective traces back to an unclear handoff between sales and implementation. One owner for the handoff beats exhorting both teams to communicate better. Another review may show late decisions, not weak delivery, caused repeated misses. Then the fix belongs in decision deadlines.

Research cited by UK Parliament found the top half of British manufacturing businesses ranked by structured management practices had average productivity 38% higher than the bottom half, in evidence published by Parliament. Structured review is one of those compounding practices. See my format for an OKR retrospective that changes the next quarter.

9. Quarterly Planning Sprint and Execution Rhythm Design Building the Next Cycle's OKRs and Operating Cadence

Planning drags when every decision needs another meeting. I compress it into a one or two day sprint, then design the rhythm that keeps those choices alive after the room empties.

Objective: Produce draft OKRs, owners, dates, escalation rules and a one-page operating calendar. Timing: One to two days. Materials: Pre-work sent at least five days ahead, prior scores, company priorities, capacity data and current meeting inventory.

Sequence and Fixed Outputs

Review last quarter. Confirm company priorities. Draft objectives, cascade to teams, run a pre-mortem and agree weekly check-ins, monthly deep-dives, quarterly scoring and the annual strategy refresh. Every forum needs an owner, decision rights and required inputs.

• Remove before adding: Delete at least one existing meeting before creating a new forum.
• Assign decision rights: State who decides, who advises and who gets informed.
• Book the first check-in: Put it in calendars before the sprint closes.

Say a 220-person scale-up completes planning in two days and holds its first check-in on day ten. Dependencies surface while options remain open. Another team may remove overlapping management meetings and replace them with one weekly check-in plus a monthly deep-dive, returning leadership time to delivery.

Measure time from sprint close to first working check-in. A long gap signals planning theatre. Review the rhythm after two quarters and remove any forum that doesn't produce decisions, escalations or clearer ownership.

The nine activities at a glance

Each activity trains one OKR capability you can see in the next cycle. I book the duration below, with feedback included where the timing says so. Cut the slot and you usually lose the debrief, which is where the new behaviour sticks.

From Running Activities to Changing How the Business Runs

Match the activity to the execution failure. Vague goals need the writing clinic, because the capability gap is outcome language, not motivation. Clear goals that barely move need check-in simulation and accountability practice. Repeated surprises need a pre-mortem before the quarter starts. A crowded agenda needs forced prioritisation before anyone books another session.

A UK Government rapid evidence review found management-skills programmes generally improve management practice and organisational productivity, with facilitator involvement and content adapted through training-needs analysis most consistently associated with effective design, in the UK Government rapid evidence review. I build sessions around live objectives, current dependencies and the conversations leaders have been avoiding. Generic self-study rarely creates that pressure or that feedback.

Build a 30, 60 and 90 Day Transfer System

Pick one observable behaviour after each activity. Tie it to a live OKR job: writing an outcome, running a check-in, calibrating a score, or holding a peer to a commitment. Give that behaviour a real business application, a peer or manager feedback loop and a review point inside a meeting that already exists. Judge transfer through behaviour and delivery evidence, not attendance or satisfaction.

At 30 days, check whether leaders are using the new language and meeting rules. At 60 days, inspect decision speed, overdue commitments and how fast dependencies get resolved. At 90 days, compare outcomes, confidence and score quality with the starting point. If the behaviour has not shown up in the operating rhythm, the activity did not transfer.

Coverage matters as much as content. Training only a senior cohort produces polished executives and inconsistent management below them. A peer-reviewed Journal of Management and Organization study of Help to Grow: Management found that 91% of programme completers reported improved leadership and management of their business, in Does business training make a difference?. I treat that confidence as useful, not proof. Commercial impact still needs delivery evidence.

Live team training uses two OKR simulations and the 4C's learning model of Connection, Concept, Concrete Practice and Conclusion, so teams write their first real OKRs in the room. Most sessions run over one day, in person or remotely. 82% of leadership teams say they leave facilitated sessions with clearer strategic alignment than before. That clarity only pays off if the weekly rhythm keeps the same standard after the room empties.

I help leadership teams close the gap between strategy and execution by putting these activities into the operating rhythm, through leadership training, team training, away days and hands-on coaching. If your OKRs have become a tick-box exercise, book a conversation.