Update How We Measure Impact in Data team handbook section

Why is this change being made?

• In preparation for the 2024-07 Key Review, we reevaluated metrics for data adoption. Tableau Adoption % is being removed because (a) we are no longer measuring the number of users who are still using the old BI tool which has since been sunset and (b) an increase in Adoption % can point to more active users, or to inactive users being unlicensed. Since we are now deprovisioning inactive users on a quarterly basis (decided upon in May 2024), this metric is going to be volatile and would appear to be artificially inflated even if the # of active users stays stable. As such, it is more indicative of adoption to report on the raw number of active users in Tableau.

CHANGEME

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
  • Division: If the update affects your division, share the MR in your division 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

Commits

• update data adoption definitions

---