First off, I want to note that I read this book for work at the request of my company's CEO, who gifted it to me, and would not have picked it up otherwise. With that being said, this is a book that could have been an email. In fact, I am sure it was, at one point, some sort of online article, since there are hyperlinked words within the text that I obviously can't click on because I read a physical book.

The reason this book gets more than half a star is that it explains the framework my company's CEO is looking to implement in an understandable way. However, even this 70 page, 30 minute read felt like it beat the concept to death. The more the author attempts to explain the intricacies of the OKR framework, the more he begins to contradict the points he made earlier in the book. I felt like I had to Google a lot of what the author wrote to make sure he was actually describing OKRs correctly (and he is; the details that become contradictory are somewhat irrelevant to the overall point, but it's the principle of ruining the reader's faith in your expertise). And no, he doesn't get into how Google used OKRs to become successful to any interesting degree.

That's not even touching on the atrocious grammar here. I know the author is Turkish and I know the book is self-published, but honestly that isn't an excuse to have terrible grammar and missing syntax. I feel like so many of the issues could have been fixed with a single reread, which really makes me question the book as a whole. Long story short: don't read this. Please just Google what an OKR is. My review is the length of at least three pages in this book at this point, and at least I'm bothering to reread my work before publishing.