Skip to content

Update Results for Customers operating principles

Devin Rogozinski requested to merge drogo-results-value-updates into main

Why is this change being made?

This MR captures changes to the Results for Customers value based on inputs from CEO, Chief of Staff, and VP, Talent & Engagement. As this MR is finalized, specific details about what is changing will be added below.

Here is what is changing and why:

  • Adding new values explainer video to the main page to help team members and new joiners understand all of our values and how they work together
  • Adjusting the definition of "Keep ens users in sight" for conciseness.
  • Clarifying the "customer results are more important than" section to help add more specific direction for team members
  • Clarify aspects of "measure impact, not activity" so it's clearer that flexibility and autonomy require delivering on expectations to happen.
  • Expect the definition of "dogfooding" to better explain how this helps us to achieve Results for customers
  • Remove operating principle "Write promises down" as it's now a part of what it means to "Set ambitious and measurable goals"
  • Adjust "Global optimization" to "Cross-functional optimization" to clarify that this operating principles relates more specifically to optimizing solutions for the entire company, across all functions.
  • Adjust "disagree, commit, and disagree" to "disagree, commit, and advocate" to clarify that we don't want to continue to disagree after committing, but that it's always appropriate to advocate for a different direction after a decision has been made.
  • Remove "Accepting uncertainty" as an operating principle as it doesn't relate directly to Results for Customers
  • Update "Escalate to unblock" definition to clarify this doesn't apply specifically to DRIs

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
Edited by Devin Rogozinski

Merge request reports