How do I use OKRs to give my team focus?

I have heard a few leaders say, “I have been asked to use OKRs, but I am not sure where to begin.” They want to do the right thing for their people, yet the request feels like another management fad. The truth is that OKRs are not a magic solution. They are simply a structure. Their power lies in how we use them to protect attention and reconnect people with purpose. A structure only creates that protection if someone actively defends it; left alone, urgent but unimportant work will always crowd out what OKRs are meant to safeguard.

The problem they are meant to solve is real. Gallup’s 2023 State of the Global Workplace survey found that only 23 percent of employees are engaged at work, and that most do not feel their work connects to a larger purpose. Gartner reports that just 22 percent of employees believe their tasks align directly with organisational goals. Without that connection, effort turns into exhaustion. People are busy, but they are not sure they are making progress. This is what makes disengagement so corrosive: it is not a lack of effort but a lack of visible payoff, and over time that gap between effort and evidence of progress is what wears people down.

OKRs, short for Objectives and Key Results, are one way of bridging this gap. They are a tool that sits in the middle. Above them is mission, the reason a team exists. Below them are the daily tasks that fill calendars and inboxes. OKRs hold the middle ground. They transform purpose into a concise set of objectives for this season, providing a clear way to determine whether progress is genuine.

Used carelessly, they become another reporting exercise. Used with care, they can give a team the clarity that most crave: what matters now, and how we will know if we are moving forward together.

Where OKRs come from

OKRs did not appear out of nowhere. Their roots go back to Peter Drucker, who in the 1950s popularised Management by Objectives. His idea was that leaders and employees should agree on a small set of goals and track progress toward them.

In the 1970s, Andy Grove, then CEO of Intel, refined this into what we now call OKRs. Grove wanted a system that balanced ambition with evidence. He encouraged teams to set bold objectives but insisted they name measurable results so they would know whether they were truly advancing.

John Doerr, a venture capitalist at Kleiner Perkins, carried OKRs into Google in the late 1990s. The young company needed discipline as it scaled, and OKRs gave a way to channel energy into focus. Since then, the practice has spread widely, from start-ups to government departments.

The structure remains simple. An Objective is a statement of what you want to achieve. It should be bold, qualitative, and inspiring. Key Results are the measures that tell you whether you are making progress. They should be specific, time-bound, and verifiable.

For example:

• Objective: Restore customer trust in our service.
• Key Results:
  • Raise satisfaction scores from 70 percent to 80 percent in 3 months.
  • Achieve 75 percent first-contact resolution.
  • Reduce repeat calls by 15 percent.

The beauty of OKRs lies in their simplicity. Yet simplicity can be deceptive.

The promise of OKRs

When OKRs are used well, they create genuine value.

They help with focus. Harvard Business Review has reported that 95 percent of employees are unaware of or confused about their company’s strategy. OKRs force teams to choose a few things that matter most, reducing the risk of dilution. This works because naming a small set of objectives makes trade-offs explicit; a team that can point to what it chose not to pursue understands its priorities far better than one that simply has a long list.

They foster alignment. In most organisations, departments compete for resources and attention. OKRs can act as connective tissue, ensuring that marketing, operations, and customer service are not working at cross-purposes. Shared visibility into each other’s objectives is what makes this possible: once teams can see how their goals interlock, coordination replaces the guesswork that usually drives silent competition for the same resources.

They build a cadence of reflection. Because OKRs are usually set quarterly, they create a rhythm of stepping back. This gives teams more opportunities to learn and adjust rather than waiting until the end of the year. Frequent, smaller course corrections are cheaper than infrequent, large ones, so this rhythm reduces the cost of being wrong about any single quarter’s plan.

They encourage stretch without fear. Grove’s principle was that OKRs should be ambitious. Achieving 70 percent of a bold target could still be considered success, because the point was to spark innovation, not to guarantee safety. Separating the size of the goal from the expectation of hitting it entirely is what makes ambition safe to attempt; people take on stretch targets only when they trust that falling short will not be treated as failure.

They offer transparency. In some organisations OKRs are shared across departments. This makes visible who is working on what, reducing duplication and creating collective accountability. Visibility changes behaviour on its own: when people know their objectives are seen by others, they are more likely to follow through, and more likely to ask for help before a goal quietly slips.

The perils of OKRs

