Managing OKRs at scale is not simple. This is one of the key problems Gtmhub solves.

The three main dimensions we focus on is:

  • alignment
  • transparency
  • manageability

With the latest bulk management features – based on actual use cases – Gtmhub makes the process of planning and managing OKRs not only significantly simpler, but also – enjoyable.

The new bulk editor is available in all editions, through the bulk function.


As organization aligns itself around business goals and priorities, very often objectives get reassigned between people – to ensure that no one has too much on their plate and can fully focus.

This is why we have introduced bulk assigning and reassigning.


Another common use case is simply postponing OKRs for the next quarter. As we often say, OKRs are just as much about deciding what not to do, as they are about deciding what to do.

This use case is the reason why we’ve introduce bulk moving of objectives between planning sessions.

Doubling-down or simply doing a better job

OKRs are aspirational by their very nature. There are two typical side-effects of this:

  • sometimes we get surprised by how well something works, so we decide to double-down on that OKR in the next planning period
  • other times, we fell short of achieving our objective – so we decide to try harder in the next period on the same OKR

For this use case, we’ve introduced ability to clone OKRs from one planning session into another.

Brainstorming or bottom-up approach

Many organizations choose a bottom-up approach with OKRs and foster employee engagement. In this scenario, employees are encouraged to define OKRs themselves and then teams collectively decide on which ones are to be pursued.

The side effect of this approach is that many OKRs will not be used and need to be deleted.

For this scenario, we’ve implemented a bulk delete operations.

Did this answer your question?