All templates
Ops
OKR Quarterly Plan
Outcome-based OKRs (Objective + 3-5 measurable Key Results) with monthly check-in cadence and scoring. The template that replaces 'we're so busy' with 'we hit 0.7'.
Last updated June 8, 2026
What it is
A quarterly OKR planning template for founder-led teams of 2-30 people. Replaces vague "we're working on X" with measurable commitments. Used at the start of each quarter, reviewed monthly, scored at quarter-end.
When to use it
First Monday of each quarter. Re-reviewed in the monthly leadership meeting. Scored and rewritten in the last week of the quarter before the next planning cycle.
The template
# OKR Plan — Q[N] [YEAR] **Owner:** [CEO / function lead] **Plan written:** [DATE] **Review cadence:** Last Friday of each month **Score date:** [DATE — last week of quarter] --- ## Theme for the quarter One sentence. The bet you're making this quarter that defines what success looks like. > Example: "Turn the new mid-market motion into the dominant revenue source — proving it generates >40% of new MRR by quarter-end." ## Objectives (1-3 max) Ambitious, qualitative, time-bound. Each Objective is something the team can rally around. Not a list of features — a desired state of the world. ### Objective 1: [Objective in one sentence] **Why this matters:** [1-2 sentences. The reasoning that justifies the investment.] **Key Results** (3-5 measurable outcomes): | # | Key Result | Baseline | Target | Score at Q-end | |---|---|---|---|---| | 1 | [Specific, measurable outcome] | [Current number] | [Target number] | [0.0-1.0] | | 2 | [Same] | | | | | 3 | [Same] | | | | ### Objective 2: [If you have a second] [Same structure as Objective 1.] ### Objective 3: [If you have a third — maximum] [Same structure.] ## Anti-OKRs — what we're NOT doing this quarter List 2-3 things you're explicitly deferring. Forces sharper prioritisation and protects the team from scope creep. - [Thing 1 we're not doing — and the reason] - [Thing 2 — and the reason] ## Monthly check-in template Each month, the OKR owner updates this in the leadership meeting: | Key Result | Last month | This month | On track / At risk / Off track | Notes | |---|---|---|---|---| | | | | | | **Decisions for the month:** What changes based on what we just reviewed? ## Quarter-end scoring Each Key Result scored 0.0-1.0: - **0.0-0.3** = Missed badly. Worth a post-mortem. - **0.4-0.6** = Decent progress, didn't fully hit. Normal for ambitious OKRs. - **0.7-0.8** = Strong outcome. The target zone for well-set OKRs. - **0.9-1.0** = Hit or exceeded. Either great execution OR the Key Results were too easy — pick one before next quarter. ## Lessons forward Write 3-5 sentences answering: what did we learn this quarter that changes how we plan next quarter? --- **Discipline reminder:** The monthly check-in is non-negotiable. OKRs without a review cadence become a write-once doc that nobody references. The 30 minutes a month is the entire point.
Common mistakes
- Treating Key Results as a todo list — "ship feature X" is not a Key Result, the measurable outcome of feature X is
- More than 3 Objectives per team — dilutes attention; pick the 1-3 that matter
- Cascading OKRs top-down to every IC — defeats the framework; teams should set the Key Results they own
- Grading OKRs as part of performance reviews — kills willingness to set ambitious objectives next time
- Only reviewing at quarter-end — the discipline is in the weekly tracking, not the report
- OKRs that depend on other teams without their buy-in — surprise dependencies kill execution
Related tool
Founder Weekly ReviewRelated hub
Startup Operations