The most common failure is too many objectives. A Deloitte study found that 61 percent of leaders admit to setting more priorities than their teams can realistically handle. When a team lists eight or ten OKRs, the focus they were meant to bring is lost. Attention is a finite resource, so a long list of objectives does not multiply focus, it divides it until each goal receives too little to move.

Another danger is top-down imposition. When OKRs are cascaded from senior leaders without conversation, they are experienced as orders rather than commitments. Ownership disappears. People commit most to goals they helped shape, so when objectives arrive fully formed, teams execute them without the discretionary effort that comes from believing the target is genuinely theirs.

A third is confusing OKRs with performance reviews. When individual bonuses or appraisals are tied too tightly to OKR achievement, people set safe goals. The spirit of stretch and learning evaporates. Research from MIT Sloan shows that linking targets directly to pay reduces creative problem solving by up to 30 percent. Once a target carries financial consequence, the incentive shifts from learning what is true to protecting what is safe, and ambition quietly gives way to self-preservation.

And perhaps the deepest danger is disconnection from purpose. OKRs that are not rooted in mission become sterile. People chase numbers without knowing why. That is when engagement drains away. A number detached from a reason people care about is just a task with extra reporting; it asks for compliance rather than commitment, and people can tell the difference.

A coaching story

I once worked with a leader of a customer service department. His team was struggling. Staff turnover was high. Customer satisfaction scores were low. People were tired and demoralised.

Senior management wanted improvement. The leader was told to introduce OKRs. He worried this would be another layer of reporting, but he also saw the need for focus.

We began with purpose. Why does customer service exist? After reflection he said, “We exist to give customers confidence that we will stand by them.” That statement became the anchor above.

From there we shaped two objectives for the next quarter. The first was to restore customer confidence. The second was to stabilise the team. Together with his staff he explored how to measure progress. They suggested satisfaction scores, first-call resolution rates, training completion, and peer support sessions.

At first, scepticism filled the room. They had seen targets before. But when they realised their own ideas were being written into the OKRs, the conversation changed. Agents began linking their daily tasks to these objectives. Calls were no longer only about speed but about building trust. Training was not a box to tick but part of stabilising the team.

Six weeks later, attrition had slowed. Customers were reporting better experiences. And the team had a new rhythm of reflection. The OKRs were not perfect, but they gave the group a shared language of focus.

Best Practices as stewardship

The real lesson is that OKRs work best when they are treated as a practice of stewardship. They are not about control or compliance. They are a way of protecting people’s energy and attention, and ensuring that their effort contributes to something that matters. Stewardship asks leaders to hold OKRs as a shared commitment rather than a set of marching orders.

Keep them few. Focus is always an act of choosing what not to pursue. A team that sets ten objectives has none. When a marketing department cut its OKRs from eight to three, they were forced to stop chasing “vanity metrics” such as impressions and instead doubled down on qualified leads. The result was not only better performance but less exhaustion. Fewer OKRs meant everyone could keep the most important goals in view, even on the busiest days. The discipline here is less about writing fewer objectives and more about having the harder conversation of what to deliberately leave out.

Connect them to purpose. Numbers alone do not inspire. An objective of “deliver five new features” is measurable but sterile. When a software team reframed their OKR to “reduce user frustration,” the metrics suddenly lived inside a story. Developers began asking customers about pain points, and small fixes that improved usability became as valued as big releases. Linking objectives to purpose reminds people that the real goal is not activity but impact. A metric attached to a story about who it helps gives people a reason to care about the number beyond simply hitting it.

Co-create them in conversation. Ownership cannot be delegated. When OKRs are cascaded from above, they land as instructions. When they are created in dialogue, they become commitments. A customer service leader I worked with invited his agents to suggest what progress would look like. They proposed measuring first-call resolution and peer support. These measures mattered to them, because they had named them. The shift from compliance to ownership was visible in the room. Authorship is what converts a target into a commitment; people defend what they helped build far more readily than what was simply handed to them.

Separate them from judgment. OKRs should be used as mirrors, not report cards. When bonuses or appraisals are tied directly to key results, people set safe goals. They stop taking risks. By holding OKRs apart from individual evaluation, leaders create space for ambition and experimentation. This is how one product team felt able to aim for doubling adoption of a new feature, knowing that if they reached only 70 percent, the learning would still be celebrated. When the cost of an honest miss is removed, people set targets based on what would genuinely matter rather than on what they are confident they can deliver.

