OKR is a goal management framework that turns strategy into everyday action. The acronym stands for Objectives and Key Results. The idea is simple: an organization picks a handful of ambitious objectives for the quarter, defines 2–5 measurable key results for each, and reviews them weekly so the whole organization moves in the same direction.
By Henri Sora, founder, Sora Consulting · Published 25 April 2026, updated 19 August 2026 · 12 min read
Sounds easy? In practice, getting OKRs to work takes a surprising amount of effort, because it is a change management project like any other. We have covered the topic extensively with Juuso Hämäläinen in our book Strategia arkeen OKR-mallilla, and writing it was only possible because we had seen both successful and failed adoptions. This article is a summary and an extension of what those projects have taught us.
If you are looking for a quick definition, read the next section. If you want to understand why most OKR adoptions stumble into the same valley of death and how to get across it, read all the way through. The article also serves as a table of contents: each main heading leads to its own topic, and you can jump straight to the one that interests you most.
Most organizations have a great strategy. Yet research and experience keep repeating the same observation: crossing the execution gap is hard.
The strategy is born in a leadership team offsite, ends up in PowerPoint and Confluence, and then begins a slow, almost invisible drift back toward normal everyday work where only urgent things get done. Halfway through the quarter, there is bewilderment in the air: where did that focus go again?
The problem is called the execution gap. Inside it are recognizable symptoms:
Teams do not know what to focus on: the calendar fills up with unmissable but irrelevant meetings.
Goals exist, but they are hidden in the HR system, opened only once a year.
Leadership and the field do not meet in conversation: leadership thinks it has communicated, the field disagrees.
Metrics report on the past, not the future: by the time the situation is noticed, fixing it is already too late.
New change projects are started faster than old ones can be finished.
OKR is one of the most serious answers to this very problem. It is not a marketing trick or a new acronym for the HR toolkit. It is a combination of a few clear structural choices whose combination forces the organization to do things it does not naturally do: limit the points of focus, communicate the choices transparently, and check direction weekly so densely that the course can be corrected before it is too late.
If you have a great strategy but everyday work does not bend to match it, OKR is designed precisely for this.
In Finnish, this phenomenon is called strategian jalkautus, strategian toimeenpano, or strategian eläminen todeksi. Each phrase has its own nuance, but the idea is the same: getting strategy into everyday work so the entire organization has a chance to execute it.
OKR (Objectives and Key Results) is a goal management framework where an organization sets a few clear, inspiring objectives and measures their progress with 2–5 numerically tracked key results in quarterly cycles. Objectives and key results are visible to everyone, they are updated weekly, and outcomes are reviewed in a retrospective at the end of the quarter.
OKR differs from traditional goal frameworks in four ways:
Focus: there are only a few objectives, because focus is the core of the whole model.
Transparency: all objectives are public inside the organization.
Stretch: objectives are deliberately set at a level where 70% completion is considered good performance.
Team involvement: teams shape their own objectives, leadership does not pre-define them for everyone.
This combination makes OKR a tool that, when implemented correctly, narrows the execution gap described above. The OKR model is designed precisely to solve this problem.
The basic rhythm of the model is simple: plan for the quarter, follow up weekly, reflect at the end of the quarter, repeat. But as is almost always the case with simple models, the hardest part is getting the whole organization to do a simple thing with discipline over a long stretch of time.
OKR consists of three levels. Separating them from each other is one of the most common places organizations struggle when they start using OKR.
The objective tells what you want to achieve and why it matters. A good objective is inspiring, destination-focused, and qualitative. That is, it is verbal, not numerical. It must be so clear that a person grasps it and lights up. A good test is to imagine saying the objective aloud in the morning meeting with a slight feeling of pride.
Good examples of objectives:
“Conquer the American market.”
“We are Finland’s most wanted employer.”
“Our customers trust the way we operate.”
“Our online store is number one.”
“Outstanding customer experience from the first contact.”
Bad examples, even if they feel right:
“Revenue grows by 20%.” (This is a key result, not an objective.)
“We adopt a new CRM system.” (This is a task, not an objective.)
“We improve customer satisfaction.” (Too loose.)
Word choice determines whether an objective sticks. Vivid, punchy language stays in the organization's everyday talk. Bureaucratic or jargon-heavy objectives are forgotten within the same week. One of the most effective objectives we have seen was the two-word “Assists for Sales.” Once the ice-hockey analogy behind it was explained across the organization, no one was left unsure about the desired behavior, and the phrase quickly became hallway shorthand.
A word of caution on humor and wordplay. OKR objectives get read in weekly meetings, on slides and in internal communications, and the register of humor varies from reader to reader. In one workshop, a team first chose “100 new sekakäyttäjää” as a key result (the aim was to grow the number of customers using the software in several different ways). In Finnish the term reads two ways: as multi-mode users, which the team meant, and, in slang, as poly-drug users, which they did not. The phrasing worked in the workshop moment, but the double meaning would not have landed well in wider internal communications. The final version became “100 new monikäyttäjää,” which conveys the same meaning without the second reading. Some semantic acrobatics, yes, but handled with care.
A key result tells how progress toward an objective is measured. Good key results are outcome-focused, numerical and verifiable. There are 2–5 per objective. If you have only one, the objective probably is not a real objective. If you have more than five, focus is lost.
A useful litmus test: a key result must be such that the team can honestly say at the end of the quarter, “we achieved 73% of this.” If the answer requires interpretation, the key result is not numerical enough.
Examples of good key results for the objective “Conquer the American market”:
10 potential American distributors in our pipeline.
3 signed letters of intent.
Marketing site translated and live, 5,000 monthly visitors.
Notice that key results are not tasks. They are outcomes. Tasks come next.
Tasks are the actions through which the team moves key results forward. They are concrete, owned by one person, and have a deadline. Tasks are not OKRs, but they are the bridge by which OKRs are realized in everyday work.
The team plans tasks weekly: which actions this week move which key result forward? The work itself does not change. What changes is the focus on prioritizing it.
It is easier to understand the model with an example. Take a 40-person SaaS company whose strategy is to grow internationally in Northern Europe.
Company-level objective: We are the most wanted SaaS partner in the Nordics for medium-sized industrial companies.
Key results: - 8 new customer agreements in the Nordics, of which at least 3 outside Finland. - Net revenue retention 110%. - 50 qualified sales conversations in Q3.
Sales team’s objective (supporting the company-level objective): We turn Nordic interest into customer agreements.
Key results: - 30 qualified meetings booked in Sweden and Denmark. - Win rate from qualified meeting to agreement 25%. - Average sales cycle below 75 days.
Marketing team’s objective: We make Nordic decision-makers see us as the obvious choice.
Key results: - 4 published industry-targeted case stories. - LinkedIn followers in the target group +30%. - Webinar series gathers 200 qualified attendees.
You can see that the objectives are connected: the marketing team works for the same end as the sales team and the company level, but with its own specific objective and its own measurable key results. This is what we mean when we say the OKR model aligns the organization in the same direction.
OKR is not a trend. Companies and public sector organizations adopt OKR for concrete reasons. Here are the most common ones we have seen in our own projects.
Focus that actually holds: an organization can have at most a handful of priorities at the same time, and OKR forces this choice every quarter. No more “everything is important.”
Strategy becomes visible to the field: when objectives are public, everyone can see how the strategy is translated into team-level work. Strategy stops being a leadership team’s secret.
Weekly rhythm beats annual rhythm: weekly reviews mean that a problem at the start of the quarter does not need to mature into a crisis by quarter-end. Direction is corrected in real time.
Confidence levels show problems early: when teams assess the likelihood of reaching each key result, drops in confidence become an early warning, not after-the-fact reporting.
The leadership team gets visibility without micromanagement: a monthly snapshot built by the OKR Lead replaces the “let me jump into the team’s work” instinct. Leaders see what they need to see, without intervening.
Engagement grows from participation: when teams set their own objectives, they own them. Top-down assigned goals create the opposite effect.
The model is cross-functional: OKR works the same way for finance, sales, IT and people operations. It is not a department-specific framework, which is why coherence is built across the whole organization.
These benefits do not appear in the first quarter. They emerge gradually as the discipline becomes habit. The first quarter usually feels rough. The second is already noticeably easier. By the fourth quarter, the model is part of how the organization operates.
A common confusion: are OKRs and KPIs the same thing? They are not. The clearest analogy: KPI is the speedometer of a car, OKR is the navigator.
KPIs describe the operational state of the business. Revenue, customer satisfaction, retention, conversion rates. They report on what is, and they should be monitored continuously. KPIs do not change with the quarter.
OKRs describe what we want to achieve next that is different from today. They are time-bound by their nature. They expire when the quarter ends.
The same metric can serve both purposes, but its role differs. Revenue as a KPI (“we monitor revenue continuously”) is different from revenue as a key result (“in Q3 we grow Nordic revenue from 1M to 1.5M”). The first one reports a state. The second one drives a change.
Many organizations think they are doing OKR when they have just renamed their KPIs. That is the most common pitfall in adoption. If your “OKRs” do not change between quarters, they are not OKRs. They are KPIs in a new dress.
The OKR model has three time horizons that work in concert.
Once a year (typically in the autumn) leadership formulates company-wide annual objectives, derived from the strategy. These are the highest-level objectives that guide everything that follows. They are usually 3–5 in number, big in scope, and may stretch into multi-year work.
The quarter is the heart of the OKR model. Each quarter, every team formulates 2–4 objectives with 2–5 key results each, supporting the annual objectives and the company-wide direction. The quarter begins with a planning workshop, and at the end of the quarter the team holds a retrospective, where it assesses what was achieved and what was learned.
The quarter is short enough that even ambitious objectives become tangible, and long enough that something meaningful can be achieved within it.
Once a week the team holds an OKR check-in, lasting about 30 minutes. The team:
Updates confidence levels for each key result.
Discusses what blocks progress, and how to remove the blocks.
Plans the next week’s tasks.
Decides what to bring up to leadership if necessary.
This weekly rhythm is the model’s most distinctive feature. Without it, OKR becomes a quarterly planning theatre with no real-time correction.
OKR adoptions often fail in the same places. The most common misunderstandings are surprisingly consistent. We have written about them separately in detail, but the most common ones are: confusing OKRs with KPIs, treating them as a performance management tool, setting too many objectives at once, and failing to set up the weekly rhythm.
Between quarters 1 and 3 of adoption lies a stretch we call the valley of death. The initial enthusiasm has cooled. People notice that this takes more discipline than was promised. Some teams have great quarters, others lose the rhythm. Senior leadership starts asking: is this still working?
This is the moment when most OKR adoptions either deepen or are abandoned. The difference between organizations that come out the other side and those that don’t comes down to six things: a clear OKR Lead role, leadership team’s own functioning OKR rituals, manager training, software support, transparent metrics about adoption progress, and consistent communication about why this matters.
When all six are in place, the second year delivers what was promised. When even two are missing, the model usually fades into existence-without-impact.
Before adopting OKR, ensure:
The strategy is clear enough to derive objectives from. If the strategy is “be better at everything,” no OKR will save it.
The leadership team is willing to lead by example. If the leadership team does not run its own OKR check-ins, no team below will either.
An OKR Lead has been named. This is the role that holds the model together at the organization-wide level. We have written a separate article about this role.
The team has weekly time for a check-in. Half an hour is not a lot, but it must be defended on the calendar.
Patience for at least a year. Real benefits emerge only by quarter 3 or 4. The first one is mostly learning.
If any of these is missing, fix it before adoption. Adopting on top of an unstable foundation produces the worst possible outcome: a half-implemented model that everyone has lost faith in.
The OKR model originated at Intel in the 1970s. Andy Grove developed it as a successor to Peter Drucker’s Management by Objectives. From Intel, OKR moved to Google in 1999 through John Doerr, who worked as a venture investor and brought the model to the Google founders. Google scaled the model to tens of thousands of people, and the model became known publicly through Doerr’s book Measure What Matters in 2018.
In Finland, OKR has been used since the early 2010s in tech companies, and over the past five years it has spread to industry, finance, healthcare and the public sector. Today there are several OKR practitioners in Finland, both as adopting organizations and as consultants.
Typically 12–18 months until the model genuinely settles in. The first quarter is rough, the second already lighter. By quarter 4, the model is starting to be part of how the organization works. Major benefits become visible in the second year.
MBO is OKR’s predecessor. The biggest differences: OKR has a shorter cycle (quarter vs. year), transparency is built in (everyone sees everyone’s OKRs), key results are explicitly numerical, and OKRs are not directly tied to compensation. The last point is the most important: separating OKR from compensation is what allows objectives to be ambitious without people lowering them defensively.
No. This is the single most damaging mistake organizations make with OKR. When the model rewards reaching targets, people learn to set lower targets. The model loses its stretch property and becomes a sandbagging mechanism. Use OKRs for direction and learning, not for compensation.
The OKR Lead is the person whose main job is keeping the OKR model alive at the organization-wide level. The role coordinates the leadership team’s own OKR rituals, prepares the monthly snapshot, runs quarterly retrospectives, and supports OKR Champions in teams. We have written a separate article about this role.
Clear signals are: weekly meetings start to slip, confidence levels are not updated, objectives are left to gather dust at the bottom of Excel, and nothing new is learned in the quarterly retro. When these start to appear, you are in the valley of death, and the diagnostic above will tell you which of the six missing pieces to grab.
Yes, but simplified. A team of under 20 people can keep the whole OKR model at one level: company-wide objectives and key results where every team member knows their own role. A separate team level is not needed until there are several teams.
A confidence level is a numerical estimate by the key result’s owner of how likely it is that the key result will be achieved by the end of the quarter. It is updated before the weekly check-in. Its job is to make problems visible before they become catastrophes: if the value drops significantly in one week, something is wrong, and it should be discussed immediately.
OKR is not a budget, and it does not replace budgeting. But the two talk to each other. Well-set OKR objectives guide how the resources inside the budget are prioritized. If the quarter’s OKR objective is upselling, the extra euros from sales and marketing flow under it, not evenly across everything else.
As a rule, this is not worth doing. The OKR model’s central power is calm: the whole organization knows what to focus on this quarter, and new urgent priorities do not drop into the calendar weekly. Only in truly exceptional situations such as a market crisis, a major external event, or a strategic shift in direction, should quarterly objectives be reopened. Otherwise the model loses its power.
OKR is not a fad, and it is not consultant speak. It is a disciplined way to do three things that most organizations do poorly: choose what to focus on at any one time, communicate the choice transparently, and follow progress on a weekly basis so that direction can be corrected in time.
Learning the model takes time. Adoption goes through a valley of death. But in Finland and around the world it has proven to be one of the most significant individual things a leader can do to close the execution gap: that perennial problem where a fine strategy does not turn into results.
We have been involved in OKR adoptions both in board roles and in consulting, and the journey has included projects that flourished from the first quarter onward and projects that had to be restarted multiple times. The common denominator of successful ones has always been the same: real commitment from leadership, patience to practice, and the discipline to hold weekly check-ins even when things are busy.
When these are in place, the OKR model keeps its promise. Time and again.
Want to discuss how the OKR model would work in your organization? Get in touch and we will walk through your situation together.
A thesis: a role with many names but one shared task.
Mare's article about the single most important role in OKR adoption.
Certification training for the organization's internal OKR lead.