>And then customers complain that the driver is frequently crashing and the team is well aware but won’t fix the ticket because it doesn’t help them meet OKRs.

>And then customers complain that the driver is frequently crashing and the team is well aware but won’t fix the ticket because it doesn’t help them meet OKRs. You highlight the danger of goal setting - where the goal becomes an end onto itself. I disagree with your adjustment however. It's too vague as written, and if you attach KRs to it, you'll end up where you started (with a KR like 'improve fps performance of game X by 25%') Ideally, you fix the issue, but you track it as having impact on achieving the OKR. Achieving OKRs should not be seen as a "be-all and end-all" ... Failing an OKR should be seen as a opportunity for improvement. If the corporation sets a goal of improving game FPS performance but is unable to meet it because of technical debt, that is good information that needs to be managed.