OKRs: [Team or company], [Quarter and year]
Replace everything in [brackets]. Write one objective per copy of this page, and leave a target blank rather than invent one: a key result with no real starting number is a guess, not a measure.
01How a good OKR is written
Check your draft against each line before you share it.
- One objective: a short, plain sentence about an outcome, not a project name
- Two to four key results, each with a start, a target and a way to measure it
- Key results are outcomes (what changes), not tasks (what you will do)
- Every key result has one owner who reports on it
- The objective is hard enough that reaching 70% would still be a good quarter
02The objective
What you want to be true at the end of the period, and why it matters now.
- Objective: [One sentence: the outcome you want by the end of the period]
- Why now: [What happens if this does not get done this quarter]
- Owner: [Name]
- Level: [Company / Team / Personal]
- Period: [Start date] to [end date]
- Supports: [The company objective this rolls up to, or delete this line]
03Key results
Two to four rows. Start is where you are today, measured, not estimated. Write how each one is measured so nobody argues about the number at the end.
- Score for each row: (current − start) ÷ (target − start), from 0.0 to 1.0
| Key result | Start | Target | Current | How it is measured | Owner |
|---|---|---|---|---|---|
| KR1 [What changes, as a number] | [Today] | [Target] | [Latest] | [Source: report, query, tracked issues] | [Name] |
| KR2 [What changes, as a number] | [Today] | [Target] | [Latest] | [Source] | [Name] |
| KR3 [Optional third key result] | [Today] | [Target] | [Latest] | [Source] | [Name] |
04Initiatives
The work you will do to move the key results. These are bets: if one does not move a number, change it rather than the key result.
- [Initiative] → moves [KR1]
- [Initiative] → moves [KR2]
- [Initiative] → moves [KR3]
05Example: product OKR
Example only. The numbers are illustrative; replace them with your own.
- Objective: New teams get real work done in their first week
| Key result | Start | Target | How it is measured |
|---|---|---|---|
| Share of new teams that finish a project in week one | 20% | 40% | Product analytics, weekly cohort |
| Median days from sign-up to inviting a teammate | 3 | 1 | Sign-up and invite events |
| Onboarding improvements shipped | 0 of 12 | 12 of 12 | The tracked set of onboarding issues |
06Example: sales OKR
Example only. The numbers are illustrative; replace them with your own.
- Objective: Make outbound a repeatable source of new revenue
| Key result | Start | Target | How it is measured |
|---|---|---|---|
| Qualified first calls booked | 0 | 30 | Calls logged against deals in the CRM |
| Value of deals won this quarter | $0 | $40,000 | Won deals closed inside the period |
| Proposals that become won deals | 15% | 25% | Won ÷ proposals sent, in the CRM |
07Example: hiring OKR
Example only. The numbers are illustrative; replace them with your own.
- Objective: Build the team that ships the mobile app
| Key result | Start | Target | How it is measured |
|---|---|---|---|
| Roles filled | 0 | 3 | Roles marked filled inside the period |
| Median days from application to decision | 30 | 14 | Applicant pipeline dates |
| New hires who finish onboarding within 30 days | 0% | 100% | Onboarding checklists completed on time |
08Scoring
Score each key result at the end of the period, then average them for the objective. For ambitious OKRs, 0.7 is a good result; scoring 1.0 every quarter usually means the targets were too easy.
- Score: (current − start) ÷ (target − start), capped between 0.0 and 1.0
- During the quarter: compare the score with how much of the period has passed
| Score | What it means | Status during the quarter |
|---|---|---|
| 0.0 to 0.3 | Little movement. Something was wrong with the plan or the target. | Off track |
| 0.4 to 0.6 | Real progress, short of the target. | At risk |
| 0.7 to 0.9 | A good result on an ambitious target. | On track |
| 1.0 | Target reached. | Done |
09Weekly check-in
Five minutes, same day each week, written by the owner of each objective. The history matters more than any single week.
- Week: [Date]
- Status: [On track / At risk / Off track / Done]
- In one sentence: [How it is going and why]
- New values: [KR1: value, KR2: value, KR3: value]
- Blocked by: [What is in the way, and who can help, or none]
10End-of-quarter review
Do this before you write next quarter's OKRs.
- Every key result has a final value and a score
- Each score has one sentence on why it landed where it did
- You have decided whether each objective continues, changes or ends
- Lessons about how you set targets are written down for next time