How to Set OKRs That Actually Stick
Most OKRs die in a spreadsheet by week three. The ones that stick are few, measurable, genuinely ambitious, and reviewed often enough that they steer real decisions.
What good OKRs look like
An objective is a qualitative, ambitious statement of what you want to achieve; key results are the measurable outcomes that prove you got there. The classic failure modes are having too many, writing key results that are really tasks, and setting them once and forgetting them. Good OKRs are few, outcome-based, and revisited on a rhythm.
- Set three to five objectives per team, no more
- Write two to four measurable key results per objective
- Make key results outcomes, not activities or task lists
- Set ambitious targets where ~70% attainment is a success
- Review progress on a regular cadence, not just at quarter-end
Objectives vs key results
| Objective | Weak key result | Strong key result |
|---|---|---|
| Delight new users | Redesign onboarding | Lift day-7 activation from 32% to 45% |
| Win the mid-market | Do outbound | Close 12 mid-market logos |
| Ship reliably | Improve testing | Cut Sev-1 incidents from 9 to 3 |
A worked example
- 1Draft three to five objectives tied to the company’s priorities.
- 2Write measurable, outcome-based key results for each.
- 3Cascade so team OKRs support company OKRs without dictating tasks.
- 4Set a weekly or biweekly review rhythm.
- 5Score at quarter-end and carry the learning forward.
How Fintra runs OKRs
Fintra’s goals and OKRs live alongside 1:1s and performance reviews, so objectives are reviewed in the conversations that already happen rather than in a separate tool nobody opens. Key results track measurable progress, cascade from company to team, and feed the review cycle - closing the loop between what you said mattered and how you evaluate the year.
- Company-to-team OKR cascade without task micromanagement
- Measurable key-result tracking with a review rhythm
- OKRs reviewed inside 1:1s, not a separate tool
- Goals feed the performance review cycle
Frequently asked questions
How many OKRs should a team have?
Three to five objectives, each with two to four key results. More than that dilutes focus and turns OKRs into a task list. The constraint is the point - OKRs are about choosing what matters most.
What is the difference between an objective and a key result?
An objective is a qualitative, ambitious statement of what you want to achieve. Key results are the measurable outcomes that prove you achieved it. If a key result is a task you can simply complete, rewrite it as an outcome.
What attainment counts as success for OKRs?
For ambitious OKRs, hitting around 70% is generally considered a success - full attainment often means the targets were not ambitious enough. Commit-style goals meant to be fully delivered are a different category.
How often should OKRs be reviewed?
On a weekly or biweekly rhythm, ideally inside conversations that already happen like 1:1s, with a formal score at quarter-end. OKRs reviewed only at the end of the quarter rarely change any decisions along the way.
Stay in the loop
One practical finance briefing a week - new guides, checklists, and benchmarks.