[maytc]

Helping teams know what to say "no" to is the real power of OKR.

You do that by having the entire organization's O and KR roll up and cascade down. My Objectives directly roll up to my parent organization's Key Result. My parent org's Objectives rolls up to their parent's KR, and so on to the top. Then, you have the top-level check downwards if the sets of OKRs still make sense in their entirety.

Unfortunately, I have never seen any organization I was with ever do this...

[Macha]

That requires the high level OKRs to not be vague BS, because otherwise the team wanting you to do extra work can justify everything. Like the exec level OKR might be something like "customer first", which literally any feature work could be justified under (or is often used as an excuse to try push out needed technical work)

[darkwater]

I have seen company-wide Objectives that are basically euphemisms for "make more money". No shit, Sherlock! I can be a CEO as well!