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

How do you avoid OKRs for capability that are all-or-nothing? I've had the problem picking ones that stay at 0 for a very long time.


OKRs that are all-or-nothing are fine in practice, when you have ways to measure progress.

For example the objective "Land a team on the moon" is all-or-nothing, and has progress indicators such as "Orbit a team around the moon", "Orbit a team around the earth", "Prove mission control performance during a crewed mission", and so forth. Each of those all-or-none items can have sub-OKRs, sub-KPIs, sub-metrics, etc. as you wish.


It depends on what you are trying to accomplish. A lot of things like migrations can be expressed as “100% of traffic on $New_service”.




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

Search: