Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

OKRs are essentially 2 parts. The "O" is an aspirational goal; The "KR"s are the measureable components.

* Start with the problem statement and then make the objective to address it.

* If you're always 100% on your OKRs they are not amibtious enough. The value is in the progress not "completion".

* Don't make your Key Results a giant checklist of TODOs. It's OK to have figuring out the "how are we going to do this?" as part of the result to be measured, you just need to predefine how it will be measured.



So it's

O -> SLA

KR -> SLO

KPI -> SLI




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: