> Keeping something static (like keeping a metric at a particular number) is not a key result.
I could easily imagine a support team having an objective to keep the backlog of queries low. And to be pedantic, any metric can be expressed as “keep difference between metric x and expected/desired value y close to zero”, so there must be something deeper here.
IMHO that article quotation is wrong, and you're right. Static OKRs can be great for support teams, reliability engineering, service queues, recurring maintenance, periodic compliance, etc. Static OKRs can be as inspiring as dynamic OKRs, especially for highly motivated teams.
A popular example is the objective of 99.999% uptime. This is a superb goal, and when you achieve it there's a ton of ongoing work to keep it-- it's akin to a fine restaurant that earns a Michelin Star, and works very hard to keep it.
> Keeping something static (like keeping a metric at a particular number) is not a key result.
I could easily imagine a support team having an objective to keep the backlog of queries low. And to be pedantic, any metric can be expressed as “keep difference between metric x and expected/desired value y close to zero”, so there must be something deeper here.