Hacker News new | past | comments | ask | show | jobs | submit login

Missing OKRs always seemed a little weird to me. It strikes me as a lack of vision and makes the numbers and goals chosen seem very arbitrary.



Missing OKRs means that the team cannot set achievable goals. It is a signal that the team has terrible foresight.

I know the argument is that by being more ambitious and achieving 70%, you are setting ambitious goals. But then the goals are never met. The work doesn't finish. The projects falter. The users are unhappy. Engineers leave.


In my experience, people make 10 goals during planning and then later decide on the 7 that they're going to hit. I wouldn't mind if the goals were ambitious but efforts were made to achieve 70% of them. However, in practice it seems like there's no vision during planning and instead they change course midway through the half. What's the point of planning if you can't stick to the plan.




Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: