Thanks for that! I found it valuable, and I would recommend it to anybody using OKRs. It’s fun to hear that you found a lot of similar things that I have found over the last few years applying OKRs, such as
- The importance of having “non-binary” key results (checkbox key results)
- The value of focusing on the end result, without dictating or committing to specific features to get there (allowing for continued team creativity and experimentation)
One thing I noticed you mentioning is that in your view completing all KRs to 100% should mean the objective is achieved. Personally I take a different approach on this. Generally I’m quite ok with a “infinite objective” like “Reduce friction of the QA process.” This type is obviously never achieved (unless it becomes 0, I suppose), but key results should get specific goals to move closer.
In my mind it’s perfectly fine for objectives to remain the same for quarters, even years, just the key results change (either the target numbers in the KRs, or the KRs in general).
Any opinion on this approach?