News for hackers. Stuff that matters.

A comment on OKRs from a development team’s perspective. Parent comment

Re:OKRs from a development team’s perspective by sanderjd on Friday May 24, 2019 @09:32PM (#20006594)
Yep, this would be good feedback up the chain. People above you should be working on breaking the company level goals into team and role specific ones.

Edit: just to note that I have some other criticisms of OKRs, but having them be way too high level, broad, and not actionable should not be the problem.

[ Parent | on HN ]
Re:OKRs from a development team’s perspective by cstrasen on Monday May 27, 2019 @08:17AM (#20021515)
Please share your criticism. I would be happy to get as much perspective on the topic as possible.

The problem I encountered was having, or the notion of wanting, a product roadmap which is produced from stakeholder, C-level, product- and IT team input parallel to OKRs. I feel this is an anti pattern. You have OKRs and they make your quarterly roadmap or you don't apply OKRs at all to the producing team.

[ Parent | on HN ]