- The Cranky PM
- Posts
- Your OKRs Are Shit and It's Not the Framework's Fault
Your OKRs Are Shit and It's Not the Framework's Fault
Your OKRs are failing because you're treating them like a magic productivity spell instead of a management discipline. Most teams write vague objectives and meaningless key results that sound impressive but create zero accountability. Here's how to diagnose what's really broken and fix your goal setting framework.

Your OKRs are fucking garbage. Not because the framework is broken, not because Google did it wrong, not because your tools suck, but because you're using OKRs like a corporate cargo cult, copying the symbols without understanding the substance, going through the motions without grasping the meaning.
You've turned OKR implementation into another bureaucratic ritual where everyone writes elaborate objectives that sound impressive in quarterly reviews but have zero connection to actual business outcomes. Your key results are either so vague they're meaningless or so specific they're irrelevant. Your quarterly OKR ceremonies have become performance art where people pretend ambitious goals and celebrate mediocre achievements.
The framework isn't the problem. You are. You're treating OKRs like a magic productivity spell that will somehow make your confused organization focused, your unclear strategy coherent, and your unmotivated team driven without actually doing the hard work of being focused, coherent, or driven.
OKRs don't create clarity. They reveal the absence of it. And if your OKRs are confusing, contradictory, and constantly changing, that's not an OKR problem. That's a leadership problem disguised as a goal setting framework problem.
The OKR Cargo Cult Symptoms
You're Writing Objectives That Aren't Objectives
Your "objectives" read like feature lists, project descriptions, or activity reports. "Improve user onboarding experience" isn't an objective; it's a vague aspiration that could mean anything. "Launch mobile app" isn't an objective; it's a deliverable with no connection to why it matters.
An objective should be a meaningful outcome that moves your business forward. It should answer "what will be different about the world if we succeed?" not "what stuff will we build this quarter?"
Your objectives sound like they were written by a committee of people who've never had to explain why their work matters to anyone who signs paychecks.
Your Key Results Are Theater Props
Your key results are either completely unambitious (increase signups by 5%) or completely fictional (reduce churn to zero, increase revenue by 500%). They're designed to make you look sophisticated in planning meetings, not to actually measure progress toward meaningful goals in your goal setting framework.
You've got key results like "improve customer satisfaction" without defining what satisfaction means or how you'll measure it. You've got key results like "increase engagement" without specifying what engagement is or why it matters. You've got key results that change every month because you realized they were measuring the wrong thing.
Your key results aren't results. They're wishful thinking dressed up in business language.
You're Chasing Vanity Metrics Like a Social Media Influencer
Your key results focus on metrics that make you feel good about yourselves rather than metrics that actually matter to your business. You're measuring page views instead of conversions, signups instead of revenue, features shipped instead of problems solved.
You celebrate hitting your "monthly active user" targets while your revenue stagnates. You high-five each other for increasing email open rates while your churn rate climbs. You optimize for metrics that correlate with success instead of metrics that actually are success.
You're Playing OKR Theater for the Audience
Your OKRs are written for your boss, not for your team. They're designed to sound impressive in executive reviews rather than provide clear direction for day-to-day work. You spend more time explaining your OKRs than executing them.
Your team members can recite their OKRs from memory but can't explain how their daily work connects to achieving them. You've created a parallel universe where OKR compliance exists independently from actual work.
Why Your OKR Implementation Is Actually Terrible
You Don't Actually Know What You're Trying to Achieve
Before you blame the OKR framework, answer this: what is your business trying to accomplish this quarter? Not what projects you want to complete, not what metrics you want to improve, but what fundamental business outcome you're trying to create.
If you can't answer that question clearly and specifically, your OKR problem isn't about better key results. It's about not having a coherent strategy worth measuring in the first place.
You're Avoiding Hard Choices
OKRs force you to choose what matters most. If everything is equally important in your OKRs, you're not using OKRs. You're using a fancy to-do list. Real objectives require saying no to things that matter so you can say yes to things that matter more.
Your OKRs are diplomatic compromises designed to avoid disappointing anyone rather than strategic choices designed to maximize impact. You've got six objectives because you couldn't choose between them, not because you need six different outcomes.
You Don't Understand the Difference Between Outputs and Outcomes
Your key results measure what you're doing (outputs) rather than what you're achieving (outcomes). "Launch three new features" is an output. "Increase user retention by 20%" is an outcome. "Hold five customer interviews" is an output. "Identify the top user pain point blocking conversion" is an outcome.
You're measuring your activity level instead of your impact level. You're optimizing for looking busy instead of being effective.
You're Using OKRs as Performance Theater
Your OKRs exist to make you look strategic and goal-oriented to executives who don't understand your actual work. You're performing goal-setting for an audience that mistakes elaborate objectives for effective execution.
Your quarterly OKR reviews are presentations about why you almost hit your targets, not conversations about what you learned and what you're changing based on results.
What Good OKR Implementation Actually Looks Like
Objective: Clear, Ambitious, Meaningful
A good objective answers: "If we accomplish this, what meaningful change will we create for our business or our users?"
Bad: "Improve the product experience"
Good: "Make new users successful enough to become paying customers"
Bad: "Optimize our marketing funnel"
Good: "Generate qualified leads that sales can actually close"
Bad: "Enhance team productivity"
Good: "Ship features faster without sacrificing quality"
Key Results: Specific, Measurable, Time-bound
Good key results are specific enough that anyone can look at them and immediately know whether you succeeded or failed, no interpretation required.
Bad: "Increase user engagement"
Good: "Increase daily active users from 10,000 to 15,000"
Bad: "Improve customer satisfaction"
Good: "Achieve an NPS score of 50 or higher"
Bad: "Launch the mobile app successfully"
Good: "Get 1,000 mobile app downloads with 70% 7-day retention"
Connected to Business Impact
Every key result should have a clear, logical connection to business outcomes that matter. If you can't explain how achieving a key result will make your business more successful, it's not a key result. It's a hobby.
The Real Problems You're Solving With Your Goal Setting Framework
Problem #1: Strategic Confusion
Your team doesn't understand what success looks like because leadership hasn't defined it clearly. OKRs force you to articulate specific, measurable definitions of success that everyone can understand and work toward.
Problem #2: Misaligned Effort
People are working hard on things that don't matter because they don't understand what does matter. A proper goal setting framework creates alignment by making priorities explicit and measurable.
Problem #3: Lack of Accountability
Nobody knows whether they're succeeding or failing because success isn't clearly defined. OKRs create accountability by making results visible and measurable.
Problem #4: Short-term Thinking
You're optimizing for immediate outputs instead of meaningful outcomes. OKRs force you to think about impact over activity.
The OKR Implementation Reality Check
You Can't OKR Your Way Out of Strategic Confusion
If your business strategy is unclear, your OKRs will be unclear. If your priorities are constantly changing, your OKRs will be constantly changing. OKRs are a framework for executing strategy, not a substitute for having one.
You Can't Measure Your Way to Motivation
OKRs don't make people care about their work. They make it clear whether people who already care are succeeding. If your team is unmotivated, the problem isn't your key results. It's your leadership.
You Can't Framework Your Way to Focus
OKRs don't create focus. They reveal whether you have it. If you have twelve objectives, you don't have focus problems with your goal setting framework. You have focus problems with your decision-making.
The OKR Implementation Diagnostic Questions
Before you blame the framework, answer these questions honestly:
Strategy Questions:
Can you explain your business strategy in one sentence that a customer would understand?
Do you know what success looks like for your business this quarter?
Can you articulate what you're not going to work on and why?
Execution Questions:
Do your key results actually measure the outcomes that matter to your business?
Can your team explain how their daily work connects to your objectives?
Are you making decisions based on your OKR progress or ignoring it?
Accountability Questions:
Do you actually review your OKR progress regularly and change your approach based on results?
Are you honest about which key results you're missing and why?
Do you use OKR results to inform future planning or just celebrate/mourn and move on?
What Bad OKR Implementation Looks Like
The Participation Trophy Factory
Everyone hits their OKRs every quarter because they're not actually challenging. You've turned OKRs into a celebration of mediocrity where 70% achievement is considered success and 100% achievement is considered suspicious.
The Moving Goalpost Olympics
Your key results change every month because you realize they weren't measuring what matters. You spend more time adjusting your OKRs than working toward them.
The Vanity Metric Parade
You celebrate increasing followers, page views, and email subscribers while your revenue, retention, and customer satisfaction stagnate. You're winning at metrics that don't matter.
The Bureaucratic Ritual
Your OKR process involves elaborate templates, multiple approval layers, and lengthy review meetings that produce no insights and drive no changes in behavior.
What Good OKR Implementation Actually Looks Like
Brutal Honesty About Results
You regularly miss your key results because they're actually ambitious. You learn from failures and adjust your approach. You measure things that matter even when the results are uncomfortable.
Clear Connection to Work
Every team member can explain how their current projects contribute to achieving the key results. Daily decisions are influenced by OKR progress.
Strategic Coherence
Your objectives reflect actual business priorities. Your key results measure outcomes that correlate with business success. Your OKRs change when your strategy changes, not when you get bored.
Learning-Oriented Reviews
Your OKR reviews focus on what you learned about your market, your product, and your execution capability, not just whether you hit your numbers.
Common OKR Implementation Mistakes That Kill Results
Mistake #1: Too Many Objectives
You have 8 objectives because you couldn't choose what matters most. Real focus means 3-5 objectives maximum. Everything else is just organized wishful thinking.
Mistake #2: Activity-Based Key Results
Your key results measure what you're doing ("Ship 5 features") instead of what you're achieving ("Increase user retention by 15%").
Mistake #3: Sandbagging Goals
Your key results are so conservative that hitting them requires no actual improvement or risk-taking. Ambitious goals should feel slightly uncomfortable.
Mistake #4: No Connection to Daily Work
Your team can't explain how their current projects contribute to OKR achievement. The goals exist in a parallel universe from actual work.
Mistake #5: Set-and-Forget Planning
You write OKRs once per quarter and never review progress or adjust tactics based on what you're learning.
How to Fix Your Broken Goal Setting Framework
Step 1: Start with Strategy Clarity
Before writing any OKRs, answer: "What does success look like for our business this quarter?" If you can't answer this clearly, stop and fix your strategy first.
Step 2: Focus Ruthlessly
Choose 3-5 objectives maximum. If everything is important, nothing is important. Use the prioritization framework to make hard choices about what matters most.
Step 3: Write Outcome-Based Key Results
Every key result should measure a business outcome, not an activity. Ask: "If we achieve this key result, how will our business be better?"
Step 4: Make Them Measurably Ambitious
Your key results should feel slightly uncomfortable. If you're 100% confident you can hit them, they're not ambitious enough.
Step 5: Review and Adjust Weekly
Check OKR progress weekly and adjust tactics based on what you're learning. The goals stay stable, but your approach should evolve.
The Uncomfortable Truth About Your Goal Setting Framework
Your OKRs suck because you're using them to avoid the hard work of leadership, not to do it better. You want OKRs to magically create the clarity, focus, and accountability that you're not providing through actual leadership.
You're treating OKRs like a productivity hack instead of a management discipline. You want the benefits of clear goals without the work of setting them thoughtfully, the benefits of accountability without the discomfort of honest performance evaluation, the benefits of focus without the pain of saying no to things that seem important.
OKRs are a tool. Tools don't make you better at your job. They make it easier to do your job well if you already understand what doing it well means.
Stop Blaming the Framework
Your OKR problem isn't a framework problem. It's a leadership problem. Your objectives are vague because your strategy is vague. Your key results are meaningless because you don't understand what meaningful results look like for your business.
Stop blaming Google. Stop blaming your tools. Stop blaming the framework. Start being honest about whether you actually know what you're trying to achieve and whether you're actually committed to achieving it.
OKRs work when they're used by people who understand their business, know what success looks like, and are willing to be held accountable for results. If that doesn't describe you, the problem isn't your OKRs.
Fix your strategy. Clarify your priorities. Define success in terms that matter. Then write OKRs that reflect that clarity.
Your framework is fine. Your execution is garbage. Time to own it and fix it.