[Draiken]

Then people create objectives like:

O - Improve team efficiency

KR - Increase test coverage by X%

KR - Update at least Y outdated dependencies

Which are complete bullshit, easily gamed and don't actually make the company move forward or the team better.

But according to almost any OKR believer, these are great OKRs.

Making KRs measurable a lot of the times corrupts the OKR system. However if they aren't measurable, their value is sometimes questionable. Kind of a paradox.

Perhaps for huge corporations this kind of system is absolutely needed, but I'm experiencing this on a small company and it's honestly tiring and inefficient.