Visibility control 🔒

While OKR methodology promotes transparency across the entire organisation, 10xGoals recognises that large enterprises often have sensitive objectives that require a limited audience.

Problem Statement

Use cases:

• There could be company objectives that could be confidential: (~large)

  • Cost reduction objectives (could have down-sizing of certain teams etc)

  • Highly secretive project from a strategic/ competitive angle; Market share at stake.

• At some level in the chain, it becomes public but before that it is not visible to anyone (medium)- Meesho and Grow requested for this;

• User has a few personal OKRs that he/she does not want to share with anyone (small) We would not optimise for this as we expect them to write this in their other apps;

• User is writing OKRs in private mode before publishing to anyone (~small) We would not optimise for this as you can write on notes and then bring it here and even if you did brainstorm here and do not want the log for it - You can create the OKR as a new one once it is final and delete this one.

Points to note

• Even though an objective is private, it is usually accessible by some set of users who are working on it or get affected by it. (Could be admins or other members)

• The privacy of an objective can be edited or changed at any time by the owner of the objective.

• Private objective's comments, likes, check-ins, etc. will only be visible to the designated list of viewers and only those user's see them in the all objectives view and not others.

Potential Solution

"Private" as a property of an OKR along with access control to some users

• A user can mark an objective as private in the create/edit flow. (Default, Obj's are public)

• A user can select a few user's who can see this private objective. (By default, no-one is selected and only creater & owner can see a private objective).

NOTE: A user may or may not select admin as the viewers. Admins will also not have access to private objectives?? Does that mean we need a super-admin role?

• Once a user marks something as private, all KR's below that get marked as private by default but can be made public. If a KR is public, and an O is private then we do not show the "Show alignment".

Note: The "show alignment" chain may or may not lead to a root objective anymore. If the root is public -> it will show till then if its not, the chain leads to the top-most public objective.

Open questions

• Do we need to give view access to private objectives to people outside of this private tree? [What % cases does this happen?]

• The admins can still view Private objectives while for everyone else they are hidden? Or this tree is hidden for the admin as well. [What % cases does this happen?]

• Does the KR owner (KR being private) under a private Objective see the parent or not?

Potential solves (Not recommended)

• Admins customise tabs for an Org: "All objectives tabs doesn't exist"

• Then also we will need "private OKRs" if we need to stop showing the chain till the parent because otherwise in "show alignment" I would see the entire chain.

Move and Paste Implications:

Note: Private objectives cannot be aligned upwards. An existing public objective can be aligned to a private OKR if the person has view access :P