The problem with this kind of article is the dry, abstract, formal presentation, which feels devoid of content. A lot of us don't quite know how to operationalize it, and often the users of such language don't either. It feels like religious doctrine that everyone pays lip service to but doesn't really affect life in any meaningful way.
The manager-bureaucrat many of us are familiar with does not understand or care how to put these ideas to work, and reduces "OKRs" to forms to be filled and boxes to be checked.
We need context, examples, and explanations that show us when these ideas are working and when they aren't. We need them in plainer, more candid and more relatable language. And they need to be relevant to the problems developers and managers actually face. We need the why - why is it helpful to think in terms of OKRs rather than some other more familiar or simpler way?
Bottom line: the secret missing ingredient is often "actually use your brain when doing all these things".
The manager-bureaucrat many of us are familiar with does not understand or care how to put these ideas to work, and reduces "OKRs" to forms to be filled and boxes to be checked.
We need context, examples, and explanations that show us when these ideas are working and when they aren't. We need them in plainer, more candid and more relatable language. And they need to be relevant to the problems developers and managers actually face. We need the why - why is it helpful to think in terms of OKRs rather than some other more familiar or simpler way?
Bottom line: the secret missing ingredient is often "actually use your brain when doing all these things".