OKRs Explained: How People Managers Can Create Focus, Ownership, and Better Results

Introduction

Most teams do not struggle because they lack work. They struggle because they lack focus, alignment, and a clear way to measure progress.

This is where OKRs can help.

OKRs have been used for decades. They were introduced by former Intel CEO Andy Grove and were influenced by the Management by Objectives framework, also known as MBO.

Since then, OKRs have been adopted by thousands of companies to achieve business goals and align teams around priorities and strategy. However, there are still many myths and misunderstandings around the framework. For many leaders, it is still unclear how OKRs can help their teams succeed, develop their skills, and take more ownership.

In this article, I will explain how the OKR framework works and how leaders can use it as a management tool to create real change in teams and build a result-oriented culture.

What is an OKR?

OKR stands for Objectives and Key Results.

• An objective describes what you want to achieve.
• Key results describe how you will know that the objective has been achieved.

In other words, the objective gives direction, while key results make progress measurable.

OKRs were designed to help organizations align around important goals, improve performance, and focus teams on results. They are especially useful when a company needs to operate under pressure, make trade-offs, and move in one clear direction.

One early example was Intel’s Operation Crush in 1979. Intel needed to regain momentum in the microprocessor market while facing strong competition from Motorola. The company aligned around one clear goal: win 2,000 customer designs within a year.

Intel exceeded the target and achieved almost 2,500 design wins, including the IBM PC, which helped make x86 a long-term industry standard.

This example shows the real value of OKRs. They help turn a broad business challenge into a clear objective with measurable results. Instead of leaving teams with a vague direction, OKRs create focus, alignment, and a shared understanding of success.

OKRs are useful for organizations and teams of any size. It does not matter whether you work in a company of 10,000 people or in a small startup. The goal is to have clear, motivating, and realistic objectives that help you move through uncertainty, deal with conflicting priorities, and achieve meaningful results.

What Can an Objective Focus On?

A common mistake is to think that every objective must be tied to revenue, delivery, or product metrics.

Those objectives are important, but they are not the only ones that matter. Some objectives describe direction. Some describe execution. Others focus on building the skills, ownership, and habits the team needs to succeed later.

A good objective should be self-explanatory, realistic, and motivating. It should clearly describe what you want to achieve or the direction you want to move in.

In practice, objectives often fall into four common categories.

Strategic objectives

Strategic objectives describe the direction of a company, department, or product.

Execution objectives

Execution objectives describe what you want to achieve. This can include product goals, team goals, or important milestones.

Learning objectives

Learning objectives describe what you or your team members need to learn.

Leadership objectives

Leadership objectives describe what you want to improve in the way the team works, makes decisions, takes ownership, or collaborates.

Key Results

Key results make an objective measurable. They define what progress looks like and help the team understand whether the objective has been achieved.

A good key result should be clear, measurable, and easy to evaluate. At the end of the OKR cycle, it should be possible to say whether the key result was achieved or not.

Good key results also give the team freedom in how to reach them. They should describe the result, not turn into a list of tasks. This creates space for ownership, problem-solving, and better decisions.

Key results can usually be split into three categories:

• Input-based key results measure effort or activity
• Output-based key results measure what was delivered
• Outcome-based key results measure what changed as a result of the work

1. Input-based key results

Input-based key results measure effort or activity under your direct control.

Examples:

• Send 100 emails to potential customers
• Publish 10 articles
• Complete Kubernetes training for all team members
• Document the release process for the engineering team

My recommendation: avoid using input-based key results alone. They show effort, but they do not always prove that the objective was achieved. They are usually more useful when combined with outcome-based key results.

For example, if your objective is to increase sales by 10% this quarter, sending 100 emails may help, but it does not guarantee the result. Getting 10 new customers is a much stronger signal of progress.

2. Output-based key results

Output-based key results measure what was delivered. They are usually the result of inputs, activities, and team execution.

Examples:

• Deliver the first version of a new onboarding flow
• Complete migration of 80% of services to the new platform
• Create runbooks for all critical alerts used by the on-call team
• Launch a new dashboard for tracking support and incident trends

Output-based key results are useful when delivery itself is important. However, they still do not always show whether the work created the expected impact.

For example, creating runbooks for critical alerts is useful. But the stronger question is whether those runbooks helped the team reduce recovery time, avoid repeated incidents, or improve on-call confidence.

3. Outcome-based key results

Outcome-based key results describe what changed as a result of your work. They measure impact.

Examples:

• Reduce the average age of bug and support issues to below 15 days
• Reduce average code review time to less than 1 day
• Reduce average incident recovery time from 60 minutes to 30 minutes
• Increase deployment success rate from 92% to 98%
• Reduce manual deployment steps from 8 to 2
• Increase platform adoption from 40% to 70% of engineering teams
• Reduce monthly infrastructure cost by 20%

Outcome-based key results are usually the strongest because they measure whether the work actually improved something. They help teams focus on meaningful change, not only on activity or delivery.

How to Set OKRs

Now that we understand the basic structure of OKRs, we can talk about how to set them.

The first step is alignment. Before writing objectives, you need to understand where the company is heading and how your work connects to the broader strategy.

Start by asking:

• What are the current company goals?
• What is the strategy for this quarter or year?
• What is expected from your department, product, or team?
• Which important problems are not yet covered by existing goals?
• What is within your level of responsibility?

Too many people jump into their own goals without understanding the broader context. As a result, they may work on problems that feel important locally but are not the most valuable or impactful for the organization.

