That only kind of helps ... and can lead to micromanagement.
I've found a better approach is to focus on key metrics or KPIs and empower people to go after them without a heavy planing cycle. Like if your app is slow and buggy the OKR process tends to favor waterfally quarter long projects like "rewrite X in Y." A better approach is often to get good at monitoring and prioritize cycles spent on maintaining, optimizing, and refactoring existing stuff with a possible incremental rewrite.
This isn't hard to fix; it only requires upper management to recognise the issue. If a goal is easy to reach, it's a bad goal.