EXAMPLE OKR Review: An OKR for mediating inter-team project dependencies

OKRs Review my OKR!
, ,
1

OKR Objective

Eliminate project blockers caused by misaligned cross-team dependencies to ensure Q3 deliverables ship on time.

OKR Key Result

  1. Map and document 100% of inter-team dependencies for the “Project X” launch by Week 2.
  2. Reduce “Blocked” status time on shared tickets from an average of 5 days to <24 hours.
  3. Establish a bi-weekly “Dependency Sync” where 100% of identified risks are assigned an owner and resolution date.

Is this a Team Goal?

Issues to discuss

We need to agree on a “contract” for how requests are prioritized between Team A and Team B. Currently, ad-hoc Slack messages are getting lost; we propose moving all dependency requests to a specific Discourse category or using the Discourse Assign plugin to track ownership formally.

Ambiguity in Terminology: Are we using unclear or overloaded terms? (e.g., does ‘completed’ mean launched to 100% of users, or just code merged?)

Cross-Team Dependencies: Does this OKR rely on another team that hasn’t committed to it? (The #1 cause of failure in matrix organizations)

Strategic Misalignment: Does this actually move the needle for the wider company goals? (Checking for ‘busy work’ vs ‘value work’).