3 ms·
so many issues straight away > should you complete 70% of your goals to 100%? Or should you complete 100% of your goals at 70%? explicitly addressed in variou
by willsmith72 3y ago
so many issues straight away
> should you complete 70% of your goals to 100%? Or should you complete 100% of your goals at 70%?
explicitly addressed in various articles and books. you average your scores across objectives and KRs to get a score. So the answer is both, looking for average score of 0.7
> if your key result is "migrate 100% of users to the new system" and you only migrate 70%, guess what? Now you're stuck maintaining two systems in perpetuity
so you're going to migrate all of your users in a big bang moment?? hell no. it'll be bit by bit no matter what. of course you're maintaining two systems, that's a sign of a good migration, not a bad one. the KR just helps you get done with it faster
of course there are valid criticisms of okrs, and many (most?) teams get them wrong.
but saying "okrs are bullshit" has become a common trope for new-age companies who use that as a way to differentiate themselves. do you really think Andy Grove and John Doerr are bullshit artists?
- FranksTV 3y agoIt's not that I think Andy Grove is a bullshit artist, it's that I'm pretty sure the person assigning the OKRs isn't Andy Grove.
- willsmith72 3y agobullshit management is bullshit management that's a company/people problem, not a tool problem
- zelphirkalt 3y agoBut wait: "People over processes and tools."
- Marazan 3y agoHow do KRs help you migrate faster?
- willsmith72 3y agothe whole purpose behind an okr is alignment. a public, committed KR for % of users migrated helps a team get there faster than not having one, and signifies to everyone at all levels what's important and what's being worked on that's the theory behind okrs in general
- Marazan 3y agoHow is that different from saying "My team will be migrating everyone to the new system this quarter"