Duh, obviously I want "shipping the roadmap" in the OKRs. OKRs should capture everything you plan to do, otherwise what's the point? Obviously I don't want the whole roadmap, just the part we commited to. You probably also don't want only the roadmap, for obvious reasons.
There's never enough time to do everything that's planned or necessary and OKRs should be the tool that lets you resolve the conflicts. Ship feature X or fix the infrastructure? "X is in OKRs, let's work on X". "X is not in OKRs and we have KR to get Y% success on autodeployments, let's fix infra".
What I definitely don't want is "do OKRs and also do roadmap". The only things that should not be in the OKRs are ones where prioritization is trivial (like "fix critical outages").
There's never enough time to do everything that's planned or necessary and OKRs should be the tool that lets you resolve the conflicts. Ship feature X or fix the infrastructure? "X is in OKRs, let's work on X". "X is not in OKRs and we have KR to get Y% success on autodeployments, let's fix infra".
What I definitely don't want is "do OKRs and also do roadmap". The only things that should not be in the OKRs are ones where prioritization is trivial (like "fix critical outages").