I encounter this same problem. My teams do OKRs but they always end up using it as a way to confirm what they wanted to work on. In fact if something they wanted to work on is not reflected in the OKR, they modify the list of OKRs.
I like your suggestion. I’ll add one more, if management incentivized achieving business goals instead of project metrics (eg velocity, on-time delivery), then I think OKRs would be much more meaningful.
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.