OKRs

OKRs (Objectives and Key Results) align teams on what to achieve (objectives) and how to know (key results) in a time box — usually a quarter. Objectives are qualitative and inspirational; key results are measurable outcomes, not task lists.

OKRs are a cadence for focus and learning, not a performance surveillance weapon. Healthy OKRs connect upward to strategy and downward to weekly bets.

Roadmaps without outcomes drift into feature factories. OKRs force evidence of progress — retention lifted, cycle time cut, pipeline quality improved. They coordinate cross-functional work when BMC or journey maps surface priorities needing multiple teams.

Poor OKRs waste the quarter; good OKRs make trade-offs explicit when new ideas appear mid-cycle.

Set OKRs after strategic choices (BMC, journey priorities, north star) and before sprint planning. Revisit mid-quarter for health checks; roll forward with lessons, not blind copy-paste.

Skip OKRs if leadership will not protect focus — too many objectives defeats the system.

1. Anchor to strategy — pick 1–3 objectives tied to BMC, north star, or journey fixes.
2. Draft objectives — outcome language, no numbers in the objective line.
3. Define 2–4 key results per objective — measurable, time-bound, verifiable.
4. Sanity-check — KRs are outcomes (conversion rate), not outputs (ship feature X) unless output truly is the only proxy.
5. Assign owners per KR, not per vague theme.
6. Set confidence and dependencies openly.
7. Cadence: weekly check-ins, mid-quarter grading, retrospective.
8. Archive and narrate — document what worked for next cycle.

• 1–3 objectives per team per quarter; KRs have baselines and targets.
• KRs pass the "so what if we hit 70%?" test — still meaningful.
• Clear owner per KR; dependencies named.
• Objectives trace to customer or business outcomes, not internal vanity.
• End-of-quarter scoring includes narrative learning, not just grades.

• Key results that are task lists ("launch homepage redesign").
• Too many objectives — everything is "critical."
• Sandbagging or impossible targets that erode trust.
• OKRs disconnected from weekly work — set and forgotten.
• Using OKRs for compensation in ways that hide truth.
• Copying industry template OKRs without strategic linkage.

Northvale Systems Q4 OKR: Objective = onboard 70% tier-1 suppliers. KR1 = median validation time ≤ 5 days. KR2 = 95% documents pass first structured upload. KR3 = zero audit findings on vendor evidence.

PulseWell Q3 OKRs. Objective: Prove ROI to CFO buyers in mid-market HR. KR1: Raise pilot-to-paid conversion from 35% to 55%. KR2: Deliver automated ROI report used in 80% of closed-won deals. KR3: Reduce time-to-first insight from 21 to 10 days. Objective 2 (team capacity): Cut support tickets per account 30% via manager playbook self-serve. Weekly check-ins tied to journey pain fixes; grading noted CFO persona objections dropped after KR2 shipped.

Harbor Consulting Q2 OKRs. Objective: Make diagnostics the scalable top of funnel. KR1: 12 diagnostics booked via webinar channel (baseline 4). KR2: 75% of diagnostics convert to phase-2 engagement. KR3: Consultant utilisation ≥ 70% without overtime. They killed a distracting rebrand objective mid-quarter to protect KR1 — OKRs made the trade-off visible to partners.

Clearwater Initiative OKR: Objective = reliable readings at all points. KR1 = 90% weekly tests submitted on time. KR2 = median repair ≤ 72h after fail. KR3 = 80% committees run meetings without NGO staff present.

Run /okr to produce okr-table entries OKR-O-01 objectives with nested OKR-KR-01 key results. Links to north star metric (/northstar) and roadmap (/road). Strategy Pack okr phase drafts from prior artefacts. Grade and comment in workspace; cite OKRs in validation reports.