The OKR (Objectives and Key Results) system has become the standard for managing performance in modern companies. From Google and Intel to startups — everyone uses this methodology to focus work on what truly matters. But knowing about OKR is one thing, and successfully implementing it is quite another. This article will help you understand OKR principles, figure out the differences from KPI and MBO, and go through the entire implementation path: from the first cycle to a stable goal-management system in your organization.
What is OKR and Why It Works
Definition and Essence of the Methodology
OKR is a management methodology that directs the efforts of all people in an organization toward the most important and common goals. The abbreviation is simple: O (Objectives) + KR (Key Results).
The OKR system combines the best practices from three approaches:
MBO (Management by Objectives) — goal-setting
KPI (Key Performance Indicators) — measurable metrics
Agile — sprints, flexibility, and adaptability
Result? A flexible goal-management system that works in practice, not just on paper.
MBO (Management by Objectives) — goal-setting
KPI (Key Performance Indicators) — measurable metrics
Agile — sprints, flexibility, and adaptability
Result? A flexible goal-management system that works in practice, not just on paper.
Four Superpowers of OKR
Why do companies choose OKR? Here are four main reasons:
1. Prioritization and Commitment
OKR tells a person clearly: allocate 10–15% of your time to achieving company goals. The rest of the time goes to current work, which will keep you busy anyway. But ambitious goals require conscious work, and OKR provides that.
2. Synchronization and Transparency
Everyone in the company sees everyone's goals. This may seem strange, but it's a powerful tool. Goal synchronization between departments prevents scattered efforts: people see what colleagues are doing and quickly find points of intersection and mutual help.
3. Monitoring and Real-Time Feedback
OKR allows you to track progress weekly, not wait a year. The system includes weekly check-ins, mid-quarter reviews, and quarterly retrospectives — people get feedback in real time.
4. Striving for Outstanding Results
Ambitious goals stimulate better work. As psychology professor Edwin Locke wrote: "Specific, difficult goals yield higher performance than vague and abstract ones". OKR is built into this psychology.
1. Prioritization and Commitment
OKR tells a person clearly: allocate 10–15% of your time to achieving company goals. The rest of the time goes to current work, which will keep you busy anyway. But ambitious goals require conscious work, and OKR provides that.
2. Synchronization and Transparency
Everyone in the company sees everyone's goals. This may seem strange, but it's a powerful tool. Goal synchronization between departments prevents scattered efforts: people see what colleagues are doing and quickly find points of intersection and mutual help.
3. Monitoring and Real-Time Feedback
OKR allows you to track progress weekly, not wait a year. The system includes weekly check-ins, mid-quarter reviews, and quarterly retrospectives — people get feedback in real time.
4. Striving for Outstanding Results
Ambitious goals stimulate better work. As psychology professor Edwin Locke wrote: "Specific, difficult goals yield higher performance than vague and abstract ones". OKR is built into this psychology.
OKR vs. KPI vs. MBO vs. SMART: What's the Difference
OKR vs. KPI: Key Results are similar to KPI but serve a different purpose. KPI are long-term indicators of business health. OKR is a tool to focus on what is especially important right now for a quarter. For example, for a recruiter, KPI might be "close 12 positions in a year," while KR in OKR is "conduct 80 interviews this quarter" (very specific, temporary requirement).
OKR vs. MBO: Management by Objectives required annual goals tied to bonuses. People feared taking ambitious goals because non-achievement meant losing a bonus. OKR are not tied to compensation and change every quarter — this allows people to take risks.
OKR vs. SMART: SMART goals (Specific, Measurable, Achievable, Relevant, Time-bound) are an excellent tool for personal development but not flexible enough for rapidly changing organizations. OKR requires reassessment every quarter.
OKR vs. MBO: Management by Objectives required annual goals tied to bonuses. People feared taking ambitious goals because non-achievement meant losing a bonus. OKR are not tied to compensation and change every quarter — this allows people to take risks.
OKR vs. SMART: SMART goals (Specific, Measurable, Achievable, Relevant, Time-bound) are an excellent tool for personal development but not flexible enough for rapidly changing organizations. OKR requires reassessment every quarter.
What a Quality Objective and Key Result Look Like
Objectives (Goals): Formulation Rules
An Objective is a direction we want to conquer. Here are the rules:
1.Inspiring, not boring. The goal should motivate you. Not just "increase sales" but "become number one in our segment."
2.Concrete, not vague. Not "improve customer work" but "conquer the B2B market in EU."
3.Important for the company. The goal should be strategic, not just "close an urgent bug."
4.Long-term (can be). An Objective can be a goal for a year or even longer.
5.How many goals to set? Expert recommendations — 3–5 goals per company, team, or person. No more! When there are more than 10 goals, people get lost.
Key Results: Formulation Rules
A Key Result is a measurable way to check if we've achieved the Objective. Here are the rules:
1.Must have a number. If there's no number in the Key Result — it's not a Key Result, it's a task.
2.Number is time-bound. Not just "5 km per week" but "5 km per week during this quarter."
3.Ambitious but realistic. Recommended achievement percentage — 70%. If you achieved 70%, that's great. If 100% — maybe the goal was too modest.
4.Can change during the quarter. If a Key Result becomes irrelevant or wrong, it can be updated. OKR is a flexible system.
5.Transparent and clear. Anyone in the company should understand what you're measuring
An Objective is a direction we want to conquer. Here are the rules:
1.Inspiring, not boring. The goal should motivate you. Not just "increase sales" but "become number one in our segment."
2.Concrete, not vague. Not "improve customer work" but "conquer the B2B market in EU."
3.Important for the company. The goal should be strategic, not just "close an urgent bug."
4.Long-term (can be). An Objective can be a goal for a year or even longer.
5.How many goals to set? Expert recommendations — 3–5 goals per company, team, or person. No more! When there are more than 10 goals, people get lost.
Key Results: Formulation Rules
A Key Result is a measurable way to check if we've achieved the Objective. Here are the rules:
1.Must have a number. If there's no number in the Key Result — it's not a Key Result, it's a task.
2.Number is time-bound. Not just "5 km per week" but "5 km per week during this quarter."
3.Ambitious but realistic. Recommended achievement percentage — 70%. If you achieved 70%, that's great. If 100% — maybe the goal was too modest.
4.Can change during the quarter. If a Key Result becomes irrelevant or wrong, it can be updated. OKR is a flexible system.
5.Transparent and clear. Anyone in the company should understand what you're measuring
Example: Product Company (SaaS)
BAD OKR:
Objective: Improve the product
Key Result: Build 5 features
❌ Why is it bad? Goal is vague ("improve"), Key Result doesn't make sense (number of features says nothing about results).
GOOD OKR:
Objective: Increase retention rate and become essential for SMB in EU
Key Results:
- Increase 30-day retention from 62% to 75%
- Achieve NPS ≥ 50 in the SMB category
- Get 50+ positive case studies from EU customers
✅ Why is it good? Goal is inspiring and concrete. Each KR is measurable, time-bound, and ambitious (requires work).
Example: HR Team
BAD OKR:
Objective: Hire good people
Key Results:
Close all open positions
Improve interview process
❌ Why is it bad? Too vague. What does "good" mean? What does "improve" mean?
GOOD OKR:
Objective: Build a team of top-10% specialists in our niche
Key Results:
- Hire 12 engineers, at least 5 with > 5 years experience in the relevant stack
- Achieve 85% positive feedback score on interviews from candidates (post-round survey)
- Reduce time-to-hire from 60 days to 35 days for strategic positions
✅ Why is it good? Goal is clear. KR are specific, measurable, focused on quality, not quantity.
OKR cascading Models
How Goals cascade: Company → Team → Individual
OKR works on the principle of nested matryoshka dolls. Company-level goals become a reference point for teams, team goals for individuals.
1. Company-level OKR (Strategic Goals)
These are organization-level goals. Usually 3–5 goals that determine the direction for the quarter.
Example:
2. Department/Team OKR (Tactical Goals)
Each team looks at company goals and asks: "What do we need to do to help the company achieve its goals?"
Example (Sales team responds to Company OKR):
3. Individual OKR (Personal Goals)
Each employee looks at their team's goals and decides what personal OKR they will set to help the team.
Example (Account Executive from Sales):
Important Note: cascading is Dialogue, Not Top-Down Command
Anti-pattern: Manager writes OKR top-down and tells subordinates: "Here are your OKR, go do them." This doesn't work.
Correct Approach:
1.Company defines 3–5 strategic goals
2.Each team proposes their OKR, explaining how they'll help achieve company goals
3.Manager and team sync goals (dialogue may occur)
4.OKR is approved
5.Each employee proposes their OKR in the context of team goals
This is a democratic, not authoritarian process.
OKR works on the principle of nested matryoshka dolls. Company-level goals become a reference point for teams, team goals for individuals.
1. Company-level OKR (Strategic Goals)
These are organization-level goals. Usually 3–5 goals that determine the direction for the quarter.
Example:
- Objective: Scale Sales in EU and become top-3 in the segment
- Key Results:
- Achieve ARR = $10M (from current $6M)
- Cover 60% of target market (from 25%)
- Get 5 contracts > $100k from Fortune 500 companies
2. Department/Team OKR (Tactical Goals)
Each team looks at company goals and asks: "What do we need to do to help the company achieve its goals?"
Example (Sales team responds to Company OKR):
- Objective: Increase conversion rate and average deal size
- Key Results:
- Increase win rate from 22% to 35%
- Increase average contract size from $18k to $25k
- Adapt sales process for Enterprise (new in EU)
3. Individual OKR (Personal Goals)
Each employee looks at their team's goals and decides what personal OKR they will set to help the team.
Example (Account Executive from Sales):
- Objective: Become top performer in Enterprise segment EU
- Key Results:
- Close 4 contracts > $25k in the quarter
- Create and validate new sales deck for EU on 5 Fortune 500 companies
- Get rating ≥ 4.5 from customers in post-call survey
Important Note: cascading is Dialogue, Not Top-Down Command
Anti-pattern: Manager writes OKR top-down and tells subordinates: "Here are your OKR, go do them." This doesn't work.
Correct Approach:
1.Company defines 3–5 strategic goals
2.Each team proposes their OKR, explaining how they'll help achieve company goals
3.Manager and team sync goals (dialogue may occur)
4.OKR is approved
5.Each employee proposes their OKR in the context of team goals
This is a democratic, not authoritarian process.
OKR Cycle: How the Practical Process Works
Quarterly Cycle
OKR is typically planned for 3 months (a quarter). Here's how the cycle looks:
Phase 1: Planning (Planning week, quarter start)
What Happens:
Time: Usually 1 week at the start of the quarter is allocated for planning.
Tool: OKR are documented in a special tool (15Five, People Force, Ally, Lattice, Ally) or even in a shared Google Sheet/spreadsheet.
Result: All OKR are published and visible to everyone in the company. Transparency!
Phase 2: Weekly Check-ins
What Happens:
Example of KR Status:
🟢 Green: On track to achieve by end of quarter
🟡 Yellow: Risk of not achieving, needs help
🔴 Red: We're not making it, need to change approach
Result: Team sees progress in real time.
Phase 3: Mid-Quarter Review
What Happens:
Important: This is NOT a meeting to blame people. This is a meeting to learn and adapt.
Phase 4: End-of-Quarter Retrospective
What Happens:
Important: Retrospective is about learning, not evaluating people. OKR should NOT be tied to bonuses or terminations.
Annual Planning
Some companies (like Google under Sundar Pichai) do long-term OKR for a year, then break them into quarterly ones. This gives more strategic context. But the main cycle is still quarterly.
OKR is typically planned for 3 months (a quarter). Here's how the cycle looks:
Phase 1: Planning (Planning week, quarter start)
What Happens:
- Company leadership defines 3–5 company-level OKR for the quarter
- Each team looks at company OKR and proposes their team OKR (usually 3–5)
- Sync meetings between managers — ensure OKR are connected and don't conflict
- Each employee proposes their personal OKR (2–3)
Time: Usually 1 week at the start of the quarter is allocated for planning.
Tool: OKR are documented in a special tool (15Five, People Force, Ally, Lattice, Ally) or even in a shared Google Sheet/spreadsheet.
Result: All OKR are published and visible to everyone in the company. Transparency!
Phase 2: Weekly Check-ins
What Happens:
- Every Monday (or chosen day), a 30-minute team meeting is held
- People update progress status for each KR (green/yellow/red)
- Discuss blockers (what got in the way this week?)
- Share small wins
- Make decisions about plan adjustments (if needed)
Example of KR Status:
🟢 Green: On track to achieve by end of quarter
🟡 Yellow: Risk of not achieving, needs help
🔴 Red: We're not making it, need to change approach
Result: Team sees progress in real time.
Phase 3: Mid-Quarter Review
What Happens:
- At week 6–7 of the quarter, a meeting is held
- Team analyzes current progress on all OKR
- Discusses mistakes and wrong assumptions
- If a KR is no longer relevant or incorrect, it can be updated (this is allowed!)
- Plan for the second half of the quarter is revised
Important: This is NOT a meeting to blame people. This is a meeting to learn and adapt.
Phase 4: End-of-Quarter Retrospective
What Happens:
- After the quarter ends (usually on the last day), a meeting is held
- Everyone shares final status of all their OKR
- Discusses what worked, what didn't, and why
- Looks for patterns (for example, why do we always miss marketing OKR?)
- Team reflects on the process and themselves
Important: Retrospective is about learning, not evaluating people. OKR should NOT be tied to bonuses or terminations.
Annual Planning
Some companies (like Google under Sundar Pichai) do long-term OKR for a year, then break them into quarterly ones. This gives more strategic context. But the main cycle is still quarterly.
Grading and Learning: How Achievement is Evaluated
Scoring
At the end of the quarter, each Key Result is scored on a scale:
·1.0 — 100% achieved (required result fully obtained)
·0.7 — 70% achieved (good result, requires work)
·0.3 — 30% achieved (something done, but insufficient)
·0.0 — 0% achieved (nothing achieved)
Target OKR Score: 0.6–0.7 on average across the company. This means goals were ambitious but achievable.
Learning: Philosophy
Main Rule: OKR is NOT used to evaluate employees. If a person achieved 50% of their OKR, it doesn't mean they're a bad worker. It means:
OKR is a management tool, not an evaluation tool.
Correct Use of OKR in Evaluation:
At the end of the quarter, each Key Result is scored on a scale:
·1.0 — 100% achieved (required result fully obtained)
·0.7 — 70% achieved (good result, requires work)
·0.3 — 30% achieved (something done, but insufficient)
·0.0 — 0% achieved (nothing achieved)
Target OKR Score: 0.6–0.7 on average across the company. This means goals were ambitious but achievable.
- If the company constantly achieves 0.9+, goals are too modest
- If the company constantly gets 0.3, goals are unrealistic or the process is poor
Learning: Philosophy
Main Rule: OKR is NOT used to evaluate employees. If a person achieved 50% of their OKR, it doesn't mean they're a bad worker. It means:
- Goals were too ambitious
- Circumstances beyond their control occurred
- The approach needs to change
OKR is a management tool, not an evaluation tool.
Correct Use of OKR in Evaluation:
- OKR shows what the team achieved for the business
- But employee evaluation is a comprehensive judgment about competencies, behavior, collaboration, learning
- If a person achieved 40% of OKR but demonstrated excellent learning, helped colleagues, solved critical problems — this can be a good result
How to Implement OKR from Scratch: Step-by-Step Roadmap
Phase 0: Preparation (Week 1–2)
Step 1: Leadership Training
Step 2: Choose OKR Tool (Optional)
Step 3: Choose OKR Champion
OKR Champion is a person who:
Step 4: Prepare Communication
Phase 1: Pilot (3 Months, 1 Quarter)
Quarter 1: Pilot on One Team or Department
Recommendation: Start with one team or department that:
What to Do:
1.Week 1–2: Planning
2.Week 3–12: Cycle
Expectations from First Quarter:
·~30% achievement is normal! John Doerr writes about this in his book
What to Track:
Phase 2: Scaling (3–6 Months, Quarters 2–3)
Quarter 2: Expand to Two Teams
After the pilot, add another team (for example, Sales if Quarter 1 was Product).
What to Improve:
Expectations:
Achievement increases to 40–50%
Quarter 3: Scale to Entire Company
Now implement OKR across all teams.
What to Change:
Expectations:
Phase 3: Optimization (6–12 Months)
Quarter 4 and Beyond: Stabilize the Process
By the end of the first year:
What to Improve in Stabilization:
Roles in OKR Implementation
1. CEO / Executive Sponsor
Responsibility: Approve transition to OKR, support the process
Participation: Quarterly participation in Company OKR planning, weekly status visibility, conduct retro
Tone: Set the tone that OKR is a tool, not a weapon
2. OKR Champion (Process Owner)
Responsibility: Process management, training, deadline coordination
Participation: 20–30% of working time on OKR
Tasks:
3. Team Leads
Responsibility: Lead your team through OKR cycle
Participation: Weekly syncs, mid-quarter, retro
Tasks:
4. Individual Employee (IC — Individual Contributor)
Responsibility: Propose your OKR, work on them
Participation: Weekly check-ins, retro
Tasks:
Step 1: Leadership Training
- Read John Doerr's book "Measure What Matters"
- Watch Andy Grove's video on OKR (it's publicly available)
- Tell yourself: "We're going to change. It will be unusual, but it's worth it"
Step 2: Choose OKR Tool (Optional)
- You can start with a simple Google Sheet or Notion
- Or use specialized tools: 15Five, Lattice, Ally, People Force, Fif (migrate later)
- But it's better to first test the process on simple tools
Step 3: Choose OKR Champion
OKR Champion is a person who:
- Owns the OKR process in the company
- Trains people
- Ensures the cycle is followed
- Can be an HR leader, COO, Head of People, or even CEO in small companies
- This is a person at 20% working time (not full-time)
Step 4: Prepare Communication
- Write a letter to the team: "Next quarter we're moving to OKR. Here's what it means..."
- Explain the 4 superpowers of OKR
- Give a few examples of good OKR
- Say: "The first quarter will be experimental. Mistakes are normal"
Phase 1: Pilot (3 Months, 1 Quarter)
Quarter 1: Pilot on One Team or Department
Recommendation: Start with one team or department that:
- Is large enough (minimum 5–10 people)
- Has a clear mission
- Manager believes in OKR
- Tasks are specific enough (good for examples)
What to Do:
1.Week 1–2: Planning
- Company manager defines Company OKR for the quarter
- Pilot team defines their Team OKR
- Each team member defines Personal OKR
2.Week 3–12: Cycle
- Weekly check-ins (30 min)
- Mid-quarter review (1 hour, week 6–7)
- Quarter 2 start: retrospective
Expectations from First Quarter:
- People will confuse difference between OKR and tasks
- Some OKR will be poorly formulated
·~30% achievement is normal! John Doerr writes about this in his book
- Main goal: learn the process, not achieve results
What to Track:
- Do people see each other's OKR?
- Are there weekly check-ins?
- Are people starting to learn from mistakes?
Phase 2: Scaling (3–6 Months, Quarters 2–3)
Quarter 2: Expand to Two Teams
After the pilot, add another team (for example, Sales if Quarter 1 was Product).
What to Improve:
- OKR are better formulated (people learned from mistakes)
- Sync between teams improved
- Process is smoother
Expectations:
Achievement increases to 40–50%
Quarter 3: Scale to Entire Company
Now implement OKR across all teams.
What to Change:
- More structured planning (company-wide push)
- Best practices from pilots transferred to all teams
- Process slightly refined
Expectations:
- Achievement 50–60%
- People start seeing value of goal synchronization
- First wins (people see they're working toward one goal)
Phase 3: Optimization (6–12 Months)
Quarter 4 and Beyond: Stabilize the Process
By the end of the first year:
- OKR achievement 60–70% — this is a good metric
- People can write good OKR
- Process works smoothly
- You see results: better focus, better synchronization
What to Improve in Stabilization:
- More frequent feedback (weekly check-ins + ad-hoc syncs)
- Tie to business metrics (track how OKR affects P&L)
- Maybe transition to semi-annual + quarterly OKR (for additional strategy)
Roles in OKR Implementation
1. CEO / Executive Sponsor
Responsibility: Approve transition to OKR, support the process
Participation: Quarterly participation in Company OKR planning, weekly status visibility, conduct retro
Tone: Set the tone that OKR is a tool, not a weapon
2. OKR Champion (Process Owner)
Responsibility: Process management, training, deadline coordination
Participation: 20–30% of working time on OKR
Tasks:
- Train teams to write OKR
- Ensure planning starts on time
- Help sync OKR across teams
- Conduct retrospective, draw conclusions
3. Team Leads
Responsibility: Lead your team through OKR cycle
Participation: Weekly syncs, mid-quarter, retro
Tasks:
- Help team write good OKR
- Conduct weekly check-ins
- Support team when it's hard
- Participate in syncs with other teams
4. Individual Employee (IC — Individual Contributor)
Responsibility: Propose your OKR, work on them
Participation: Weekly check-ins, retro
Tasks:
- Write 2–3 good personal OKR
- Update status weekly
- Learn from mistakes
- Help colleagues
Ready OKR Card Template
Here's a simple template to use for documenting OKR:
``` === QUARTERLY OKR CARD ===
OWNER: [Name] DEPARTMENT: [Department] QUARTER: Q2 2026 LEVEL: [ ] Company [ ] Team [ ] Individual
OBJECTIVE (Goal) [Inspiring, concrete direction]
Context (why is this goal important?): [2–3 sentences on why this direction was chosen]
KEY RESULT 1: [Metric] Current: [Current value] Target: [Target value by quarter end] Confidence: [70%, 80%, etc.] How we'll measure: [Where do we get the data?]
KEY RESULT 2: [Metric] Current: [Current value] Target: [Target value by quarter end] Confidence: [70%, 80%, etc.] How we'll measure: [Where do we get the data?]
KEY RESULT 3: [Metric] Current: [Current value] Target: [Target value by quarter end] Confidence: [70%, 80%, etc.] How we'll measure: [Where do we get the data?]
ALIGNMENT (Which other teams' OKR are we synced with?)
[Team X OKR: ...] (we help achieve)
[Team Y OKR: ...] (they help us)
DEPENDENCIES (What people / resources do we need?)
[Dependency 1]
[Dependency 2]
WEEKLY STATUS (Updated weekly) Week 1: [Green/Yellow/Red], [Note] Week 2: [Green/Yellow/Red], [Note] ...
FINAL SCORE (filled out at quarter end) KR1: 0.6 (60% achieved) KR2: 0.8 (80% achieved) KR3: 0.4 (40% achieved) Overall OKR Score: 0.6 (60% average)
LEARNINGS (What did we learn?) [3–4 key lessons about process, ourselves, the market]
```
OKR Launch Checklist (4 Weeks)
Week 1: Preparation
[ ] CEO approved transition to OKR
[ ] OKR Champion selected
[ ] Tool selected (Google Sheet, Notion, or platform)
[ ] Leadership read John Doerr or watched Andy Grove
[ ] Letter to team about OKR transition written
Week 2: Training
[ ] Training delivered (webinar/session) for all leaders
[ ] Examples of good and bad OKR shown
[ ] Questions answered: "Is this mandatory?" "What if we don't achieve?"
[ ] Explained about transparency and that OKR does NOT affect salary
Week 3: Planning
[ ] CEO/Leadership defined 3–5 Company OKR for quarter
[ ] Each team proposed their Team OKR
[ ] Sync meetings between managers conducted
[ ] All OKR approved
[ ] OKR published in tool (everyone can see)
Week 4: Start
[ ] Kick-off meeting held (all OKR explained)
[ ] Weekly check-ins scheduled (day, time, participants)
[ ] People updated status for week 1
[ ] Mid-quarter review planned for week 6–7
[ ] CEO approved transition to OKR
[ ] OKR Champion selected
[ ] Tool selected (Google Sheet, Notion, or platform)
[ ] Leadership read John Doerr or watched Andy Grove
[ ] Letter to team about OKR transition written
Week 2: Training
[ ] Training delivered (webinar/session) for all leaders
[ ] Examples of good and bad OKR shown
[ ] Questions answered: "Is this mandatory?" "What if we don't achieve?"
[ ] Explained about transparency and that OKR does NOT affect salary
Week 3: Planning
[ ] CEO/Leadership defined 3–5 Company OKR for quarter
[ ] Each team proposed their Team OKR
[ ] Sync meetings between managers conducted
[ ] All OKR approved
[ ] OKR published in tool (everyone can see)
Week 4: Start
[ ] Kick-off meeting held (all OKR explained)
[ ] Weekly check-ins scheduled (day, time, participants)
[ ] People updated status for week 1
[ ] Mid-quarter review planned for week 6–7
Tools and Systems for OKR Management
Simple Tools (Startups, <50 People)
Pros: Cheap, simple process, can start tomorrow Cons: No automation, harder to scale, no integrations
Specialized Platforms
Pros: Automation, integrations, statistics, convenience Cons: Expensive ($10k–50k+ per year depending on company size), needs setup
Recommendation
- Google Sheets (free, simple)
- Notion (free/paid, beautiful, flexible)
- Excel (if company uses Windows)
Pros: Cheap, simple process, can start tomorrow Cons: No automation, harder to scale, no integrations
Specialized Platforms
- 15Five (focused on OKR and 1-on-1 check-ins)
- Lattice (popular in US, integrates OKR + reviews + compensation)
- Ally (focused on OKR, simple)
- People Force (Russian platform, integrates OKR and HR)
- Fif (OKR specialist with beautiful UI)
Pros: Automation, integrations, statistics, convenience Cons: Expensive ($10k–50k+ per year depending on company size), needs setup
Recommendation
- If company < 50 people: start with Google Sheets or Notion. Goal is to understand the process, not the platform.
- If company 50–500: consider moving to specialized platform (15Five, Ally, People Force).
- If company > 500: probably need a full-featured platform with integrations (Lattice, Bamboo HR + OKR integration).
Core OKR Principles (Summary Checklist)
✅ Quarterly cycles instead of annual (flexibility)
✅ Transparent OKR — everyone sees everyone's goals
✅ Ambitious goals — recommend 70% achievement
✅ Flexible — can change if irrelevant
✅ Dialogue cascading — not top-down order
✅ OKR = management tool, not evaluation — not tied to salary
✅ Weekly check-ins — real-time feedback
✅ Mid-quarter review — adaptation in the middle
✅ End-of-quarter retrospective — learning from mistakes
✅ Maximum 3–5 goals — priority > quantity
✅ Transparent OKR — everyone sees everyone's goals
✅ Ambitious goals — recommend 70% achievement
✅ Flexible — can change if irrelevant
✅ Dialogue cascading — not top-down order
✅ OKR = management tool, not evaluation — not tied to salary
✅ Weekly check-ins — real-time feedback
✅ Mid-quarter review — adaptation in the middle
✅ End-of-quarter retrospective — learning from mistakes
✅ Maximum 3–5 goals — priority > quantity
Knowing about OKRs is one thing. Implementing them effectively is quite another. You'll need patience, determination, training, and leadership support. But if you follow through, the results will be worth it.
Start with the basics: take the OKRs course: How to Implement a System of Objectives and Key Results.
