This book, co-written by Paul Niven and Ben Lamorte, is a fantastic handbook for the OKR implementer. OKRs stands for "objectives and key results," and there are doubtless other reviews that spell out what OKRs are, so I won't do that here. OKRs are in fashion now because they are effective but also because they are used by companies like Intel, Google, etc. Full disclosure, Ben Lamorte consulted for my company as an OKR coach and did a great job getting us launched. Thanks, Ben!
The audience here is likely a member of a company's executive team and her staff who needs to get an organized process going for OKRs. For a bit more of the experiential feel of OKRs for a small group, try Christina Wodtke's book Radical Focus. The only reason I'm giving this a 4 rather than a 5 is because I think this book benefits from being accompanied by the narrative in Wodtke's book. It's hard to capture the texture of what OKRs feel like without that story.
If you're in a company with more than, oh, 100 employees, I think this book will bring significant benefit. It will help you understand what needs to be done by whom and when. Everywhere we even diverged slightly from the counsel of this book (for instance, we have probably not been diligent enough having weekly meetings) -- it provides the plan. It will also tell you about things you might forget. For instance, you must coordinate your OKRs with your peers, be they functional areas or individuals. Another: At the end of the quarter when you present your OKR results, you must *discuss them*. Don't just end the meeting with the results.
If another version ever comes out . . . a few concerns (which I hope to address in a blog post):
1. There really aren't enough examples of key results here. I think that finding good inspirational objectives gets a lot of guidance, but the KRs are largely sales metrics or derived from them. We implementers need more. Having said that, as someone involved with defining KRs, Ben contributes a critical question for finding those KRs. After you've defined your object, he asks: "How will you know when you've reached it?" That's the big question. Once you've heard it, it's obvious. Otherwise: Not obvious. Thanks, Ben.
2. I am very skeptical now of the "milestone" OKR. If it isn't clearly numerical on a scale that works nicely from 0% done to 100% meeting the "amazing" stretch goal . . . dunno. Haven't seen milestones work very well. They seem like deliverables or tasks to me.
3. Niven and Lamorte also talk about breaking the score down into 0.3, 0.5, 0.7, and 1.0. If the KR is numerical, do we really need this? I think the provision of the 0.3, 0.5, 0.7, 1.0 draws attention away from the numerical quality of the KR. The KR ought to be good enough itself to provide the high-level guidance for completion.
4. OKRs and agile can be an awkward fit. We need to hear more voices on OKRs from engineering groups.