Quarterly OKR Scoring & Retrospective

Template Overview

Objectives and Key Results (OKRs) provide strategic alignment across high-growth organizations. Setting ambitious quarterly OKRs is relatively easy; the true test of organizational discipline occurs at the end of the quarter when leaders must candidly score results, evaluate misses, and learn from execution gaps.

Too many teams abandon OKRs midway through the quarter or inflate scores to avoid uncomfortable conversations about missed targets.

This template provides an objective scoring rubric: quantitative Key Result evaluations (0.0 to 1.0), systemic post-mortem reflections on misses, qualitative context on unexpected achievements, and forward-looking guidance for upcoming quarterly planning.

Markdown Template Structure

Copy the block below or click Download .md File to add this template directly to your personal vault:

---
title: "Quarterly OKR Scoring Review: [Quarter / Year]"
date: [YYYY-MM-DD]
quarter: "Q3 2026"
review_lead: "[[Head of Product / Operations]]"
overall_okr_average_score: 0.74
scoring_verdict: [Healthy Stretch Attained | Over-Conservative | Underperformed]
tags: [okr, goals, quarterly, retrospective, strategy]
---

# Quarterly OKR Scoring Review: [Quarter / Year] — [YYYY-MM-DD]

## 1. Executive Summary & Company-Wide Cadence
- **Quarterly Theme:** Achieve rock-solid on-device software stability and establish sovereign data market leadership.
- **Overall Attainment Score:** 0.74 across 4 strategic objectives (indicates well-calibrated stretch targets).

## 2. Objective-by-Objective Scoring & Analysis
### Objective 1: Deliver Enterprise-Grade On-Device Audio Transcription
- **Objective Lead:** [[Elena Rostova]] (VP Eng)
- **Objective Score:** 0.83 (🟢 Green)

| Key Result | Baseline | Target | Actual Result | Score (0.0 - 1.0) | Verdict |
| :--- | :--- | :--- | :--- | :--- | :--- |
| KR 1.1: Reduce CoreAudio transcription latency | 1,200ms | < 350ms | 280ms achieved | 1.0 | Exceeded |
| KR 1.2: Zero dropped audio frames under stress | 0.05% | 0.00% | 0.00% verified | 1.0 | Exceeded |
| KR 1.3: Ship localized multi-language models | English only | 4 Languages | English & Spanish only | 0.5 | Partial Progress |

### Objective 2: Build World-Class Markdown Content & Knowledge Assets
- **Objective Lead:** [[David Park]] (VP Product)
- **Objective Score:** 0.70 (🟢 Green)

| Key Result | Baseline | Target | Actual Result | Score (0.0 - 1.0) | Verdict |
| :--- | :--- | :--- | :--- | :--- | :--- |
| KR 2.1: Author comprehensive technical glossary | 0 terms | 60 terms | 60 terms deployed | 1.0 | Completed |
| KR 2.2: Launch curated Markdown template gallery | 0 templates | 120 templates | 120 templates staged | 1.0 | Completed |
| KR 2.3: Reach 100,000 monthly organic pageviews | 15,000 | 100,000 | 42,000 achieved | 0.4 | Lagging Indicator |

## 3. Deep-Dive Post-Mortem on Missed Targets
> [!NOTE] Reflection on KR 1.3 (Multi-Language Models)
> We underestimated the memory footprint required to run simultaneous Whisper models for non-Latin scripts on 8GB base Mac hardware. 
> **Learning:** Future AI model additions will undergo rigorous memory-envelope benchmarking before setting public launch dates.

## 4. Key Takeaways for Next Quarter (Q4 2026)
- Double down on localized enterprise customer discovery in European markets.
- Invest in automated CI/CD physical hardware test racks to accelerate release verification loops.

## 5. Next Quarter OKR Draft Checkpoint
- [ ] [[David Park]] Distribute Q4 OKR draft proposals by [[YYYY-MM-DD]].
- [ ] Schedule executive alignment session for final Q4 OKR lock.

Filled Real-World Example

Here is a realistic example demonstrating how this template captures actual deliberations:

---
title: "OKR Scoring: Q3 2026 Final"
date: 2026-10-01
quarter: "Q3 2026"
overall_okr_average_score: 0.76
tags: [okr, quarterly, scoring]
---

# OKR Scoring: Q3 2026 Final — October 1, 2026

## 1. High-Level Performance
Company achieved an average score of 0.76. Key wins include shipping the 60-term technical glossary and completing local FTS5 indexing.

## 2. Key Learnings
Traffic growth is compounding following the launch of high-depth glossary hubs. Staging the 120 templates will expand indexable footprint from 272 to 405 pages.

## 3. Q4 Priorities Locked
- Launch Markdown Template Gallery.
- Expand local AI prompt customization workbench.

When to Use and When to Avoid

When to Use

• Use at the close of each calendar quarter during formal OKR scoring and retrospective sessions.
• Use to evaluate team performance against quantitative Key Results on a standardized 0.0 to 1.0 scale.
• Use to extract organizational insights from missed targets before drafting next quarter’s goals.

When to Avoid

• Avoid using for weekly tactical task standups or individual engineer pull request reviews.
• Avoid using as a punitive employee compensation scoring mechanism.

On-Device AI Integration

Score and evaluate quarterly OKRs using Oyma on macOS:

Analyze the quarterly OKR scoring review transcript:
1. Synthesize the executive summary, quarterly theme, and overall average attainment score.
2. Group objectives and build scoring tables for each Key Result comparing target vs actual.
3. Extract candid post-mortem reflections explaining reasons behind missed or lagging results.
4. Record strategic lessons learned and scheduling commitments for upcoming quarterly OKRs.
Output in structured CommonMark format.

Your company’s strategic performance records and internal OKR evaluations stay safely on your Mac.