OKR is probably one of the worst fads to happen to project management and software engineering.
Just set normal realistic goals and plans, or even just a general direction. Don't use numbers where it doesn't make sense -- not everything needs to be a piece of data -- not everything has a completion percentage.
Hope it goes away soon, along with "Agile", "Extreme Programming" and "Open Office Layout"
I completely agree. At work they never work out because there are inevitably so many detours. OKRs do nothing but reveal that management know nothing about the environment they're managing. Unfortunately, when the fad does pass, you know some other nonsense fad is going to arrive on the scene. If only people would stop with fadding.
Comments
OKR is probably one of the worst fads to happen to project management and software engineering.
Just set normal realistic goals and plans, or even just a general direction. Don't use numbers where it doesn't make sense -- not everything needs to be a piece of data -- not everything has a completion percentage.
Hope it goes away soon, along with "Agile", "Extreme Programming" and "Open Office Layout"
I completely agree. At work they never work out because there are inevitably so many detours. OKRs do nothing but reveal that management know nothing about the environment they're managing. Unfortunately, when the fad does pass, you know some other nonsense fad is going to arrive on the scene. If only people would stop with fadding.
All of those things have worked fine for me. I suspect it depends on how you use them.