Updating Customer-centric value

Why is this change being made?

💡 Provide a detailed answer to the question on why this change is being proposed, in accordance with our value of Transparency.

We are shifting the C in our CREDIT values to Customer-centric from Collaboration. The addition of Customer-centric is an acknowledgment of the importance of external collaboration as we grow. Avoiding overly focusing internally will help drive our success as a company.

This update does not mean that we no longer value effective collaboration, but adds the priority of external collaboration. Collaborative work is required to achieve high quality results. Collaboration is a way of working that is built into GitLab the product, and in turn, built into the structure of GitLab the company. The operating principles from Collaboration are applicable to many of our CREDIT values and will be integrated into those, as well as our Communications page.

If you feel passionate about adding an operating principle to the new Customer-centric value and want to contribute, submit an MR with your idea.

Author and Reviewer Checklist

Please verify the check list and ensure to tick them off before the MR is merged.

• Provided a concise title for this Merge Request (MR)
• Added a description to this MR explaining the reasons for the proposed change, per say why, not just what
  • Copy/paste the Slack conversation to document it for later, or upload screenshots. Verify that no confidential data is added, and the content is SAFE
• Assign reviewers for this MR to the correct Directly Responsible Individual/s (DRI)
  • If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the Maintained by section on the page being edited
  • If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in #mr-buddies
  • The when to get approval handbook section explains the workflow in more detail
• For transparency, share this MR with the audience that will be impacted.
  • Team: For changes that affect your direct team, share in your group Slack channel
  • Department: If the update affects your department, share the MR in your department Slack channel
  • Company: If the update affects all (or the majority of) GitLab team members, post an update in #whats-happening-at-gitlab linking to this MR
    • For high-priority company-wide announcements work with the internal communications team to post the update in #company-fyi and align on a plan to circulate in additional channels like the "While You Were Iterating" Newsletter

---