Strategy

OKRs for engineering teams: examples and common mistakes

How engineering teams can write useful OKRs: outcome-based key results, worked examples for platform and product teams, and the mistakes that make OKRs fail.

· 6 min read

OKRs — objectives and key results — are supposed to focus a team on what matters. In many engineering organizations they have become a quarterly ritual of copying the roadmap into a spreadsheet. The difference between the two is almost entirely in how the key results are written.

The structure

An objective is qualitative and inspiring: where you want to be. Key results are measurable outcomes that show you got there — usually two to four per objective. Projects and tasks are not key results; they are how you hope to move them.

Outputs versus outcomes

  • Output (weak): “Launch the new search service.”
  • Outcome (strong): “Search result click-through rises from 31% to 40%.”
  • Output (weak): “Migrate to Kubernetes.”
  • Outcome (strong): “Lead time from merge to production falls from 3 days to 4 hours.”

If you could hit the key result and still fail the objective, it is an output in disguise.

Examples

Product team. Objective: make onboarding effortless for small businesses. Key results: activation within seven days rises from 42% to 55%; onboarding support tickets per new account fall by half; time to first invoice drops from 3 days to under 1.

Platform team. Objective: make shipping safe and boring. Key results: change failure rate falls from 18% to under 10%; median deploy time under 15 minutes; every service has an SLO with an error-budget policy.

Common mistakes

  • Too many: five objectives with five key results each is a to-do list, not a focus.
  • All outputs: a list of projects tells you nothing about whether they worked.
  • Sandbagging: if every key result is hit at 100%, the targets were too safe. Around 70% is healthy for stretch goals.
  • No baseline: “improve latency” cannot be scored. Write the starting number.
  • Tied to compensation: people stop setting stretch goals the moment bonuses depend on them.
  • Set and forget: review progress every two weeks, not just at quarter end.

Where keep-the-lights-on work fits

Not everything belongs in OKRs. Reliability, security and support are ongoing commitments; track them as health metrics with thresholds, and only make them an OKR when you intend to change the level. Be explicit about how much capacity they take — often 30 to 50% — so the OKRs are sized for what is left.

Quick check

3 questions from the related lessons. Answers are explained, and the ones you get right count towards your progress.

Question 1

Q1.Which is a well-formed key result?

Question 2

Q2.An initiative has a reach of 2,000, impact of 2, confidence of 50% and effort of 4 person-months. What is its RICE score?

Question 3

Q3.Which of these is a strategy rather than a goal?

Practice this in a lesson

Each engMBA lesson pairs a short explanation with practice questions that grade themselves. Free, with no signup.

See the full curriculum

Keep reading