3 ms·
My issue with OKRs is trying to apply them to employees who have no power to make business decisions.
by Apreche 4y ago
My issue with OKRs is trying to apply them to employees who have no power to make business decisions.
- b3morales 4y agoOr worse, doing a little farce where they supposedly "choose their own".
- cgearhart 4y agoI’ve said for years that OKRs can make some sense at higher levels of the org because it’s an easy way to communicate strategy but it makes no sense for individual engineers to use them. I think your comment explains why. At some point the people writing the OKRs no longer have the authority or autonomy to actually achieve them. So what’s the point?
- spaetzleesser 4y ago100%! I have to set goals at the beginning of the year but so far every time priorities changed and the goals became deprioritized or obsolete quickly. And at the end of the year I have to map my achievements into categories like "increase market share" or "fuel international growth". My work is so far away from these things that it makes no sense at all. I can see this working for VP and higher who have a multi year perspective and can changes things as needed, but for lower ranks it makes no sense. The only realistic goal for my work is "Keep the f...ing system running and enhance as needed"
- spookthesunset 4y agoOKRs are supposed to be liberating. In theory the management owns the prioritization of problems to be worked on. The team owns the actual way the problem is solved. Done right, OKRs help drive team level innovation. Of course there are plenty of ways to fuck up OKRs…
- deleted 4y ago[deleted]
- eddieroger 4y agoHow about a twister of key results that depends on teams with their own OKRs? It's enough to try to keep my team moving forward sometimes, but I won't put down on paper something I have no control over and be accountable to it.