Some goals sound so good that no one objects.
“We want to become more efficient.”
“We want to collaborate better.”
“We want to implement our strategy more consistently.”
At first glance, this seems clear. But in everyday practice, things start to get fuzzy. What does “more efficient” actually mean? Which aspects of collaboration need to change? How does a team know it’s driving the strategy forward?
That’s exactly where OKRs come into their own.
Objectives and Key Results bring goals from the presentation into the work. They force an organization to link direction and progress. That sounds technical. In practice, it’s a pretty honest test: Does a goal lead to different decisions? Or does it remain just nice words?
This question is central to transformation. Change needs direction. It also needs measurable indicators of whether movement toward the desired future is already taking place.
The Gap Between Goals and Action
In organizations, there is often a disconnect between strategy and day-to-day operations. A goal is set at the top. At the bottom, that goal must be translated into action.
This transition is delicate.
A goal like “increase efficiency” can mean many things. Shorter turnaround times. Less coordination. Clearer priorities. Less effort spent in the wrong places.
As long as this translation is missing, the goal remains vague. Teams can be busy and still work at cross-purposes. Leaders can expect progress without it being clear what kind of progress is meant.
OKRs bring this fog into the light.
They make it clear which goal matters right now and which results are relevant to it. This makes goal-oriented work more concrete. And more uncomfortable. Because measurable Key Results show whether the direction is working in day-to-day practice.
The Wrong Start
OKRs lose their power when they’re used as a new template for old goal-setting.
Then a project becomes an Objective. Tasks become Key Results. Review meetings become status updates with a new label.
The method then appears to have been implemented. Its actual impact remains weak.
OKRs are meant to transform goal-setting discussions. The central question is: Which result shows that our work is making an impact?
This question shifts the focus. Away from mere activity. Toward progress.
That is precisely what makes OKRs interesting for transformation. Change rarely thrives on simply doing more work. It thrives on the fact that the right work produces visible results.
Why a bottom-up approach is crucial
Kelly explains that OKRs should be set using a bottom-up approach. Teams should define their own OKRs and link them to the overarching goals. Leaders formulate the ultimate goal, draft a vision, and outline the desired future. Teams then determine how they can contribute to this (see Kelly 2023: 10).
This is more than just a methodological nuance.
Leadership provides direction. Teams bring the reality of the work to the table. Together, these elements create a system of goals that becomes actionable.
When teams develop their own OKRs, they clarify their contribution to the desired future. This makes strategy more tangible. Responsibility shifts closer to the work.
“Bottom-up” means here: The organization leverages the knowledge of the people who know the day-to-day work. When formulating an Objective, you must clarify the direction. When defining Key Results, you must specify how progress will be measured.
This requires more than just clear wording. It requires a common language for measuring impact.
Why Language Matters in Implementation
Before OKRs are introduced, employees need a shared understanding of the method. Training and communication are therefore essential.
The terminology must be clear. An Objective is a target vision. A Key Result is a measurable outcome indicator. A Review is a learning opportunity.
This distinction changes the quality of the conversations. Teams then talk less about completed tasks and more about visible change.
This is precisely where the real work with OKRs begins. The method demands precision.
Why pilot projects help
Starting with pilot projects can be a good approach. This allows an organization to gain initial experience and develop appropriate practices before rolling out OKRs more widely.
This prevents the method from becoming a mere facade.
After all, OKRs look simple on slides. In practice, however, it becomes clear just how challenging it is to set good goals. Objectives can quickly become too broad. Key Results can quickly devolve into mere activity tracking. Reviews can quickly turn into reporting exercises.
A pilot project reveals these patterns early on. Teams can learn which phrasing works and what rhythm suits their work.
This is valuable for transformation. The organization tests the method on real work and identifies where adjustments are needed.
Why Reviews Set the Pace
OKRs require regular review. Reviews and feedback help measure progress, identify problems early, and make adjustments.
Without this rhythm, OKRs quickly become static.
A goal formulated at the start of a cycle and rarely revisited thereafter loses its impact in day-to-day operations. Reviews bring it back into the workflow.
They show whether Key Results are making progress visible. They also reveal whether the organization needs to adjust its assumptions.
This is particularly relevant in transformation efforts. Change generates new information. Reviews ensure that this information is incorporated into decision-making.
In this way, OKRs become a rhythm for learning.
Leadership must be visible
Managers should actively use OKRs and share their goals and progress. This fosters accountability. Employees see that management stands behind the method.
This is a sensitive point.
If leadership introduces OKRs but rarely works with them visibly themselves, the method quickly loses credibility. Then it appears to be a tool for teams. Actual leadership remains on the sidelines.
Effective OKR work requires visible leadership. Leaders demonstrate which Objectives they are pursuing. They make progress transparent. They also discuss missed Key Results and derive adjustments from them.
This turns OKR work into leadership work. Goals are managed, reviewed, and refined.
Adapting to the Culture
The OKR methodology should be adapted to the specific needs and culture of the respective organization. Flexibility in implementation helps ensure the method is used effectively and sustainably.
This means: OKRs need to be adapted.
An organization with formal decision-making processes starts differently than a division with agile experience. A team with little experience in goal-setting needs different support than a team that already works in a results-oriented manner.
The core of the method should remain clear. Objectives provide direction. Key Results make progress measurable. Reviews create opportunities for learning.
If this core foundation is solid, implementation can align with the organization’s needs.
Our Impact
Our contribution lies in translating OKRs from methodological theory into effective leadership practice.
To do this, organizations need a clear goal architecture. They need routines that make progress visible. And they need leaders who can work with results.
We support organizations in implementing OKRs in a way that concretely supports transformation. The focus is on the connection between strategic direction and daily work.
This involves questions that create pressure in practice: Which goals truly guide the organization? Which Key Results demonstrate the quality of outcomes? Where does the method create clarity? Where does it create additional effort?
These are the points where it is decided whether OKRs provide guidance or merely introduce new terminology.
What Remains
OKRs can help organizations define goals more clearly and make progress measurable. They can support teamwork because teams can more concretely determine their contribution to the strategic direction.
The benefits arise from active application. Training, pilot projects, regular reviews, and visible leadership by example are therefore part of the implementation process.
For transformation, the strength of OKRs lies in their ability to translate vision into action. A target vision becomes verifiable work. Strategy becomes a conversation about progress. It is precisely this conversation that makes the difference between a goal that sounds good and a goal that actually changes the way we work.
Sources:
- Kelly, A. (2023): Succeeding with OKRs in Agile: how to create & deliver Objectives and Key Results for teams. 2nd edition. Leanpub
- Praz (2022): Link Technology to your Longterm Business Goals, How to use Technology to Mobilize your people, strategy and operations. Apress
