OKRs are NOT Pokémon

OKRs are NOT Pokémon

You don’t “gotta catch ’em all”. 🎮

It’s the same pattern every quarter:
17 new OKRs per tribe.

The quantity of OKRs matters but the way we approach them in matters more.

You know the drill:
Everyone starts their own.
And when one person needs help, everyone else is busy. 🏃‍♂️

The problem is less that these dependencies occur, and more how we sequence our efforts to resolve them.

For me, the solution is to focus on the order we want to tackle them in.
So we can work as a team and avoid letting OKR #17 block OKR #1.

Now, when your team on #1 is interrupted by others dependent teams, they can say:

🙏 “Sorry, we’re busy on #1, please come back later.”
🤝 “Chat to this team, they might be able to help.”
💡“Here’s the docs, can you solve it yourself?”

Better yet, your team on #17 might think:

“I’m on #17. Do you need my help?”
“I know they’re on #1, so won't interrupt them at all.”

🔎 This simple pattern has helped the companies I work with create focus across their entire org:

- Focus on the highest leverage items
- Put the #1 on a fast track and get it done
- Reduce the effects of their dependencies
- Prevent everyone from bumping into each other constantly
- Remember that early delivery gives more time in the market to make money

When you’re ready, lets:

Stop letting your #17 block your #1.

PS, Thanks to Jeff Gothelf whose post inspired this.

Remove your growth pains of Scaling Up

Receive exclusive posts on Leadership Growth, Scaling Up, and improving your org design.

Cliff Hazell - Remove your growth pains of Scaling Up

Great! You’ve successfully signed up.

Welcome back! You've successfully signed in.

You've successfully subscribed to Cliff Hazell - Remove your growth pains of Scaling Up.

Success! Check your email for magic link to sign-in.

Success! Your billing info has been updated.

Your billing was not updated.