Engineering is on plan. But we are lending some of our recruiters to sales for this quarter. And we just put in place a new "one star minimum" rule that might decrease offer volume.
We are continuing to onboard new support agents and engineers so this average will be relatively dynamic as new people onboard. Still, we are in a healthy place for solving tickets and keeping pace.
Determine appropriate team metrics to continue to drive individual contribution to solving tickets.
Identify ways to match complexity to time to solve to differentiate expectations per support role.
While we have an overall ratio of less than 10:1 as a department at time of this evaluation, we have re-balanced the larger imbalance in EMEA with new management in place, and have plans for 3 additional managers to hire to accommodate growth in other teams.
Hire to plan for new managers.
Re-align ICs to new managers to restore balance.
Key Performance Indicators
Support Hiring Actual vs Plan
Are we able to hire high quality workers to build our product vision in a timely manner? Hiring information comes from BambooHR where employees are in the division `Engineering`.
Engineering is on plan. But we are lending some of our recruiters to sales for this quarter. And we just put in place a new "one star minimum" rule that might decrease offer volume.
Health: Monitor health closely
Maturity: Level 2 of 3
Needs periscope data
Support Average Location Factor
We remain efficient financially if we are hiring globally, working asynchronously, and hiring great people in low-cost regions where we pay market rates. We track an average location factor by function and department so managers can make tradeoffs and hire in an expensive region when they really need specific talent unavailable elsewhere, and offset it with great people who happen to be in low cost areas.
We are at our target of 0.58 exactly overall, but trending upward.
We need to get the target location factors in the charts.
It will probably be cleaner if we get this in periscope.
We need to set the target location factors on our vacancies and make sure recruiting is targeting the right areas of the globe on a per role basis.
Maturity: Level 2 of 3
Needs periscope data
Support Satisfaction (SSAT)
A measure of how satisfied our customers' are with their interaction with the GitLab Support team. This is based on survey responses from customers after each ticket is solved by the Support team using a Good or Bad rating.
Collecting feedback from dissatisfied customers to identify trends.
Support Managers review trends to create changes to workflows and/or training.
Maturity: Level 3 of 3
Service Level Agreement (SLA)
GitLab Support commits to an initial substantive response in a specified amount of time from the time the customer submits a ticket. The SLA for this first reply is based on each customer's Support Plan.
Tracked and reported monthly, and for the year we are under our margin target for spend.
Maintain focus on spend while iterating on needs for non-headcount expense requirements.
Maturity: Level 3 of 3
ARR per support team member
This is a function of modeling for staffing to a ratio of ARR and not directly influenced by Support staff performance but more to our hiring which is managed through other performance indicators.
Determine the need to continue to track this as a KPI versus a Support Gearing Ratio to ARR for modelling hiring plans.
Maturity: Level 2 of 3
Needs periscope data
Average daily tickets closed per Support team member
The Gitlab support team aims to staff the team based on weighted average of both self-managed and GitLab.com tickets closed in a given month by an individual support team member involved in customer tickets. Total number of tickets closed / Total number of support staff.
Target: 65 tickets closed per support staff per month
We are continuing to onboard new support agents and engineers so this average will be relatively dynamic as new people onboard. Still, we are in a healthy place for solving tickets and keeping pace.
Determine appropriate team metrics to continue to drive individual contribution to solving tickets.
Identify ways to match complexity to time to solve to differentiate expectations per support role.
Maturity: Level 3 of 3
Manager to customer support rep ratio
The Manager to IC Ratio is the ratio of individual contributors to one manager. This data comes from Bamboo HR.
Target: The long term target for this metric is 10:1
While we have an overall ratio of less than 10:1 as a department at time of this evaluation, we have re-balanced the larger imbalance in EMEA with new management in place, and have plans for 3 additional managers to hire to accommodate growth in other teams.
Missing one of: description, target, or periscope data.
Level 1 of 3
Missing two of: description, target, or periscope data.
Level 0 of 3
Missing a description, a target, and periscope data.
Health
Level
Meaning
Okay
The KPI is at an acceptable level compared to the threshold
Attention
This is a blip, or we’re going to watch it, or we just need to enact a proven intervention
Problem
We'll prioritize our efforts here
Unknown
Unknown
How to work with pages like this
Data
The heart of pages like this is a data file called /data/performance_indicators.yml which is in YAML format. Almost everything you need to do will involve edits to this file. Here are some tips:
Avoid : in strings as it's an important character in YAML and will confuse the data parsing process. Put the string in "quotes" if you really need to use a :
urls: should be an array (indented lines starting with dashes) even if you only have one url
Both maturity.level and health.level take a number between 0 and 3 (inclusive)
Pages
Pages like /handbook/engineering/performance-indicators/ are rendered by and ERB template.
These ERB templates call the helper function performance_indicators() that is defined in /helpers/custom_helpers.rb. This helper function calls in several partial templates to do it's work.
This function takes a required argument named org in string format that limits the scope of the page to a portion of the data file. Possible valid values for this org argument are listed in the org property of each element in the array in /data/performance_indicators.yml.
