Writing
Why I built OKR Orca
Most OKRs I review measure the work done rather than the change it caused. “Launch the new onboarding flow” is a launch. You can ship it and still have learned nothing about whether users are better off.
I review OKRs for teams every week, so I turned the rubric I use into OKR Orca. You paste an OKR, it scores it against seven named criteria, names the anti-patterns, and walks you through fixing it one issue at a time.
Each rewrite shows its reasoning, so you can see how it got from your line to the proposed one and edit it if the assumption is wrong. A key result with no baseline and no target gets flagged.
There is a small free allowance per day. Bringing your own API key removes that daily limit. The tool works without an account, and the rubric is deliberately opinionated. I would rather fix the rubric than defend it.