Beyond Setting Goals: Making OKRs Work in Practice

Reflections on strategic alignment, accountability, and performance

Most organizations don’t struggle because they lack goals.

Strategy, departmental priorities, and individual goals often exist side by side without a clear connection. Leaders know where the organization wants to go; teams may not know what that means for their work.

Objectives and Key Results (OKRs) can help create a shared understanding of what matters, how progress is measured, and how teams contribute.

But working with OKRs has taught me that introducing a framework is not the same as making it work. The challenge is not simply writing better goals. It is helping people understand them, collaborate around them, and keep them relevant after the initial launch.

The real work is moving from goal-setting as an annual exercise to goal management as an ongoing organizational discipline.

1. Start with the strategy—and help people understand it

Before choosing a goal-setting system, organizations need to ask why they are introducing OKRs. Are priorities getting lost between leadership and teams? Are departments pursuing competing outcomes? Is activity producing meaningful progress?

The answers should shape the approach. OKRs do not replace strategy; they help translate it into priorities that people can act on.

Leadership might begin with a few company objectives and measurable key results. Three can be a useful starting point, but there is no universal number. Leaders must be able to focus on, resource, and review what they choose.

One experience that stayed with me was achieving strong adoption in an organization-wide goal system. Yet the harder challenge was helping managers understand the strategy well enough to translate it into meaningful team goals.

A company objective may be clear to the leaders who developed it, but less obvious to managers balancing operational demands, client needs, and individual responsibilities. If managers are unclear, employees are even less likely to understand the connection.

System completion alone does not demonstrate alignment. Managers need opportunities to explore the strategy, ask questions, and discuss what they can influence.

A system can capture goals. It takes leadership conversations to create understanding.

2. Measure the outcome, not just the activity

An objective describes what we want to achieve. Key results describe how we will know we are making progress. Initiatives are the actions we take to influence those results.

Consider this illustrative example:

Objective: Create a more connected and engaging employee experience.

Possible key results:

  • Increase employee engagement favourability from 68% to 78%.
  • Improve favourable responses to recognition-related questions from 65% to 75%.
  • Increase employees’ understanding of organizational priorities from 70% to 85%.

An organization might launch a recognition program, hold employee listening sessions, or improve leadership communications to support these outcomes. Those are worthwhile initiatives, but completing them does not automatically mean the employee experience improved.

The useful question is not only “Did we deliver the program?” but “Did it make the difference we intended?”

Key results therefore need credible baselines, clear measures, timelines, and owners. They should focus on the change we want to see, rather than becoming a checklist of tasks.

The distinction also helps separate strategic improvements from ongoing responsibilities. Processing payroll accurately and serving clients reliably are essential expectations. An OKR might focus on improving payroll efficiency or reducing delivery errors—not simply restating the everyday work.

Not everything needs an OKR. Focus is more useful than an exhaustive list of responsibilities.

3. Alignment should encourage collaboration, not departmental protection

One thing I’ve observed is that leaders can agree on organizational objectives, but that agreement doesn’t always translate smoothly into departmental priorities.

Once departments define their own OKRs, they can become protective. Each focuses on its commitments without fully understanding another team’s limitations or dependencies.

Imagine a company objective to strengthen client satisfaction and retention. Client Service may focus on relationship outcomes, Operations on delivery quality, Technology on platform reliability, and People & Culture on building critical capabilities. Each contributes differently, and none can necessarily deliver the whole outcome alone.

This is why I believe department heads need to understand one another’s OKRs—not just their own.

They should be able to discuss:

  • What is each department trying to achieve, and why?
  • Which outcomes can it directly influence?
  • What limitations or dependencies might affect progress?
  • How can teams support one another if circumstances change?

These conversations should continue after goals are finalized. Priorities, resources, and plans change.

Without mutual understanding, it is easy to slip into asking which department failed to deliver. With it, leaders can work together on adjustments and solutions without creating a blame game.

Effective OKR alignment is not a rigid cascade. It is an ongoing conversation about shared outcomes, different contributions, and collective responsibility.

4. Invest in manager capability, not just employee training

Teaching employees how to write OKRs matters, but it is not enough.

Managers are the connection between strategy and everyday work. They help people identify the outcomes they can influence, question vague measures, manage competing priorities, and recognize when collaboration is needed.

They must distinguish ambition from unrealistic expectations and recognize that not everyone needs a separate OKR when individual goals can align with team priorities.

A practical manager conversation might ask:

  • What outcome are we trying to influence?
  • How will we know progress is being made?
  • What is within our control, and where do we need support?
  • What should we adjust if circumstances change?

Managers need examples, coaching, and space to practise these conversations—not just instructions for entering goals into a system.

5. Keep OKRs alive after the launch

OKRs often begin with enthusiasm. Leaders agree on priorities, goals are documented, and teams are encouraged to align their work.

Then routine work takes over.

People become absorbed in operational demands, deadlines, and client commitments. Updates become less frequent. OKRs gradually stop appearing in regular conversations and remain mostly in the system where they were entered.

Accountability can also become diluted. When nobody maintains an organization-wide perspective, people assume someone else is monitoring progress. Who is connecting dependencies, recognizing gaps, and raising the need for adjustments?

Language matters too. If the framework is unnecessarily complicated, or people cannot explain the objectives in simple terms, they are unlikely to use them to make decisions.

The answer isn’t another reporting burden. Short check-ins can fit into existing meetings, asking what has changed, what shows progress, where support is needed, and which decisions come next.

Ownership must be clear: business leaders accountable for outcomes, key-result owners maintaining progress, and someone connecting the bigger picture.

Measuring success requires looking beyond system adoption. I would consider three dimensions:

DimensionUseful question
AdoptionAre teams documenting and reviewing their OKRs?
QualityAre goals clear, measurable, outcome-focused, and aligned?
EffectivenessAre OKRs helping people collaborate, make decisions, and deliver strategic progress?

OKRs lose momentum when they become something people are expected to update rather than something they use to discuss priorities and progress.

6. Connect OKRs to performance without reducing people to percentages

One of the most important design decisions is how OKRs connect with performance management.

Imagine an employee achieves 100% of a relatively straightforward objective, while another achieves 70% of a genuinely ambitious one. Does the first employee automatically deserve a stronger performance assessment?

I don’t believe so.

A manager should consider the ambition of the objective, the effort involved, the impact achieved, and the circumstances that influenced the outcome. What was within the person’s control? How did they adapt when conditions changed? How did they collaborate and contribute?

Effort matters, but it is not a substitute for results. Equally, a difficult goal is not necessarily a well-designed one. Managers must distinguish thoughtful stretch objectives from unrealistic expectations or poor planning.

This is where manager capability and organizational culture become critical. Even with a framework, unfairness can creep in. Managers need training to understand the nuances, use evidence, discuss context, and apply judgment consistently. Calibration and open conversations can help reduce inconsistency, but no scoring formula can remove it entirely.

I would explain the relationship this way:

Progress on relevant OKRs is one source of evidence in performance and development conversations. Overall performance considers contribution, role expectations, impact, quality of work, behaviours, and circumstances. OKR attainment does not automatically determine a rating, compensation, or career outcome.

When employees believe missing a stretch objective will automatically harm their rating, they may choose safer goals instead of pursuing meaningful improvement.

For me, a 70% or 100% result should begin a performance conversation, not end it.

7. What I would do differently if I were introducing OKRs again

Looking back, I would invest more time before the new planning year. People should enter January ready to act, not still trying to understand the priorities.

Here is what I would focus on:

  1. Start earlier. For a January kickoff, I would aim to agree on company objectives by November, once strategy and approvals allow, and communicate them organization-wide in December.
  2. Use simple, shared language. An annual theme or rallying cry can make priorities memorable and help people understand their contribution. It should clarify the strategy, not replace measurable results with a slogan.
  3. Bring department heads together early. Leaders should share proposed OKRs, limitations, risks, and dependencies, then agree on mutual support before finalizing goals. That makes future adjustments easier and blame less likely.
  4. Enable managers first. Give managers practice translating strategy into outcomes, discussing dependencies, and assessing performance fairly—not just a system walkthrough.
  5. Make leadership ownership visible. Leaders should update and discuss OKRs in stand-ups, town halls, and business reviews. Named key-result owners and an organization-wide coordinator prevent progress from becoming someone else’s job.
  6. Make transparency the default. Share company and departmental OKRs across teams, except genuinely sensitive goals. Measure whether people understand priorities and their contributions—not only whether goals were entered into a system.

People & Culture can enable the framework and manager capability, but sustaining OKRs remains a leadership responsibility.

The best time to build alignment is before the year begins. The best way to sustain it is to keep the priorities visible, understandable, and open to conversation.

Final reflection: The real measure of OKR success

I still believe OKRs can be a valuable way to connect strategy with everyday work. But what I’ve learned is that their value does not come from the framework itself.

It comes from the conversations they encourage: what matters most, how teams depend on each other, what progress actually looks like, where support is needed, and when a plan must change.

Entering goals into a system is visible and easy to count. Building understanding, collaboration, accountability, and fair judgment takes more deliberate effort.

The real measure of OKR success is not how many objectives have been entered or completed. It is whether people understand the priorities, make better decisions together, and can see how their work contributes to meaningful outcomes.


The examples and numerical targets are illustrative. The reflections are generalized and do not disclose any organization’s internal goals or performance data.

AI transparency: This article was developed with assistance from ChatGPT for structuring, drafting, and editing. The perspectives reflect my professional experience and judgment.

Further reading

Leave a Reply