What is the difference between aligning and linking objectives?
Setting the relationship between two (or more) OKRs is important for monitoring your company's progress and it can be done by either aligning or linking them.
Aligning OKRs is a fundamental aspect of the OKRs process where it's expected that everyone pulls in the same direction and achieve the business goals.
Linking OKRs is an additional parameter of Gtmhub objectives which allows you to indicate a relation between a given objective and one other objective from different session.
Aligning Objectives is a function that allows you to set a parent-child relationship between two or more Objectives from either the same or different sessions.
Here's how to do that:
- Choose an Objective that you want to align with a higher level Objective;
- Click the Align Objective button that is under the Aligned under section;
- Choose a session;
- Choose an Objective and click the Select button.
ℹ️ When aligning Objectives, you can see the "parent-child" relationship by navigating to the Alignment view. Here's how it should look like:
Linking Objectives is a function that allows you to support an Objective from different sessions without being aligned with it.
Here's how to do that:
- Choose an Objective that you want to relate it to another one from a different session;
- Click on the Link objective button that is under the Related Items section;
- Select a session;
- Choose an Objective from the list and click the Select button.
When to use aligning?
The simplest use case for aligning OKRs is when an individual's OKRs are directly supporting her/his department/team/group's OKRs.
For instance, a personal OKR might be to "Bring MRR up to 15%" while the related OKR that is aligned to it may be "Skyrocket the North American monthly sales".
When to use linking?
OKRs in Gtmhub may support each other without being directly aligned.
This works especially well for dev/design/engineering teams whose work may be planned and executed in bi-/monthly cycles which are related to quarterly/annual company OKRs.
For instance, a monthly design team OKR might be "Identify three new use cases for "Feature X" which is directly related to the company's annual "Smash the product's new user adoption level" OKR. However, the two might not be aligned since other teams' OKRs (product and engineering) might also support it.