OKR progress review

Purpose

Turn a period's OKR updates into a defensible progress view: what moved, what is off track, which key results lack evidence, and which risks require a change in plan. The review separates measured attainment from owner commentary and does not convert confidence into performance judgment.

Scope

Review objectives, key results, baseline and target values, current check-ins, confidence ratings, owners, dependencies, milestones, and prior-period commitments. Cover committed and stretch key results and status changes across the selected review period. Excluded: rewriting objectives, assigning employee performance ratings, approving budget changes, and predicting final attainment where no model or evidence is supplied.

Data basis

• OKR table with objective_id, objective_text, owner, team, cycle, status, and priority.
• Key-result table with kr_id, objective_id, metric, baseline, target, current_value, unit, due_date, scoring_method, and confidence.
• Check-in notes with update_date, progress_comment, blocker, dependency, next_milestone, and evidence_url.
• Prior review and OKR policy defining status vocabulary, scoring bands, update cadence, and confidence scale.

Result

Create an OKR review sheet with attainment calculations, trend, status, confidence, evidence coverage, blockers, and next milestone per key result, plus a leadership memo summarizing objective-level exceptions and changes since the prior review.

Quality criteria

• Each key result maps to exactly one objective and one review cycle.
• Attainment uses the supplied scoring method and preserves unit and directionality.
• Status is derived from the stated policy or marked owner-reported when no rule exists.
• Every red or yellow finding cites a check-in, value, milestone, or policy section.
• Missing updates, stale evidence, and changed targets are visible rather than silently excluded.

Instructions

Calculate progress only when baseline, target, current_value, and direction are compatible. For a lower-is-better metric, do not apply a higher-is-better percentage. Compare like-for-like cycle and due dates; explain any target change before comparing. Treat a missed update cadence as an evidence gap, not as zero progress. Keep confidence as a separate field. Roll up objective status from its key results only when the policy defines the roll-up; otherwise show the underlying statuses and state that no roll-up was applied.

Adapt before use

• Add the OKR policy with scoring bands, status definitions, confidence scale, and roll-up rules.
• Map the company's objective, key-result, check-in, and evidence fields to the names used here.
• Set the review cutoff date and the age that makes an evidence link stale.
• Identify whether stretch key results are reported separately from committed results.