Teams that cannot credibly commit to delivering 1.0 on their OKRs must escalate quickly. This is a key point: escalation in this common situation is not only OK, but required. Whether the problem is due to disagreement on the OKRs, disagreement on their priorities, or an inability to allocate enough timepeopleresources, escalation is good. It allows the team’s management to develop options and resolve the conflict.
Corollary: Every new OKR is likely to involve some level of escalation, as it requires changes to existing priorities and commitments. OKRs that do not require changes to any team activities are business-as-usual OKRs that are unlikely to be new — although they may not have been previously documented.
Failure to achieve 1.0 on a committed OKR by its due date france mobile database warrants a post-mortem analysis. This is not intended to punish the team. It is intended to understand what happened during the planning andor execution of the OKR so that the team can improve their ability to reliably achieve 1.0 on the committed OKR.
Examples of the Commitment OKR category are ensuring that a service meets its SLA Service Level Agreement for the quarter; or delivering a defined feature or improvement to an infrastructure system by a set date; or manufacturing and delivering a certain number of servers at a certain cost point.
An aspirational set of OKRs will, by design, exceed the team’s ability to execute in a given quarter. The priority of the OKRs should inform team members’ decisions about where to spend their remaining time after completing their team’s commitments. Generally speaking, higher priority OKRs should be completed before lower priority OKRs.
Ideally, OKRs and their associated priorities should remain on the team’s OKR list until they are completed, and on a quarter-by-quarter basis as necessary. Removing them from the OKR list due to lack of progress is a mistake, as it masks ongoing issues with prioritization, resource availability, or lack of understanding of the problemsolution.
Corollary: Moving an aspiring OKR to another team’s list is a good thing if that team has the expertise and ability to accomplish the OKR more effectively than the current OKR owner.