|Acquisition and Conversion (IACV)||
|Expansion and User Retention||
Increased value in customer bookings on gitlab.com by acquiring new customers and upselling existing customers to a higher tier through data driven initiatives that help surface our existing capabilities to prospective and existing users.
Reduced customer churn on gitlab.com by identifying and re-engaging customers that have created accounts but have not adopted our product.
|Has a description, target, and periscope data.|
|Missing one of: description, target, or periscope data.|
|Missing two of: description, target, or periscope data.|
|Missing a description, a target, and periscope data.|
|The KPI is at an acceptable level compared to the threshold|
|This is a blip, or we’re going to watch it, or we just need to enact a proven intervention|
|We'll prioritize our efforts here|
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:
: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
health.leveltake a number between 0 and 3 (inclusive)
/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