this is a challenging topic and there is no correct answer. even google doesn't know and from what i've heard, doesn't utilize OKRs in every team. at the end of

this is a challenging topic and there is no correct answer. even google doesn't know and from what i've heard, doesn't utilize OKRs in every team. at the end of the day, a developer is responsible for shipping story points at most companies. setting big product outcome and aspirational KRs is not part of their job description, and those are more for product managers. in our company, we focus on shipping a certain number of story points and conducting code reviews as repeating objectives every quarter. Also, every developer has some learning goals with KRs such as watch 5 new videos, attend 3 workshops, experiment with new frameworks, ect. We also have OKRs related to some initiatives that each developer is pushing such as reducing regression, increasing app load speed, adding more tests, and 15-minute quick product wins. please let me know if you have any questions.