The point of OKRs is to make sure you are actually working on relevant projects and not burning time on something nobody actually wants or needs. Happens much more than you would think.
No amount of process is going to fix brain-dead management.
It was not a good use of software developer salaries. An initiative to at least start collecting the data we needed so it might be useful in 2-3 years could have been, but some OKRized version of "start collecting data to use in OKRs 12 quarters from now" wasn't something anyone would get behind and was pretty much impossible to tie to the higher-level OKRs that were being set.
Whole thing was a game to find something easy to measure that could be made to look useful, whether it was or not. It wasn't some huge disaster or anything and I can see how maybe in exactly the right organization it might work, but there's no way it was the right place for that company to spend their money.
So I (and everyone around me) don't take them seriously. We take the actual deadlines seriously. The only thing OKRs seem to do is provide direction to the higher ups about what my team is up to.
I started working from coffee shops until they just dropped the OKR system and every manager wasting the whole company's time on it had "moved on for personal reasons"
I had forgotten about this repressed nightmare, I'll remember that next time I am fawning over the hip location and catered meals