OKR at an individual level work fine, but they need to be positioned as an individual OKR.
For example, reduce bug count report by 10%. Or, increase LOC by 10% without reducing quality (defined as bugs, DRY, PR comments), increase documentation written by 10%, increase Slack karma by 10%, etc
Obviously other metrics other than the OKR need to be maintained.
PRoduct owner is responsible for OKRs that scope across stories implemented, not ICs. Or at least not junior ICs. Architect level IC for example should be able to complete more broad scope.
For example, reduce bug count report by 10%. Or, increase LOC by 10% without reducing quality (defined as bugs, DRY, PR comments), increase documentation written by 10%, increase Slack karma by 10%, etc
Obviously other metrics other than the OKR need to be maintained.
PRoduct owner is responsible for OKRs that scope across stories implemented, not ICs. Or at least not junior ICs. Architect level IC for example should be able to complete more broad scope.