Blog

All articles

OKR Review Agenda: Turn KPI Results and Recognition Into Decisions

A practical 45-minute agenda for reviewing OKRs with approved KPI results and recognition signals, and leaving with decisions, owners and dates.

Start with the decision you need to make

Most OKR reviews turn into a dashboard tour. You read status, nod, move on and repeat next period. A better agenda answers three questions: what changed, why, and what you will do differently. KPI results show what changed. Recognition insights help you ask better questions about why, including where effort, collaboration and values are showing up in daily work.

Wudd brings recognition, KPIs and OKRs together. Recognition is tagged to a Company Value, weighted, and capped per giver and receiver. Culture KPIs are calculated from that activity. For business KPIs, an owner reports each period's result and another person reviews and approves it. Treat these inputs as evidence for judgment, not a verdict. Results depend on your configuration and adoption, so compare against your own baseline.

Prepare a one-page evidence pack

Assign one owner. Keep the pack short enough to read in five minutes.

  1. Confirm the period and owners. Match the OKR reporting period to each KPI cycle. Check that every business KPI has an owner and an approver.
  2. Pull approved KPI results. Use the latest approved result, not a draft. Mark anything missing, late or unapproved.
  3. Review objective health. Show each objective's target, progress, supporting measures and missing data. In Wudd, eligible Control Room metrics and approved custom KPIs can be linked to company objectives, so objective health reflects its supporting measures, including gaps.
  4. Summarize recognition signals. Pull the culture KPIs you use, such as Innovation Rate, Cross-Team Collaboration Index or Integrity Signal, if configured. Look at level and distribution. A rising signal concentrated among a few givers or receivers tells a different story from a broad-based rise.
  5. List the decisions you need. Two to four is enough: continue, change, stop or investigate. If there is no decision, put it in a written update.

Recognition is a first-class input, not a buried text. Give it a named section on the page.

Run a 45-minute agenda

Use timeboxes. The output is a decision log, not complete coverage.

Time Segment What you do Output
0–3 min Frame the review Restate the objective and the decisions required today. Shared focus
3–10 min KPI results vs. target The owner states the result, variance and confidence. The reviewer confirms approval. Do not read every metric. Agreed interpretation
10–20 min Objective health Review target, progress, supporting measures and missing data. For closed periods, record delivered, partially delivered, missed or abandoned. Honest status
20–30 min Recognition insights Discuss what recognition suggests about values, collaboration and effort. Ask what changed in behavior, not just what number moved. Hypotheses to test
30–40 min Decisions and owners Choose continue, adjust or stop. Assign one owner and a due date per action. Decision log
40–45 min Close the loop Recognize specific contributions tied to values. Confirm what you will communicate to the team. Clear next step

If you have 30 minutes, cut the objective-by-objective readout and spend the time on exceptions and decisions. Do not cut recognition insights. That is often where the explanation sits.

Ask questions that move the review forward

For KPI results:

  • Which result is outside the expected range, and do we trust the number?
  • Which objective has missing data, and who will close the gap?
  • Is the measure leading or lagging? What would we expect next period if our action works?
  • Did the owner report and reviewer approve on time?

For recognition insights:

  • Which Company Values appear in recognition, and which are quiet?
  • Is recognition broad across teams, or concentrated among a few givers and receivers? Caps limit volume, but they do not replace a distribution check.
  • Are cross-team contributions being recognized? If collaboration is an objective, the Cross-Team Collaboration Index can show whether recognition crosses department boundaries.
  • What story might explain the signal? Recognition is structured data, not free-text NLP. Form a hypothesis, then check it against the work.

Avoid five common failure modes

  1. Reading the dashboard aloud. Put numbers in the pre-read. Spend the meeting on variance, cause and action.
  2. Treating recognition as a separate morale topic. Connect it to how work gets done.
  3. Overreacting to one period. Nightly culture KPIs can move for many reasons, including small samples. Look at trends.
  4. Letting recognition become a popularity contest. Tagging, weights and caps help, but managers still need to watch who gives and receives.
  5. Closing OKRs without outcomes. Record delivered, partially delivered, missed or abandoned. A clean record beats a green dashboard nobody believes.

Close the loop

Publish a one-page decision log within one working day: decision, owner, due date and evidence to review next time. Update OKR outcomes and KPI targets. Then recognize the specific work that moved the measures, tied to a Company Value, with points attached if your program uses them. Wudd describes recognition as happening in Wudd Connect threads through a slash command or wizard, so it can sit where the work is discussed.

At the next review, start with last period's actions. Did they change the KPI result? Did recognition patterns shift? If not, adjust the action or the measure. The agenda is working when your team leaves with fewer slides, clearer ownership and a better explanation of why the numbers moved. Product benefits depend on company configuration and adoption; use your own baseline to judge progress.