OKRs for Small Teams: A Practical Guide

Most OKR advice is written for Google, Intel, or fictional Fortune 500 companies with 50,000 employees.

If you have 5-50 people, that advice is mostly wrong.

Here's what actually works.

1. Fewer OKRs Than You Think

At scale, Google had 3-5 objectives per team, each with 3-5 key results. For a small team, that's too much.

My rule: 1 objective per person, 2-3 key results max. If everyone has too many goals, nothing gets done.

2. Quarterly, Not Annual

Don't write annual OKRs. You won't hit them, and you won't remember them by March.

Quarterly cycles force you to make things small and measurable. 12 weeks is long enough to accomplish something real, short enough to stay focused.

3. Key Results Are Numbers, Not Tasks

Bad: "Launch new onboarding flow" Good: "Increase 7-day activation from 22% to 35%"

Bad: "Improve customer support" Good: "Reduce avg response time from 4.2h to <1h"

If it's not a number, it's not a key result. It's a project.

4. Check In Weekly, Score Quarterly

Each Monday, take 30 seconds per KR:

• What's the current value?
• How confident are you? (On track / At risk / Off track)
• One sentence: what's blocking?

Quarterly, score each KR 0.0-1.0. The target is 0.7. If you hit 1.0 on everything, your goals were too easy.

5. Don't Tie OKRs to Compensation

This ruins everyone's behavior. They'll pick easy goals they know they can hit. Keep OKRs aspirational. Pay for performance with other tools.

6. Make Them Visible

Hide OKRs in a spreadsheet nobody opens and they die. Put them on a wall, in Slack, at the top of your all-hands. The best OKR tool is the one your team actually sees every day.

(This is why I built ProKR's home dashboard to lead with your OKRs.)

TL;DR

• 1 objective per person, 2-3 KRs
• Quarterly, not annual
• KRs are numbers, not tasks
• Weekly 30-second check-ins
• Score 0.7, not 1.0
• Don't link to comp
• Keep them visible

Good luck.

— Jordan