Gtmhub allows you to align and link objectives. Although the two features differ, they both promote transparency and focus, by establishing a relationship between the objectives. Setting the relationship between two or more OKRs is important for monitoring your company's progress.
The difference between them is the following:
Aligning OKRs is a fundamental aspect of the OKRs process where it is expected that everyone pulls in the same direction and achieve the business goals.
It allows you to set a parent-child relationship between two or more objectives from either the same or different sessions.
For more information, see Align sessions and objectives.
You can have one parent objectives and more than one child objectives, but one child objective cannot have more than one parent objective.
Linking OKRs allows you to support an objective from different sessions without being aligned with it.
It allows you to set a relationship between two or more objectives from either the same or different sessions that do not have a parent-child direction.
For more information, see Link objectives.
One objective can support many other objectives, so you can link one objective to more than one other objectives.
A simple use case for aligning OKRs is when an employee's OKRs are directly supporting the team's OKRs.
EXAMPLE: Personal OKR can be to Bring MRR up to 15%, while the related team’s OKR, which is aligned to it, can be Skyrocket the North American monthly sales.
OKRs in Gtmhub may support each other without being directly aligned. This works well for development, design, and engineering teams whose work may be planned and executed in monthly cycles which are related to quarterly or annual company OKRs.
EXAMPLE: A monthly design team OKR can be Identify three new use cases for Feature X. This can be directly related to the company's annual OKR to Smash the product's new user adoption level. However, the two may not be aligned, because the design team OKR can also support other teams' OKRs, such as product and engineering.