3 ms·

Often OKRs are forced into engineering teams and the result is that they don't deliver value. However, there are ways of doing OKRs in engineering teams as well

Often OKRs are forced into engineering teams and the result is that they don't deliver value. However, there are ways of doing OKRs in engineering teams as well. I recently wrote up a little account of how I used an OKR around linter errors to get a team to take quality more seriously. It worked surprisingly well: https://koliber.com/articles/reduce-tech-debt-with-okrs https://koliber.com/articles/reduce-tech-debt-with-okrs It's not that OKRs such. It's that they are often done in a ham-fisted fashion.

yieldcrv 3y ago
That tale is inspirational, the OKR aspect of it seems not important. You were having weekly engineering meetings regardless. You were giving positive reinforcement regardless. Its like because your team were subjugated by a hamfisted OKR feifdom, you conformed a goal into an OKR. Would you have ignored this issue if the OKR didn't tell you to go find something to be an issue? Was the maturity of your development team driven by your drive to find a problem, and then the root of the problem, because the OKR told you to find something?