Simplify and improve cross-functional alignment and coordination with Key Result relationships, enhanced with embedded AI.

The Key Results of one team often link to other objects in WorkBoard. For example, a Key Result may:

• Depend on another Key Result
• Be blocked by the completion of an Action
• Be supported by a Workstream
• Be related to something in an external link
• Be a lagging indicator of a project in Jira

You can indicate these relationships (and more) in WorkBoard by utilizing Key Result relationships. In addition, you can utilize embedded AI to suggest objects that are likely connected to the Key Result.

Creating these relationships in WorkBoard has several benefits:

• All users can see relationships and dependencies so everyone is on the same page
• It makes it simple to check the status of blockers right from the Key Result
• Identify dependencies that you weren’t aware of from AI suggestions

Add relationships to a Key Result

Add a relationship from the Key Result details page

• Locate the 'Relationships' section on the right side of the page
• Use the plus + button to search and select a Key Result, Workstream, Action, Risk, Assumption, bodies of work from Jira, or other external systems as links
• Select Save to lock in your changes

Add a relationship from the edit panel

• From the Objectives module, select the kebab menu (3 dots) next to the Key Result
  • Alternately, click the pencil in the upper right-hand corner of any Key Result details page
• Scroll down to select Add key result relationships
• Use the plus + button to search and select a Key Result, Workstream, Action Item, bodies of work from Jira, or other external systems as links
• Select Save to lock in your relationship, and Save again to save your Key Result

Note: you will need edit rights to the key result in order to add or modify relationships

Notes about adding Key Result Relationships

• By adding a relationship to a cross-functional team or related element, you're able to specify the nature of the relationship between the two objects.
• These relationships do not affect the calculation of the KRs, they simply offer a visualization to indicate how objects are connected.
• If you indicate a relationship, it will appear on both objects. For example: 

  • If you specify that Key Result A depends on Key Result B.

  • Key Result B will also reflect that it is now a dependency for Key Result A.
• Capture supporting work from Jira, or link to bodies of work from other external systems so the key result can serve as a single pane of glass and pathway to all the intersecting work that is needed to drive the outcome forward.

Relationship types

Key Results allow several kinds of relationships:

• Supports / Supported by: Something that contributes to the success of a Key Result, but is not a hard requirement, supports the KR.
• Blocked by / Blocks: Something is currently preventing progress on a Key Result, and must be dealt with before progress can be made, blocks the KR.
• Lags / Leads: Something that is a headlight indicator that a KR is on track leads that KR. Something that is a taillight indicator that the KR was achieved lags the KR.
• Relates to: This is a general purpose, generic relationship that can be used as a catch-all for anything connected to the KR.

Add Key Result Relationships to a Scorecard

Add the Key Result | Relationships column to any Scorecard. With one click, you can view all the relationships for every Key Result in the Scorecard in the familiar Scorecard table format.

Hover over any Relationship cell to view a popover with clickable links to related items.

Filter to show specific relationship types such as Dependencies, Lags/Leads, Risks or Assumptions.

Manage Risks, Assumptions, Issues & Dependencies (RAID)

If your organization uses the RAID framework, you may benefit from adding Risks, Assumptions, and linking Dependencies. These can easily be added directly from the Relationships modal and will generate a relevant Action to track. The following relationships can be tied to this framework:

• Has risk/Risk to: Potential threats or challenges to the project's objectives, scope, schedule, or resources. The likelihood of encountering a specific issue or the chance of an adverse outcome happening. 
• Assumes/Assumed by: The components of the project are affected by assumptions, highlighting the areas of the project most at risk if an assumption proves incorrect.
• Depends on / Dependency for: Something that must be achieved as a necessary condition for the success of a Key Result, but is not actively a blocker, is a dependency for the KR.

When selecting a Risk or Assumption, it will default to match the selected relationship. For example, when selecting Risk to from the dropdown, a Risk will automatically be populated after saving.

Leveraging AI relationship suggestions

Capture lateral results alignment and blockers easily from our suggestions; suggestions are surfaced to you, so you don't have to hunt for them

• Click on the potentially related button in the Relationship Section
• Hover over the suggested items for more information such as Team name and owner
• If the suggestion is relevant, select the nature of the relationship and click the + button to save
• If the suggestion isn't relevant, click on Dismiss to get it out of the way

Notes regarding Timelines:

• WorkBoard is rolling out this enhanced capability starting November 6th as part of a phased roll-out. If you don't see these capabilities in your instance, reach out to your CSM.

Notes regarding shifts and deprecated features:

• Connections established as part of Related Work and Key Result Dependencies are now part of this new relationship widget and can be managed from here.
• The Key Result Alignment Tree has been deprecated as part of this rollout. In early 2024, WorkBoard will reintroduce a visual relationship map that will incorporate all relationships.

Create A Risk, Assumptions & Dependencies (RAID) tracker

• All 3 Key Result | Relationships columns
• Filter the relationships to just the ones concerned with Risks & Rename the column Risks
• Repeat on the other two columns for Assumptions & Dependencies