March 2026
Background to the failure of classic OKR systems and strategies for contemporary leadership with orientation and radical focus on the essentials.
OKRs have an alluring charm. They are clearly structured, methodically manageable and promise exactly what many organizations are looking for: to translate strategy into concrete goals and measurable impact. For management, that sounds like focus and control. For employees, for clarity, orientation and, in the best case, more self-determination.
OKRs (Objectives and Key Results) are a framework for translating strategy into concrete goals. Objectives set the course, key results make progress measurable. The idea behind it: Organizations focus on a few important goals — and regularly review progress.
Hardly any management framework in recent years has been so broadly adopted — and hardly any causes so much disillusionment in practice. Studies and benchmarks repeatedly show a similar picture: The majority of OKR implementations fall short of expectations and don't deliver the performance improvements you'd hoped for. Another value is even more obvious: Over 40% of organisations that start with OKRs abandon the framework within the first six months or use it only half-heartedly1.
If you’ve already had experience with OKRs, this certainly sounds familiar. Perhaps the introduction was accompanied by a spirit of optimism. Perhaps there were ambitious goals on the slides. And maybe after some time, there was a feeling that the method didn't quite fit in with your organisation, or created more effort and friction in everyday life than orientation.
This raises a key question: Is the problem with the OKRs themselves — or with the way they are embedded in existing structures, management logics, and cultural patterns?
OKRs aren't a new buzzword. Their roots lie in Silicon Valley and were strongly influenced by American management culture: technology-driven growth companies, a high level of transparency, a clear sense of responsibility, a strong willingness to take risks and a natural approach to ambitious goals that are not expected to be fully achieved. In this environment, OKRs were able to fully develop their strength.
However, many SMEs operate in a different organisational context. Structures have grown, hierarchies are often more stable, and culture is created from relationships instead of scalable playbooks. At the same time, the environment today is dynamic and requires constant adjustment. The logic of OKRs remains convincing, but their effectiveness depends on how well they fit the organisation’s operating system.
It would therefore be too short-sighted to question the entire concept. When used correctly, OKRs can be extremely clear and effective. What is decisive, however, is how they are designed — and whether they fit the real working environment and culture of a company.
In the following, we take a differentiated look at the most common reasons why OKRs fail in practice — and what organisations can do differently to actually meet expectations.
Many companies start with good intentions: “We need alignment, so we cascade the goals down.” Sounds logical. In practice, however, this often results in a multi-stage translation process using an organisational chart, and with each stage, the strategic signal weakens. Business goals become departmental goals, team goals, and individual tasks. What was intended as orientation often ends up as implicit control.
Goal cascading is, therefore, often an elegant form of micromanagement. Behind this lies the concern that teams might be working on the “wrong” things. So you define more precisely, break down further, and make it more concrete. But this is exactly what causes the opposite of empowerment: People work through goals instead of taking responsibility for impact.
If we want employees to work on the right topics — and think for themselves — there is no need to cascade goals rigidly throughout the organisation. It needs clarity about purpose and priorities. Alignment is not achieved through intervention, but through a shared understanding of why something counts.
The basic idea of OKRs is impressively clear: Objectives describe the direction we want to achieve, and key results make this ambition tangible through measurable outcomes. It is precisely this combination of purpose and measurability that makes the framework so strong.
And at the same time, there is a trap here.
Because key results should be measurable, they often slip into output logic in practice. They are then called “Launch Feature X,” “Relaunch website,” or “Implement ten campaigns.” All useful activities — but just activities. They show what has been done, not what has improved as a result.
A typical example: An SME with 35 employees defines “website relaunch in Q2” as a key result. Three months later, the website is live — but the conversion remains unchanged.
This creates to-do lists with a strategic twist. What is easy to count is measured — not necessarily what really counts. Describing the desired effect without prescribing the solution is much more important. Otherwise, key results become checklists — and OKRs lose their actual purpose: to control impact instead of activity.
OKRs are often tied to fixed cycles — usually to the quarter. That is understandable: 90 days seem manageable, sufficiently agile and yet predictable. The rhythm provides structure and creates a common beat.
However, the problem is not the cycle itself, but its rigidity.
Many initiatives that really move SMEs forward cannot be neatly cut into quarters. Product developments take longer, and market changes happen faster. And sometimes, after a few weeks, the initial situation changes fundamentally — not because of poor planning, but because reality is dynamic.
When work is squeezed into tight time boxes often formulate goals that fit well into the calendar — not necessarily the ones with the biggest impact. The cycle is beginning to dominate the choice of goals.
An effective OKR system therefore, adapts its rhythm to the work environment. The goals of a production company follow different cycles than those of a software team. Focus is not created by rigid quarters, but by a rhythm that matches the actual achievement of goals.
OKRs promise measurability. But not everything that can be counted is strategically relevant — and not everything strategic can be neatly squeezed into a number.
In practice, a form of pseudo-measurability quickly develops. Key results are precise because they contain percentages and key figures. But numbers often measure activity rather than impact. They communicate progress, even if they say little about whether anything has actually improved. The system is data-driven — but the content remains superficial.
The rhythm of check-ins is similarly ambivalent. Studies clearly show that regular, in particular weekly, goal meetings significantly increase the success rate2. The exchange brings new insights, makes obstacles visible and creates momentum.
But this exact ritual often turns into the opposite. The weekly update becomes a mandatory exercise: Figures are entered, status reported, fields filled — even without progress. This creates a reporting cycle instead of a learning system. Impact is created in a conversation, not in a reporting form.
OKRs lose their power as soon as they become political — especially when they are linked to performance, bonuses or individual evaluation.
At that moment, behaviour changes. The safe space for ambitious goals is disappearing. Teams formulate more defensive goals, avoid stretch and hedge risks. Instead of maximising impact, they optimise for goal achievement rates. 60% goal achievement is then no longer understood as a learning signal, but as a flaw.
That exactly contradicts the logic behind OKRs. Motivational research shows that commitment occurs particularly when people experience autonomy and feel that they can act effectively. However, when goals are used as an assessment tool, the focus shifts: People are no longer working on the boldest goal, but the safest.
Many well-managed companies — and yes, this includes Swiss SMEs — aim to set things up cleanly and professionally. That is a strength. With OKRs, however, it can become a trap.
The introduction often begins with external consultants, extensive workshops and detailed coordination rounds. Templates, scoring models and governance loops are created. Objectives are fine-tuned across teams, dependencies are mapped, and formulations are perfected. The ambition: a perfectly engineered system.
But with every additional layer, the effort increases — especially for managers. Planning, coordination, reporting and maintenance become a parallel operating system alongside the actual business. OKRs should create focus, but start to attract attention themselves.
If a framework costs more energy than it releases, it loses acceptance. It then becomes an admin process instead of an orientation.
Experience shows that less is often more — especially when introduced. OKRs are intended as an agile learning system, not as a governance machine. Impact comes from clarity and cadence, not from process perfection.
OKRs don't lose their effect because the idea is wrong.
They lose their effect when they are incorporated into a system that contradicts them.
What runs through all points:
• Alignment is not created by cascading, but by shared understanding.
• Ownership does not come from allocation, but from participation, autonomy and purpose.
• Impact does not come from output measurement, but from meaningful outcomes.
• Progress is not achieved through reporting, but through real exchange.
• Agility does not come from fixed quarters, but from appropriate rhythms.
• Focus does not come from process perfection, but from clarity.
What does this mean specifically for SMEs?
There is no need for a perfected OKR system that becomes a second burden in day-to-day work.
No rigid governance that suppresses ownership and personal responsibility.
Not a complex set of rules that creates the illusion of transparency, while a shared understanding of what truly matters gets lost.
All you need is focus.
Focus on the few topics that really matter right now.
Focus on impact rather than activity.
Focus on team ownership instead of control from above.
Focus on dialogue instead of reporting.
Maybe this is the most important realisation: OKRs are not a goal management tool.
They ares — and they only work when leadership, culture, and organizational structure support them.
1 - https://www.globalgrowthinsights.com/market-reports/objectives-and-key-results-okr-software-market-100409
2 - https://www.okrstool.com/blog/okr-benchmark-report
At wyrd, we believe: “The best leadership tools are the ones you hardly notice in everyday life — because they simply work.”
That is why we are currently developing a new approach for goal setting in SMEs — inspired by OKRs but radically simplified: less reporting, more meaningful focus and better dialogue within the team.
If you're curious about what this approach actually looks like, we’re currently offering early insights.
