This page focuses on top performance indicators for Business Technology team. Data team metrics Procurement team metrics
Engineering Contribution Rate is a key indicator showing how productive our team members are based on two factors.
Target: TBD
FinSys Contribution Rate is a key indicator showing how productive our team members are based on the total change management issues that are completed per month.
Target: TBD
This performance indicator tracks the number of laptops that arrive before a team members start date.
Target: The goal is that 95% of laptops will arrive prior to start date.
This performance indicator measures how satisfied our customers' (internal GitLab team members) are with their interaction with the GitLab IT team. This is based on survey responses from team members.
Target: 95% CSAT
Note: This cannot be measured currently.
This performance indicator tracks against the SLA for requests.
Aligns with the following core business objectives:
Target: 95% SLA achievement
Note: This cannot be measured currently.
This performance indicator tracks the growth of the knowledge base across teams.
Aligns with the following core business objectives:
Data Team
IT Systems
This performance indicator is tracked by several metrics including: Infrastructure Cost vs Plan and Hiring Cost vs Plan. This PI is to track the financial position of all the team cost vs. the budget set by the team.
This performance indicator tracks the efficiency of new or updated system or processes.
Aligns with the following core business objectives:
This performance indicator tracks the time it took to roll out a new system vs the planned time for that system roll out.
Aligns with the following core business objectives:
These performance indicators track the coverage of security tools on systems belonging to active Okta accounts. An account is considered active if it has logged into Okta at least once within the last 21 days. Contractor, service and admin accounts are excluded from the count of active Okta accounts. Active accounts are further split between MacOS and Linux systems, although some users may use both (and will be counted in both totals).
To avoid double counting, only one system per operating system type (i.e. MacOS or Linux) is counted per Okta account.
This metric counts the number of MacOS systems that have reported to the Jamf console in the last 21 days, and divides it by the total number of active Okta MacOS accounts.
This metric counts the number of MacOS systems that have reported to the SentinelOne console in the last 21 days, and divides it by the total number of active Okta MacOS accounts.
This metric counts the number of MacOS systems that have reported to the Jamf console that their filesystem is encrypted, and divides it by the total number of active Okta MacOS accounts.
This metric counts the number of Linux systems that have reported to DriveStrike console in the last 21 days, and divides it by the total number of active Okta Linux accounts.
This metric counts the number of Linux systems that have reported to the SentinelOne console in the last 21 days, and divides it by the total number of active Okta Linux accounts.
