Overview

Gtmhub provides multiple ways to support bidirectional goal setting and objective progress calculations depending on what you're trying to model.

The relationships between objectives and key results fall in one of two categories. They can either contribute or support. Objects that contribute mean that progress calculations are affected, whereas those that support do not.

Alignment Type

Relationship

Progress calculation is affected?

Key result to objective (default)

Contribute

Yes

Child objective to objective

Contribute

Yes

Objective to key result

Support

No

Key result to key result

Contribute

Yes


Alignment types where calculations are affected

When you create an objective, you have the option to calculate progress in one of three ways:

When you create a key result, you have the option to cascade that key result. For more information, see Cascade down key results.


Objective to key result alignment

Sometimes when you create a key result, you want others to align their objectives to it. With this form of alignment, teams can focus on controllable inputs to achieve the desired result. This is one way to cascade OKRs at scale.

Here's an example of what that might look like in the real world.

Let's say you want to Increase eNPS. This is a quantifiable metric that you want to improve. When you share this with your teams, they can be thinking about how to improve this key result.

Increase eNPS = f(Celebrate wins + Invest in employees)

In this example, the organization is saying they believe increasing eNPS is a function of the aligned objectives. In other words, if the Celebrate wins and Invest in employees objectives are achieved, we would expect increase eNPS to improve. As you review the results over time, you can see if your hypothesis is correct.

NOTE: This is an alignment type where progress does not roll-up.


See also

Did this answer your question?