God yes. This happens so often.

I.e. — “processing X data” is slow and the KR describes the measurable value that would mean we have eliminated that weakness.

I also prefer “pairs” of metrics or conditions that must be met when achieving the quant part of the KR, like “no quality loss”. Prevents bullshit tactics.

This has worked for me in practice, even if it might be OKR heresy:

O’s = core advantages/differentiators/strategy of our product. They rarely change. Something like “speed of delivery”.

KRs are defined as very concrete weaknesses in the O, like “process X data under 10s w/ no loss of quality”.