We all know that Objectives and Key Results (OKRs) are about alignment, focus, engagement, and transparency . In the real world, however, there are situations when there could be too much transparency.
When private OKRs make sense?
Many of our customers have shared with us use cases for private OKRs.
Many time managers and employees set objectives that are personal in nature and is not prudent to be shared with their colleagues. For example “be more polite in meetings” or “help more your colleagues” is a valid objective for an employee, but could have unintended consequences if visible to peers.
Legally confidential OKRs
In highly regulated or competitive organizations, many times there are objectives that simply cannot be known to all of the company. This is again a valid use case for private OKRs.
A typical example of these kinds of OKRs is downsizing or layoffs. While unfortunate, businesses do find themselves in situations where there is a need to take such drastic measures. Due to sensitive nature of such objectives, which require careful communication, private OKRs again make sense.
Introducing Private OKRs in Gtmhub
To address this use cases, we have provided our customers with the ability to define private OKRs in Gtmhub.
To create a private OKR, all one has to do is mark the “Make this objective private” checkbox when creating a new objective.
Creating private OKRs in Gtmhub
Who can see private OKRs?
The important question is who can see them?
Private OKRs can be seen by the person who created the OKR, their manager and all the managers up the chain in the org chart .
Org chart in Gtmhub
It is worth noting that everyone will see the existence of a private OKR, but not the content of it. This way, we bridge both the need for structure and alignment with a need for privacy.
Private OKRs for users that don’t have rights to see them