In this episode, Dan Neumann is excited to be joined by special guest, Felipe Castro! Felipe is an expert on OKRs or Objectives and Key Results. He is an OKR trainer, speaker, and author who helps organizations transform how they use goals by adopting OKR! He has even created his own OKR tool called the OKR Cycle which is a simple method to avoid OKR\u2019s most common pitfalls.
\xa0
As a master of all things OKR, Felipe Castro is here to speak about \u2014 you\u2019ve got it \u2014 all things OKR! He goes over what OKRs are; important aspects you should consider; tips and advice regarding them; common mistakes, misunderstandings, and pitfalls; and how to overcome them.
\xa0
Key Takeaways
What are OKRs?
Stands for Objectives and Key Results
An Agile approach to setting goals and creating alignment
OKRs are about the outcome you want to achieve
A framework for defining and tracking objectives and their outcomes
Focuses on outcome-based planning as opposed to tracking tasks and activities
Instead of giving the teams a feature to build, you are giving them a problem to solve or an opportunity to tackle
Important aspects of an OKR:
The objective should be memorable, compelling, motivating, and inspiring
The \u2018why\u2019 comes from leadership and the team figures out the \u2018what\u2019 together
Asking \u2018so what?\u2019 can help your team create better key results
Give your engineers autonomy to solve problems
Psychological safety is crucial for fostering an environment for high-performance teams
Felipe\u2019s OKR tips and advice:
Start with targets that are regular goals (hard, but achievable)
Don\u2019t copy another company\u2019s method around OKR \u2014 adopting OKR is a journey that will be different for every company
Adapt the principles of OKRs for your specific context
You need to unlearn, adapt, and evolve \u2014 especially if you come from an Agile background
Common OKR mistakes, misunderstandings, and pitfalls:
Treating it as a glorified to-do list
Using OKRs as a copy of Jira (which doesn\u2019t add any value)
Seeing the role of engineers as assisting only with the coding rather than problem-solving
That the sweet spot for achieving a target is 70% (which has zero science behind it)
\xa0
Mentioned in this Episode:
The Beginner\u2019s Guide to OKR, by Felipe Castro
SVPG (Silicon Valley Product Group)
INSPIRED: How to Create Tech Products Customers Love, by Marty Cagan
McKinsey\u2019s Three Horizons Model
\u201cHow Can You Test Business Ideas? Interview with David J. Bland,\u201d by Felipe Castro
\xa0
Felipe Castro\u2019s Book Picks:
\xa0
Want to Learn More or Get in Touch?
Visit the website and catch up with all the episodes on AgileThought.com!
Email your thoughts or suggestions to Podcast@AgileThought.com or Tweet @AgileThought using #AgileThoughtPodcast!