Keep them alive. OKRs are not a quarterly ritual to complete and forget. They should form part of weekly or monthly conversations, a living agenda that guides reflection. In one operations team, the manager began each Monday huddle with a simple question: “Which OKR will your work touch this week?” This kept objectives present without turning them into a straitjacket. Reviewing progress regularly reminded people that focus is not a decision we make once, but a discipline we practise together. A goal that is only revisited quarterly has ninety days to be quietly forgotten; a short, regular touchpoint is what keeps it in view without adding the weight of a full review.

Conclusion

It is helpful to see OKRs in context. Above them sits mission, the enduring reason for being. Below them lie the daily tasks that fill calendars and inboxes. OKRs hold the middle ground. They connect purpose to focus, and they give meaning to daily work. When we confuse them with mission, they become inflated abstractions. When we confuse them with tasks, they become trivial checklists. Held in their rightful place, they provide clarity.

So how do you use OKRs to give your team focus? You begin not with the spreadsheet but with the conversation. Ask your team: what would matter most if we could only achieve two or three things in the next 90 days? Then ask: how will we know that progress is real? Write their answers down. That simple step is how ownership begins.

If OKRs are used to impose control, they will breed cynicism. If they are used as a practice of stewardship, they will spark engagement. Their value lies not in the format but in the choice to hold them as a collective commitment. For the customer service leader I worked with, OKRs were not the solution in themselves. They were the frame that allowed a better conversation to take place.

The deeper work of leadership is always the same. To protect attention. To resist overload. To make purpose visible in the midst of busyness. OKRs can help, but only if they serve that calling. Used with care, they can open a line of sight from mission to task. Used carelessly, they are just another fad. The choice is ours.

This is a continuing conversation. I would welcome your reflections, what has worked for you, and what resources have you found valuable in using OKRs to bring focus?

Questions for reflection on OKRs

To decide whether OKRs are serving your team well, you might ask yourself:

• Can every person in my team explain how their daily work connects to the objectives we’ve chosen?
• How much genuine ownership have I invited my people to take in shaping our objectives?
• Do the OKRs we set help us focus on what matters, or do they simply add to the pile of work?
• When we review our OKRs, do we leave the room with more energy, or less?
• Do our OKRs remind us of the purpose we serve, or have they slipped into being only numbers?

Further reading

1. Measure What Matters by John Doerr: This is often the go-to first book on OKRs. It covers the history of OKRs (Intel, Google), real cases, and shows how OKRs helped major organisations.
2. Radical Focus: Achieving Your Most Important Goals with Objectives and Key Results by Christina Wodtke: Offers a more narrative style, with practical examples. Good if you want a more human, story-driven sense of how OKRs work (and what can go wrong).
3. Objectives and Key Results: Driving Focus, Alignment, and Engagement with OKRs by Paul R. Niven & Ben Lamorte: More of a handbook. It includes case studies, detailed best practices, and guidance for implementing OKRs in real teams.

References

• Beer, M. and Eisenstat, R.A., 2000. The silent killers of strategy implementation and learning. Harvard Business Review, 78(5), pp.29–40. Available at: https://hbr.org/2000/05/the-silent-killers-of-strategy-implementation [Accessed 12 September 2025].
• Deloitte, 2018. 2018 Deloitte global human capital trends: The rise of the social enterprise. Deloitte Insights. Available at: https://www2.deloitte.com/insights/us/en/focus/human-capital-trends/2018/introduction.html [Accessed 12 September 2025].
• Doerr, J., 2017. Measure what matters: How Google, Bono, and the Gates Foundation rock the world with OKRs. New York: Penguin Random House.
• Gallup, 2023. State of the global workplace: 2023 report. Washington, DC: Gallup, Inc. Available at: https://www.gallup.com/workplace/349484/state-of-the-global-workplace.aspx [Accessed 12 September 2025].
• Gartner, 2022. Performance management research insights. Stamford, CT: Gartner, Inc. Available at: https://www.gartner.com/en/human-resources/topics/performance-management [Accessed 12 September 2025].
• Grove, A.S., 1995. High output management. London: Vintage.
• MIT Sloan Management Review, 2019. The problem with targets. MIT Sloan Management Review. Available at: https://sloanreview.mit.edu/article/the-problem-with-targets/ [Accessed 12 September 2025].
• Niven, P.R. and Lamorte, B., 2016. Objectives and key results: Driving focus, alignment, and engagement with OKRs. Hoboken, NJ: Wiley.
• Wodtke, C., 2016. Radical focus: Achieving your most important goals with objectives and key results. Cupertino, CA: Boxes and Arrows.