OKR dependency resolution

This page highlights the problem statement and some potential solutions to help the dependency resolution process during the OKR set-up phase

Problem Statement:

Multiple teams call out dependencies on some core central functions like Product, Tech, Marketing etc. These functions then build capabilities which could be used by many teams horizontally. To dive deeper, there could be one of these situations possible: - 3 teams discuss together and only one of them creates an OKR and the other 2 then follow their OKR? - 2 teams assign something to team A. Then team A makes one combined OKR and shares with the 2 teams. The 2 teams then delete their OKRs and follow team A's OKRs. - All 3 teams in silo's create OKRs that are similar and now teamA decides to re-calibrate their OKR and thus share a final one for the other 2 teams to follow.

What happens in today's world?

• After collecting inputs from various teams, central teams take up initiatives and broadcast what they would be doing and what all teams objectives will get catered? And what hasn't been picked is also communicated?

• In the manage phase, the teams communicate major milestone with relevant teams and also if there are any major de-tractors to the earlier said plan.

Solution 1 (Merging KRs- Not recommended)

As clear from the name, merging of KR's is a partial solve for the case where there already exists all KR's that need merging. Rather a good solution would be which covers all the 3 cases described above. Meaning as soon as the final OKR is ready, there should be a way to follow/shadow it under your relevant OKRs such that its latest state is visible there. All the other OKRs can be deleted.

Solution 2 (Shadowing/Following KRs- proposed)

Whenever there is a KR that I need to follow. I can go to it select it and then just like paste, put it under any Objective. This would mean this KR exists at all places with same status and people are always aware of it.

Open Questions:

Irrespective of any solution, there are a few questions when we implement this multi-mapping of an OKR to several other objectives:

• Show Alignment to be shown with one primary parent? and others become secondary parents? How is this decided? By system or by user?

• Who all can edit this objective? Earlier logic allowed parent to edit it but now it would have multiple parents. Does it mean we set primary and secondary parents.

Solution 3 (Starring OKRs)

Pro's

• Does not add to the complexity of the software as "Star" can be used without having to introduce another feature ( Notifications to trigger for starred objectives as well?)

Con's

• User's loose sight of where this resides (as it's not under the Objective like other KRs)

• Chances of missing notifications is high and hence I am not on top of my O.

• Relies on the the dependency callers to star and follow. The owner of dependency doesn't have a control or cannot pro-actively do it for all followers together. Neither does he know if it's being followed and if people are getting updates on time or not.