"OKRs often get confused for strategy. One of the most common mistakes I’ve seen is teams that confuse their OKRs for a broader strategy. If you observe this happening in your organization, my advice is to suggest that the two rituals get disconnected from each other. Defining strategy comes first."
I have also observed this to be a common failure point & point of confusion. My only additional perspective on this is that strategy has a continuous, iterative, evolving component to it. Which means that your OKRs will need to evolve in conjunction - which ties to another good point you make in the post Lane!
Totally. Good reminder to evolve (and update the documentation) of your strategy. I've definitely been guilty of evolving the strategy but being too slow in updating how that update is documented.
"OKRs often get confused for strategy. One of the most common mistakes I’ve seen is teams that confuse their OKRs for a broader strategy. If you observe this happening in your organization, my advice is to suggest that the two rituals get disconnected from each other. Defining strategy comes first."
I have also observed this to be a common failure point & point of confusion. My only additional perspective on this is that strategy has a continuous, iterative, evolving component to it. Which means that your OKRs will need to evolve in conjunction - which ties to another good point you make in the post Lane!
Totally. Good reminder to evolve (and update the documentation) of your strategy. I've definitely been guilty of evolving the strategy but being too slow in updating how that update is documented.
Super insightful! Thanks for sharing.
This is what I did about OKRs.
https://coda.io/@billfrench/nct-template