Aggregated OKR attainment
In the latest release of Gtmhub, we have added a highly requested feature – aggregated OKR attainment. This new metric shows the cumulative attainment of an OKR and all of it’s child OKRs.
When one aligns OKRs in Gtmhub, essentially one creates a tree. So far Gtmhub has been showing only the attainment of individual OKRs. We have kept this individual metric, as the main metric – because, in our opinion, it is ultimately the most important one. However, to help you spot any anomalies down the road, you can now see aggregated attainment both in the OKR detail view, as well as in the alignment view.
In the example above, we see an alignment view of our demo account. We can see that the Objective “Accelerate Growth” has an individual attainment of 0%, however, aggregate attainment is 13%. This 13% is calculated by summing the attainment of the OKR itself, in this case “Accelerate Growth” and all of it’s child OKRs, such as “Increase demand” or “Generate more quality leads” and then dividing it by the total number of objectives.
The aggregate attainment is visible for each objective, regardless of it’s position in the hierarchy.
Aggregate attainment is also visible in the detailed view of each objective.
In the screenshot above, we see that Objective “Grow Revenue from Existing Customers” has individual attainment or progress of 0%, however, because it’s supporting objectives are performing well, it’s aggregate progress is 41%.
Notes on using aggregate attainment
Aggregate attainment metric should be used as an indicator of anomalies and learning tool.
There is no guarantee that excellent execution of child objectives will result in same type of execution for the parent objective. In that case, one should inspect the possible causes. Many times, child objectives are just not as helpful as one has thought in supporting the parent objective.
In addition to this, when both individual and aggregate progress are low, one should examine the causes of this. Typically, in practice, this signals that the team has switched / lost focus – which could be fine, if it is intentional.