What this covers
The pain: you wrote OKRs in week 1, never looked at them in week 4, and by week 10 the quarter ended with three measured outcomes and seven aspirational paragraphs. This workflow uses AI to draft 3 objectives with 3 measurable key results each, run a 15-minute weekly check-in that catches drift early, and produce an end-of-quarter retro with honest scoring. The trick is treating OKRs as a living doc you read every Monday, not an artifact you write in week 1 and rediscover in week 13.
Who this is for
Team leads who set quarterly OKRs for an engineering, product, or design team. ICs whose company asks for personal OKRs. Founders who need to align a small team against three priorities. Also useful for chief-of-staff roles drafting cross-functional OKRs that span 4 squads — the same cadence catches misalignment before it costs a sprint.
When to reach for it
Two weeks before the quarter starts, when you have rough strategic priorities but no measurable language. Mid-quarter when an OKR has obviously slipped and you need a re-plan, not a re-write. End of quarter for an honest retro that feeds the next planning cycle. Skip it if the quarter is already half done and you have no baseline metrics — better to run a 4-week sprint than fake an OKR.
Before you start
- Have last quarter’s OKRs and actual scores open. If you do not have last quarter, gather any quantitative outcome you can defend.
- Know the company’s top 3 priorities for the quarter. If you cannot name them, do that first; team OKRs that contradict company priorities die in week 6.
- Pick a single OKR doc surface — Notion, a Google Doc, or your OKR tool. Switching surfaces breaks the weekly check-in.
- Block 90 minutes for the drafting session and 15 minutes every Monday for the check-in. Both go on the calendar before you start.
- Decide your scoring rubric ahead of time. The 0.0-1.0 scale with 0.7 as “ambitious target hit” is the default; pick it and stick to it.
Step by step
- State the strategic context in 3 sentences. Example:
Team is platform infra; company priority is reducing onboarding time; our quarter must contribute to that without breaking 99.9% uptime. - Ask AI to propose 3 objectives that ladder to company priority, each with 3 measurable key results. Reject any KR whose verb is “improve”, “drive”, or “support”.
- For each KR, demand a baseline number and a target number. Example:
p95 onboarding latency from 8.2s to under 4snotmake onboarding faster. - Pressure-test the set: ask AI to identify which KR is most likely to slip and which is sandbagged. Adjust until both answers feel honest.
- Publish the OKR doc and pin it to the weekly team meeting agenda. Every Monday: 15 minutes, walk every KR, mark green / yellow / red.
- When a KR turns red two weeks in a row: re-plan, do not re-write. Ask AI for 3 interventions that could move the number; pick one and commit.
- End of quarter: paste the final numbers and ask AI for a retro that distinguishes “missed because of execution” from “missed because the target was wrong”. The distinction matters for next quarter.
First-run exercise
Pick a quarter that already ended. Reconstruct what your OKRs should have been from the actual outcomes you remember. Run the AI drafting prompt on that hindsight context and compare to what you actually wrote at the time. Two things show up: the KRs you would have written are sharper than what you wrote, and you forgot at least one outcome that should have been an objective. Both findings make next quarter better. The exercise also calibrates how aggressive AI’s default targets are versus your real velocity.
Quality check
- Every KR has a baseline number and a target number. No baseline means no honest scoring at end of quarter.
- Every objective ladders to a company priority in one sentence. If you cannot draw the line, the objective dies in week 6.
- At least one KR per objective is a leading indicator, not a lagging one. Lagging-only OKRs cannot be steered mid-quarter.
- The set has 3 objectives, not 5. Five objectives means zero priorities and a quarter spent context-switching.
- Each KR can be measured in 5 minutes from a real source. If measuring takes a half-day, the weekly check-in will not happen.
How to reuse this workflow
- Save the drafting prompt, the pressure-test prompt, the weekly check-in prompt, and the retro prompt as four snippets. New quarter, swap the strategic context.
- Keep a
quarters/folder with the doc for every quarter. Diff two adjacent quarters; the pattern of misses is the real signal. - Track an “OKR hit rate” across quarters. Below 30% means targets are too aggressive; above 80% means sandbagged.
- After 4 quarters, paste the four retros into the next planning prompt. AI calibrates to your team’s actual range.
- Share the drafting prompt with one peer team. Comparing drafts catches misaligned priorities before the quarter starts.
Recommended workflow
Strategic context in 3 sentences → AI drafts 3 objectives with 3 measurable KRs each → pressure-test for slip risk and sandbagging → publish OKR doc → Monday 15-minute check-in marking green/yellow/red → red KR two weeks running triggers re-plan with AI-proposed interventions → end-of-quarter retro that separates execution misses from wrong-target misses.
Common mistakes
- KRs with verbs like “improve” or “drive”. They expand forever and cannot be scored.
- Writing the doc in week 1 and never opening it. The weekly check-in is the entire workflow; without it, OKRs are an artifact.
- Five objectives. Three is the upper bound for a focused quarter.
- No baseline number. End-of-quarter scoring becomes a debate instead of a number.
- Re-writing OKRs in week 7 because they slipped. Re-plan the path to the same KR; do not change the KR after the fact.
- Sandbagged targets. The team learns that hitting 1.0 means the target was too easy and stops trying for stretch.
FAQ
- What if the company has no OKRs?: Build team OKRs that ladder to a written company priority. Without a written priority, start by writing one for the team’s owner to react to.
- Should personal OKRs match team OKRs?: Mostly yes for ICs; partially for managers who carry team OKRs plus a development OKR.
- How aggressive should KR targets be?: 0.7 is “ambitious target hit”; if you regularly hit 1.0 the targets are too soft.
- What if a KR depends on another team?: Mark it
depends on Xand have a separate ask in the doc. Do not let a dependency hide a slip. - How long should the OKR doc be?: One page. If it does not fit on one page, the team will not read it weekly.
- What about half-quarter pivots?: Allowed once per quarter, with explicit retro on why. More than once means the strategy is unstable.
Related
Tags: #okr #Planning #Quarterly #Tutorial