Every company is unique in the way they customize the OKRs process to achieve their desired outcomes. In many cases the process also dictate specific rules when it comes to ownership and accountability.

In this article we will explore:

Default ownership account settings

The ownership settings are applied account wide and take effect over all OKR sessions you have created, meaning any objective, key result and task created in your account will respect the rules set in the account settings.

To access the Who can own? options in your Gtmhub account you'd need an admin role or permissions to access the account settings.

Under Settings (the gear ⚙️ icon at the bottom left) > Configuration tab scroll down until you reach:

  • Who can own Objectives?
  • Who can own Key Results?
  • Who can own tasks?

By default Gtmhub allow objectives, key results and tasks to be assigned and owned by users and teams. However this can be further limited so it's either one or the other.

Adjust the ownership rules for your account

To update the ownership of objectives, key results and/or tasks in Gtmhub:

  1. Navigate to the account Settings (the gear ⚙️ icon in the bottom left corner)
  2. Scroll down to the Who can own options
  3. Choose the preferred option from the drop down menu: employees only, teams only, employees and teams.
  4. Click Save

ℹ️ The changes won't affect already assigned objectives, key results and tasks. They will apply for objectives, key results and tasks you will create or edit from now on.

Common ownership combinations

Aside from the standard combination of objectives and key results owned by employees and teams, there are few more combinations which we often see. Here are few real life examples you can consider implementing within your organization's OKRs process:

Objectives owned by employees + KRs owned by employees and teams

Purpose: enhancing clarity around the accountability over the respective goal.

Objectives are assigned to one person indicating that they are in full ownership of delivering the goal. For team owned goals, the manager is appointed as an objective owner.

KRs can be team owned or individually owned depending whether the team is supposed to contribute or an individual.

Objectives owned by teams + KRs owned by employees

Purpose: foster team work and collaboration where each person contribution is visible.

Objectives are assigned to the team, where team can be any group of people working on a common goal. Key results are owned by individuals from the team.

ℹ️ Gtmhub does not limit the number of teams each user can be part of. Many organizations create virtual or temporary teams in Gtmhub to suit the current needs of the business.

Objectives owned by employees + KRs owned by employees

Combination of the two above. Purpose: accountability on all levels.

Objectives are owned by individual, key results also have specific person assigned to them.

When it comes to Who can own tasks? the most preferred option is limiting the ownership to employees only in order to break down the work into smaller pieces and have visibility over the work that's being done and what's still left to be worked on.

ℹ️ Whatever your preferences for the Who can own? options would be, we encourage you to carefully consider what are the desired outcomes that your organization is aiming to achieve through OKRs and then adjust the Gtmhub account settings.

Learn more:

Limit the number of objectives per user

Limit the number of KRs per objective

Did this answer your question?