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 Jtsummers on Friday May 24, 2019 @08:26PM (#20006377)
Those are system requirements and are not what you do with OKRs.
[ Parent | on HN ]
Re:OKRs from a development team’s perspective by malyk on Saturday May 25, 2019 @01:08AM (#20007217)
Are they?

I would imagine the Objective is something like "Maximize the number of people we can help at our clinic". And a key result would be "The number of no-shows for appointments is below 5%".

It then follows that the product development teams (product and engineers) would get together and say something like "Great, we can think up 14 projects that might help us reduce the number of no shows. Here they are in order of easiest and/or highest likelihood to succeed to hardest and/or least likely to succeed".

How else would you use OKRs?

[ Parent | on HN ]