This is a good insight. The biggest problem I've seen with OKRs is the desire to "align" them, which always ends up meaning that each manager rewrites their team's OKRs to fit into their director's OKRs and so on up the ladder. This doesn't "align" anything, it conceals a lack of alignment and makes it impossible to address whatever the underlying issue is.
It seems to me that if the result of an OKR process is a bunch of team OKRs that have little to do with the company strategy, the result of that should not be to repeat the process or rewrite the OKRs but for company leadership to spend the next quarter figuring out what's going on (communication issue, too many underlying technical struggles to be able to prioritize, the company strategy is bad and nobody understands or likes it, etc.).
In truth I kind of question the usefulness of "higher level" OKRs. They become too fuzzy and meaningless. Worse, I think it is almost impossible to come up with quantifiable key results that are directly influenced by the work of "lower level" OKRs.
It seems to me that if the result of an OKR process is a bunch of team OKRs that have little to do with the company strategy, the result of that should not be to repeat the process or rewrite the OKRs but for company leadership to spend the next quarter figuring out what's going on (communication issue, too many underlying technical struggles to be able to prioritize, the company strategy is bad and nobody understands or likes it, etc.).