You can use a different framework here, but you can also just use OKRs too. I argue mixing OKRs and KPIs just muddies the water for little value. Even within e

You can use a different framework here, but you can also just use OKRs too. I argue mixing OKRs and KPIs just muddies the water for little value. Even within engineering, some teams are more geared towards “sustaining quality” than “expanding capabilities”. You can just as easily set a “maintain quality” or “sell our product” objective that may or may not have explicit initiatives, and call the KPIs from the article KRs instead. There is really no difference. You often see this within teams too; it’s best practice to have a quality metric as a guardrail to any growth metric (eg “add users, but don’t increase churn for existing” or “build new functionality, but don’t impact API uptime”). So you end up needing to represent these non-initiative-driven metrics that the article wants to call KPIs in your OKR system anyway. KISS!