Define a process to remove a GitLab Handbook sub-value

Background

Our list of GitLab Handbook sub-values has grown over the years into a very large list which has the effect of diluting the Core Values.

Core Value	Total Number of sub-values
Collaboration	20
Results	15
Efficiency	15
Diversity	19
Iteration	19
Transparency	14

If you have 1000 priorities then nothing is a priority. Given how important our values are to us, it is important that we manage and refine them intentionally.

What problem are we trying to solve?

The current problem trying to be solved here is for us to do a better job of maintaining the list of sub-values ensuring that as we grow we maintain a clear list of high quality sub-values.

What is the proposal?

This is a proposal to create a process for removing a GitLab sub-values. As part of this proposal there must be agreed upon issue template:

An issue template will be created for a Request to remove a sub-value to the GitLab Values Page with the checkboxes below. Checking at least one of the checkboxes below will be required to submit a request to remove a sub-value from the GitLab Values page.

• This sub-value is a duplicate of an existing sub-value.
• This sub-value is not actionable
• This sub-value is vague and is too open to interpretation
• This sub-value can be combined with other sub-values to create one sub-value
• Other

Process for removing sub-values

Values are not just things we do but things that actively drive good behaviour. When we remove them it doesn't mean we stopped believing in it, just that it wasn't actively helping to drive behaviour. If we don't prune our sub-values, then we will be like every other company, things that make sense but are not leading to a better culture.

1. A Team Member must submit a Merge Request to remove a sub-value from the Handbook Page
2. The GitLab Value Handbook Page owner must approve and merge the request.

What are you being asked to do?

1. Review the proposal and provide comments
2. Make additions ➕ or subtractions ➖ to the proposed templates

What is not in the scope of this proposal

This proposal will not address which specific sub-values we should remove. Future MRs will be created to address that exact point. 👣 In order to proceed in an iterative manner, the first step is to define the process and agree on the issue template content.