In practice, different roles inside the same organization often see the same situation differently. Product, engineering, support, sales, and leadership may all have different priorities and expectations. Even people working on the same project can have different views of what matters most.

This is why alignment is so important. OKRs should not be created in isolation. They should connect your team’s work to the direction of the organization.

How to Understand Company Direction

In most companies I have worked in, strategy does not arrive as a clean OKR document for every team. You read it from signals around you.

Pay attention to what leadership keeps asking about in reviews: reliability, cost, delivery speed, customer pain. Watch what changed in the roadmap or staffing since last quarter. Notice what quietly dropped off the plan. Your manager’s 1-2-1s are often the most useful signal, because that is where direction gets translated into expectations for your team.

If you work at a public company, read the investor reports. They spell out promises to the market, strategic priorities, and the next targets leadership is under pressure to hit.

Before you finalize team OKRs, ask a simple test: would my director recognize this as a priority? OKRs that look impressive locally but fail that test are misaligned, no matter how well written they are.

Keep Focus

I often see teams copy last quarter’s OKRs, add two more, and call it focus. That is not focus. That is a backlog dressed up as strategy.

I keep teams to 3 to 5 objectives per cycle because it forces a real trade-off conversation. You cannot treat reliability work, a platform migration, and a major feature push as three equal top priorities. Something has to lead. Something has to wait.

Part of your job as a people manager is to protect the team’s attention. The goal is not to maximize the OKR count. The goal is to make the team’s priorities legible enough that everyone can say no to good work that does not fit the cycle.

Setting OKRs for Your Team

Before setting team OKRs, the team should first discuss what matters most.

Useful questions to start with:

• What are the most important outcomes we need to achieve?
• What would create the most value for our customers?
• What problems are blocking our team, product, or customers?
• What should improve by the end of the cycle?
• What should the team learn?
• Where do we need more ownership?
• What should we stop doing because it does not support our goals?

Team OKRs should not be created by the people manager alone. If the objectives belong to the team, team members must be part of defining them.

The team should help propose goals, challenge priorities, share their view of current problems, and discuss what they can realistically commit to. This does not mean that every personal goal becomes a team OKR. It means that the team understands the direction, sees the trade-offs, and has a real voice in shaping the goals.

Commitment is one of the key parts of OKRs. People are more likely to take ownership when they understand why the goals matter, how they connect to the broader strategy, and what role they play in achieving them.

The role of the people manager is to bring context, explain the direction, create space for discussion, and help the team turn ideas into clear objectives and measurable key results.

Good OKRs should create clarity, ownership, and commitment. They should not become another management process that the team follows without belief.

OKR Cycle

The failure mode I see most often: OKRs get written in week one, filed away, and opened again at quarter-end for a rating conversation. That turns the framework into paperwork.

I run OKRs as a management rhythm, not a one-time planning exercise. At the start of the cycle, the team sets OKRs together. During the cycle, I touch them in regular 1-2-1s. I do not schedule a separate OKR meeting unless something is stuck. We discuss progress, blockers, and trade-offs in conversations that would happen anyway.

Mid-cycle, I revisit key results that are clearly wrong or no longer relevant. Changing a key result is not failure. It means the team learned something early enough to adjust.

At the end of the cycle, we review outcomes and lessons, not just checkbox completion. The point is to surface trade-offs early, give feedback tied to results rather than tasks, and leave the next cycle sharper than the last one.

Giving Feedback and Keeping Motivation High

OKRs can also help managers give better feedback.

If an OKR appears only during a quarterly review, it is already too late to use it for feedback.

Instead of only discussing tasks, you can discuss progress, ownership, decisions, and outcomes. This makes 1-2-1s more useful and connected to professional growth.

Regular 1-2-1s can help you understand:

• Is the person clear on their goals?
• Are they blocked?
• Do they need support?
• Are they growing in the right direction?
• Are they motivated by the work?
• Do they understand how their contribution connects to the bigger picture?

It is also important to appreciate progress, not only final results. Some OKRs are ambitious, and not every key result will be fully achieved. What matters is whether the team learned, improved, and moved in the right direction.

What Not to Track

Not everything should become an OKR.

Avoid tracking things that are too small, too obvious, or too disconnected from real outcomes.

You usually do not need OKRs for:

• Regular Jira tasks
• Routine meetings
• Basic responsibilities of the role
• Work that does not create a clear change
• Metrics that people cannot influence
• Activities that measure effort but not impact

A good OKR should help people focus. If it creates noise, confusion, or fake progress, it is probably not a good OKR.

Summary

Most teams do not need more goals. They need fewer priorities, a shared definition of success, and a way to tell whether progress is real.

An objective gives direction. Key results make that direction measurable. Teams can stay busy shipping features, closing tickets, and running meetings without improving anything customers or the business actually feel.

Strong OKRs start with alignment. Before you write objectives, understand company direction and how your team’s work connects to it. Write key results that describe change, not just effort. Outcome-based results are usually the strongest signal. Input-only metrics often show activity without proof. Team OKRs should be shaped with the team, not handed down. When people understand why a goal matters and what they are committing to, ownership follows.

OKRs work as a living management tool. Review them during the cycle. Discuss blockers, trade-offs, and progress in 1-2-1s. Do not turn routine tasks, basic job responsibilities, or unfocused activity into OKRs. Used well, OKRs create clarity and commitment. Used as paperwork, they create noise.

Sources

• What Matters: OKRs Explained
• What Matters: Operation Crush
• George T. Doran: “There’s a S.M.A.R.T. Way to Write Management’s Goals and Objectives”
• Mooncamp: Management by Objectives