Skip to content

Remove Accountability Sub-value

Darva Satcher requested to merge drs-remove-accountability into master

Background:

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.

*In some cases we keep the spirit of the sub-values that we are removing and possibly place them under other sub-values.

Currently this is part of a larger effort to go through all of the sub-values on the Values page to ensure that our values remain strong and are not ambiguous and that they are actively helping to drive behavior.

Currently we are focusing on Transparency.

Purpose:

The purpose of this MR is to remove the Accountability sub-value.

Proposal

I propose that we remove the Accountability sub-value.

Explanation:

In order to remove a sub-value from the GitLab values page, please review the [process for removing sub-values}(https://about.gitlab.com/handbook/values/index.html#process-for-removing-sub-values) in the handbook.

Please indicate the reasons for removing this sub-value (note: a sub-value must meet at least one of these criteria to be removed):

  • 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

Duplicate

This sub-value is a duplicate of content located in the Say why, not just what sub value:

Saying why does not mean justifying a decision against all other suggestions. The DRI is responsible for their decision. The DRI is not responsible for convincing other people, but they should be able to articulate their reasoning for the change.

Accountability sub-value

Increases accountability when making decisions and difficult choices.

Vague

I think this can be interpreted in many different ways. If we were to keep this, I'd like to have more context.

There is also additional conversation here about this sub-value.

Merge request reports