With the document policy changes over the last 5 years, most decisions are now very opaque. Google TTLs everything except Docs and code history & reviews, at this point: emails, chats, bug reports, ...
There's probably a tech debt focused OKR for this work, but some other teams probably has OKRs that indirectly benefit from the data, and they're probably providing staffing support, tied to the tech debt OKR. OKRs are for telling people why you're great, if you're at the bottom of the pyramid, and for giving the rank-and-file some direction, if you're at the top. The top level OKRs are usually very precise and very vague at the same time.
So there's probably an OKR in search to improve the quality of the location signals. It can be vague on how. Plus, having more and better data filters into your downstream systems, so even without an OKR for the data you know it will make your models more powerful.
There's probably a tech debt focused OKR for this work, but some other teams probably has OKRs that indirectly benefit from the data, and they're probably providing staffing support, tied to the tech debt OKR. OKRs are for telling people why you're great, if you're at the bottom of the pyramid, and for giving the rank-and-file some direction, if you're at the top. The top level OKRs are usually very precise and very vague at the same time.
So there's probably an OKR in search to improve the quality of the location signals. It can be vague on how. Plus, having more and better data filters into your downstream systems, so even without an OKR for the data you know it will make your models more powerful.