update: dead serious. I searched. It says "objectives and key results." But what does one look like? Is it a document?
update: dead serious. I searched. It says "objectives and key results." But what does one look like? Is it a document?
Can be a document, an app, whatever. One flavor is objectives are set at the top, their KRs are translated into objectives for the next management layer with their own KRs, and so on. It's an iterative process with some combination of top-down and bottoms-up activities. And afterwards, the results are reviewed. There's more to it, but that's the gist.
An example: an objective might be "improve application performance". The key results for that objective might be "reduce average page load time from 3s to 1.5s" and "reduce API response times by 60%".
Ah, I see. It bubbles. Explained by https://news.ycombinator.com/item?id=40979799
Thanks everyone.
It's actually a very solid framework, but as the many comments indicate, poor implementations abound (also see Agile, DevOps, etc).
Youre currently only supporting jpeg and png.
Your objective for a quarter could be to broaden support.
So you'd plan to add 10 additional formats. If you add 8, you've achieved your goal. Makes sense, right?
Honestly, the snide comments are spot on. It was even dumber then SMART SCRUM, aka development via waterfall, which is totally agile xoxo
>So you'd plan to add 10 additional formats. If you add 8, you've achieved your goal.
My plan was to add 10, and I added 8. I achieved my goal?
But, most of the places I've seen doing "OKRs" are just appropriating the word but not the actual system.
I still don't like it.
So for example, if you worked in online retail like I did, maybe you'd get an objective like that and then hypothesize a few things along the lines of "if we increase product image interactions by X% then sales should go up by Y%." as key results that you then report back out to management to show progress towards your objective.