The problem OKRs solve: busy teams, unclear priorities
Most teams are not short of effort - they are short of agreement about what matters most. Everyone works hard on their own list, strategy lives in a slide deck, and at quarter-end nobody can say whether the important things moved. People searching for OKRs usually feel this gap: activity without alignment. Objectives and Key Results answer one question the whole team can share - what outcome are we driving this quarter, and how will we know?
What makes a good OKR
An Objective says what you want to achieve; Key Results say how you will know, in numbers with starting points and targets. A strong Objective is clear, meaningful and time-bound; strong Key Results measure outcomes rather than listing activities. Compare 'improve customer service' with 'raise customer satisfaction from 78% to 90%': the second gives the team something they can actually measure, own and review - and the starting number matters, because a target without a baseline is a wish.
Examples for Kenyan organisations
Illustrative starting points - adapt the numbers to your business. A Nairobi retail chain: make every branch somewhere customers come back to, measured by repeat-purchase rate from 22% to 30%, average checkout time under four minutes, and branch satisfaction above 4 out of 5. A SACCO: decide loans faster without raising risk, tracking approval turnaround from nine days to four, arrears steady below 5%, and mobile-application share above half. An HR team: new hires productive faster, tracking 30-60-90 onboarding completion, first-90-day resignations down, and onboarding satisfaction above 4 out of 5.
OKRs vs KPIs vs performance reviews
OKRs drive change: a few ambitious outcomes to move this quarter, then reset. KPIs monitor health: the standing numbers - revenue, uptime, arrears, satisfaction - that tell you the operation is sound. Performance reviews develop people: the conversation about an individual's growth, strengths and next steps. Many organisations run all three: KPIs keep the operation visible, OKRs move the priorities, reviews grow the people. The classic failure is grading individuals on OKR attainment - that turns an ambitious focus tool into a sandbagged target list. Keep OKRs as the team's compass and reviews as the person's conversation, and link both to the same visible record.
The cycle matters more than the wording
OKRs fail for predictable reasons: too many objectives, Key Results that are really task lists, goals disconnected from strategy, no review rhythm, and managers scoring people on attainment. A working system runs set, align, track, review, reset - few objectives, measurable key results, weekly check-ins on progress, an honest end-of-cycle review, then a fresh set. The rhythm matters as much as the wording: OKRs written once and forgotten become another document nobody opens. That is where software earns its place - one visible list, progress updating where the work happens.
■ Book a demo
Aim the whole team at what matters.
See company, team and individual goals in one visible list - with progress anyone can read.
- 3
- levels linked: company, team, individual (sample)
- 1
- visible list replacing the spreadsheet (sample)
- 0
- forced frameworks - OKRs or simple goals (sample)
Frequently asked questions
What is the difference between OKRs and KPIs?
OKRs drive change - a few ambitious outcomes to move this quarter. KPIs monitor ongoing health - the standing numbers that show the operation is sound. Most organisations run both: KPIs keep the operation visible while OKRs move what matters most.
What is the difference between OKRs and performance reviews?
OKRs are the team's compass for the quarter; reviews are the individual's conversation about growth and next steps. Avoid grading people on OKR attainment - it turns ambitious goals into sandbagged targets.
How many OKRs should a team set?
Fewer than you think: one to three objectives per team per quarter, each with two to four measurable key results. Too many objectives is the classic OKR failure - focus is the whole point.
Can goals change mid-cycle?
Yes - the cascade is flexible on purpose. Update the goal, note why, and the history stays visible so the review still reflects what really happened.
Can this replace tracking goals in Excel?
That is the most common switch: one visible list instead of a spreadsheet nobody opens, with progress updating where the work happens and check-ins starting from facts.
Do goals connect to performance reviews?
Yes - reviews start from actual goal progress, so appraisal season reflects the year's real work rather than memory. See the performance management guide for the review half of the loop.
We have never set company goals. Where do we start?
Start with one company-level objective and let teams draft theirs beneath it. AI-suggested starter goals put a first draft on the table in minutes - refine them together and launch the cycle.