The problem is when OKRs become “the thing”....overloaded to try to do all of the jobs above and more (performance management, even). They are not fit-for-purpose for these jobs, and pretending that they are can be damaging to the team. (2/4)
A big problem is uncertainty. I can give you an OKR for carrying bricks across my parking lot. Or increasing avg shopping cart $ size.
Many prod dev efforts aren’t that neat and tidy. OKRs are context-less. There’s not a one-pager attached to an OKR (most of the time) (3/4)
Many prod dev efforts aren’t that neat and tidy. OKRs are context-less. There’s not a one-pager attached to an OKR (most of the time) (3/4)
So...that’s the puzzle. In environments with the requisite context...then OKRs are easy. Do you even need them in that case? And in environments without rich shared understanding they feel needed, but can’t do all the jobs. (4/4)
