Portrait of Asbjorn Bjaanes
Asbjorn Bjaanes

Articles ·

The OKR Illusion, Why Structure Without Direction Is Just Noise

The OKR Illusion, Why Structure Without Direction Is Just Noise

OKRs (Objectives and Key Results) have gained significant traction over the past decade, especially after being widely adopted and championed by companies like Google. Originally developed at Intel, OKRs are a simple yet powerful framework for setting and tracking goals. At their core, OKRs are about defining what you want to achieve (Objectives) and how you’ll measure progress (Key Results). While the concept is simple, the impact lies in how OKRs align teams, create focus, and connect everyday work to meaningful, measurable outcomes.

Walk into most OKR meetings today, and you’ll find two familiar patterns:

  1. Key Results that are merely a to-do list.
  2. Discussions hijacked by efficiency-makers driving the team toward more output, not better outcomes.

It’s no wonder so many teams feel they’re running hard but going nowhere new.

OKRs (Objectives and Key Results) were never meant to be just goals stapled to activities. They are meant to create direction, coach teams toward preferred futures, and shape transformational conversations, not transactional tasks.

So why does it go wrong? And how can we fix it?

Direction is the Missing Link

1. Direction is not a plan. It’s a felt sense of movement.

Good OKRs create emotional alignment. They connect logic (what we do) with intention (why we do it). It is known that our behavior is shaped by our mental and emotional state. If the objective doesn’t create an internal “toward” state, something compelling and emotionally anchored, we will default to the safety of sameness.

In coaching, we often ask: “What would success look like?”
An OKR should help us ask: “What’s the direction that, if followed, would evolve how we show up?”

2. When Structure is Missing, Tactics Take Over

A surprising pattern I’ve seen across teams and organizations is this:
When structure is lacking, the instinct is to focus on tactics. Clear KPIs, action plans, and goals fill the gap. But without a unifying direction, they become fragmented efforts, resulting in more of the same, at its best done slightly faster.

These teams often believe they have direction, but what they really have are a collection of ideas. Ideas are not direction. Ideas are potential. Direction is chosen, aligned, and activated through intentional outcomes.

Without the OKR mindset, tactics can become noise. The result is local efficiency without global effectiveness.

Where Most OKRs Go Wrong

They focus on certainty over possibility.

Key Results become a checklist instead of markers of transformation.
Instead of “Improve customer onboarding satisfaction from 60 to 80%”, we write “Conduct 3 onboarding interviews.”

The first measures change. The second measures activity.

They assume alignment instead of facilitating it.

OKRs should serve as coaching tools, conversation starters that align intent, direction, and focus. But often they are set top-down, shared in slides, and never revisited as tools for reflection or redirection.

They ignore systemic context.

A team under constant firefighting cannot stretch toward a compelling vision.
Without psychological safety and a sense of shared ownership, OKRs become performative. Agile tells us that people over processes matter, so our OKRs must emerge from collaboration, not compliance.

How to Create Directional OKRs That Transform

Using Agile values, NLP strategies, and coaching methodology, here are 4 ways to reclaim the power of OKRs:

1. Make Objectives identity-driven, not output-driven.

Use language that evokes transformation.
Instead of: “Launch new AI feature by Q2”
Try: “Establish ourselves as the go-to AI partner for well intervention”

That’s not just a task. That’s a direction.

2. Write Key Results that measure movement, not motion.

Use well-formed outcomes and sensory-based language.
Bad KR: “Host 4 webinars”
Good KR: “Increase inbound demo requests from maritime clients by 40%”

3. Treat OKR reviews as coaching sessions, not status updates.

A quarterly OKR check-in is not a sprint review. It’s a strategy alignment ritual.

Ask:

  • Are we still moving toward what matters?
  • What assumptions have changed?
  • What do we need to let go of to move faster?

This is where coaching shows up, not in the setting of the OKRs, but in the conversation they enable.

4. Separate direction from velocity.

Agile loves velocity. But speed without direction is chaos. The fastest teams I’ve seen are not the ones who tick off the most tasks, they’re the ones who pause, reflect, adjust, and double-down on the highest-leverage moves.

This is what I call Directional Agility:

The ability to move fast with intention, not just motion.

The Real Role of OKRs: Inner and Outer Transformation

In the coaching field we understand, change happens across neurological levels:

  • Environment
  • Behavior
  • Capabilities
  • Beliefs
  • Identity

Most OKRs stay stuck at behavior or capability level. But what if we started writing OKRs that challenged identity and belief?

“Shift from a reactive support org to a proactive value enabler for our clients.”

That’s an identity-level transformation. That’s direction.

We Need Less Managing, More Coaching

Too many OKR meetings are dominated by efficiency-makers asking: “What’s the next action?”
As we know, actions without direction just get us more of what we already have.

As leaders, we must move from being activity managers to direction coaches.
From asking “What did you do?” to “What changed as a result?”

Because in the end, OKRs are not about what we did.
They are about who we’re becoming.

Written by Asbjorn Bjaanes for Miles AS — Norwegian Version available https://www.miles.no/post/distribuerte-team-som-strategi-og-konkurransefortrinn


Written by Asbjorn Bjaanes. Also published on Substack.

Reach out