Pod Insights The Agile Daily Standup - AgileDad The OKR Illusion, Why Structure Without Direction Is Just Noise About this episode 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.
How to connect with AgileDad:
- [website] https://www.agiledad.com/ https://www.agiledad.com/
- [instagram] https://www.instagram.com/agile_coach/ https://www.instagram.com/agile_coach/
- [facebook] https://www.facebook.com/RealAgileDad/ https://www.facebook.com/RealAgileDad/
- [Linkedin] https://www.linkedin.com/in/leehenson/ https://www.linkedin.com/in/leehenson/
Transcript 0:15 Speaker 00 OKRs have really gained significant traction over the past decade, especially after being widely adopted and championed by companies like Google, Apple. They're originally developed by Intel. OKRs or objectives and key results are a simple yet powerful framework for setting and tracking goals. At their core, OKRs are about defining what you want to achieve with your objectives, how you'll measure your progress, key results. While the concept feels and sounds very simple, the impact lies in how OKRs align teams, create focus, and connect everyday work to meaningful and measurable outcomes.
1:00 Speaker 00 This is where it all makes sense. This is where the rubber hits the road.
1:05 Speaker 00 So walk into most OKRs meetings today, OKR meetings today. If you walked into one, you'll find two patterns, at least this is what I've seen. One, key results are just like a bulleted to-do list. It's not really key results at all. It's just a bulleted list of things to do. Two, discussions are hijacked by the efficiency makers, driving a team towards more output and less focused on outcomes. The efficiency makers are dedicated to what do we have to do to get this done? And all they're focused on is an increase in story points, an increase in delivered stories, an increase in projects finished. They're not looking at the emotional or the financial
1:48 Speaker 00 or any of the impact that's going to happen after the fact from rework, upset customers, etc. So they're not focused on the correct things. They're not focused on better outcomes. It's no wonder why so many teams feel like they're running hard, but not getting anywhere. They don't feel like they're making any progress. They feel like they're running on a treadmill and not making any progress further forward.
2:10 Speaker 00 I think that OKRs were never meant to be just goals stapled to some activities that you just get done. They were meant to create direction, coach teams toward preferred futures, and shape transformational conversations, not transactional tasks. So what makes it all go wrong? That's the big question. And how can we fix it? Direction. Let me put it this way. Direction is not a plan. It's a felt sense of movement. I'm gonna say that one more time. Direction is not a plan. It's a felt sense of movement. If that's true, good OKRs create emotional alignment. Emotional damage. No, emotional
2:51 Speaker 00 alignment. They connect logic, what we do, with intention, why we're doing 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 will default to safety, safety of sameness, right? We can just keep doing it this way and we'll be fine. In coaching, we often ask, what would success look like? An OKR should help us ask, what's the direction that it followed would evolve how we show up and how we're stepping towards success? And I think that's a big differentiator.
3:37 Speaker 00 Also, when structure is missing, those tactics, they take over. So if you don't have structure, you definitely got tactics. You got minutia. A surprising pattern I've seen across teams and organizations is this. When structure is lacking, the instinct instantly becomes, let's focus on the tactics. Let's focus on the minutia. Clear KPIs, action plans, and goals fill the gap. But without a unifying direction, they become fragmented efforts, resulting in more of the same.
4:09 Speaker 00 I've seen it quoted as trying to do our best, just slightly faster. That's a good way to look at it. These teams often believe they have direction, but what they really have are a collection of ideas. Ideas are not a direction, folks. Ideas...
4:27 Speaker 00 Are potential. Direction is chosen, aligned, and activated through intentional outcomes and achieving intentional outcomes. Without the OKR mindset, tactics become just noise and the result is local efficiency without any global effectiveness. So OKRs, I don't want to say all go wrong, many OKRs go wrong. Why do they go wrong? Where do they go wrong? They tend to focus on certainty over possibility. Key results become a checklist instead of the marker, a marker of transformation. Instead of improve customer onboarding satisfaction from 60 to 80%, we write, "Conduct three onboarding interviews." The first one measures change. The second one measures an activity.
5:13 Speaker 00 That makes sense, right? I hope it does. They assume alignment instead of facilitating. So OKR should serve as coaching tools, conversation starters that align intent, direction, and focus. But oftentimes, they are set top-down, shared in slides, and never revisited as tools for reflection or redirection. How about this? Oftentimes, they ignore systemic context. This is one I see a lot. A team under constant firefighting just doesn't have the bandwidth to stretch towards a compelling vision. Without implementation of psychological safety and a sense of shared ownership, OKRs become performative.
5:56 Speaker 00 Agile tells us that people over processes matter. So our OKRs must emerge from collaboration and not compliance.
6:05 Speaker 00 How about this one? How do we create directional OKRs to transform?
6:11 Speaker 00 Using agile values, NLP strategies, and coaching methodology.
6:17 Speaker 00 I've, I've put together a short list, three or four ways that we can reclaim the power of OKR. So let's, let's get alignment around this. Here's option number one. Make objectives identity driven and not output driven. Use language that evokes transformation. Instead of launch a new AI feature by Q2, you might say establish ourselves as a go-to AI partner for well intervention. I like that. That's not just a task, that's a direction. That's a, that's an affirmative direction and I love it. How about this one? Write key results that measure movement, not motion. Use well-formed outcomes and sensory-based language. So a bad key result would be host for webinars.
7:00 Speaker 00 A good key result would be increase inbound demo requests from maritime clients by 40%.
7:08 Speaker 00 That is a key result. Yes, that is solid. How about this one? Number three. Treat OKR reviews as coaching sessions, not like a status update. But quarterly OKR check-in is not a sprint review. It's a strategy alignment and realignment ritual. Ask yourself, are we still moving towards what matters? What assumptions have changed? What do we need to let go of in order for us to move faster? This is where coaching shows up. This is where change management shows up, not, not in setting the OKRs, but in the conversation they should and could enable. And I'll throw one more for bonus. You need to separate direction from velocity. Agile teams and agile organizations love velocity for all the wrong reasons.
7:53 Speaker 00 But speed without direction is chaos. I'll say it again. 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. Those are the ones that are successful. And this is what I like to refer to as directional agility. It's part of change management. It's part of agile project management. It's part of initiate and discover. It's the part that people forget about. It's the ability to move fast with intention and not just motion.
8:31 Speaker 00 So I guess the summarizing view of all this is you need to understand the real role of OKRs in order to be successful, and that's inner and outer transformation. In the coaching field, we understand change happens across neurological levels, things like environment, behavior, capabilities, beliefs, identity, those types of things. Most OKRs stay stuck at behavior capability level. But what if we started writing OKRs that challenged identity and belief? That would change everything. Shift from a reactive support org to a proactive value enabler for our clients. That's an identity level transformation, and that, my friends, is direction and change management. I think the whole key here is we need less managing and more coaching.
9:16 Speaker 00 Too many OKR meetings are dominated by efficiency makers who ask, what is the next action? And as we know, action without direction just gets us more what we already have, doing the same thing over and over again, but expecting a different result? Insanity. You know, as leaders, we must try to move from being just activity managers and activity facilitators to direction coaches and decision makers. We need to be more proactive in our approach. We need to switch from asking, what did you do? To what changes the result of what you did? Because in the end, OKR is not about what we did. It's about what direction we're going and who we potentially can become. You know what? That's going to do it. I think that's it.
10:00 Speaker 00 If you have questions about OKRs or any other topic, or if you have a topic you want to talk about here, reach out to us, learn more at agiledad.com. We'd love to hear from you. And as always, we encourage you to stay healthy, stay well, and stay agile, my friends. Until next time, do take care.
Previous Celebrating Dr Martin Luther King Jr Next Start The Year With a Clean Backlog - Mike Cohn Page updated November 6, 2026 · transcript and summary are machine-generated