Finance Team Performance Indicators

1. You are here:
2. Handbook
3. Finance
4. Finance Team Performance Indicators

On this page

• Executive Summary
• Key Performance Indicators
• Other PI Pages
• Legends
  • Health
  • Instrumentation
• How to work with pages like this
  • Pages
    • Helper Functions
  • Data

Executive Summary

KPI	Health	Status
Average days to close	Unknown	tbd
Scalable Employment Solution	Unknown	tbd
Deliver Quantified Savings	Unknown	tbd
New hire location factor - Finance Team	Unknown	tbd

Key Performance Indicators

Average days to close

The number of business days required to report final monthly financial results. As a private company our target is 10 business days moving to 5 business days as a public company. This analysis can be found on the [Finance Dashboard](https://app.periscopedata.com/app/gitlab/483606/Finance-KPIs?widget=6500157&udv=780777). The days to close is sourced from the accounting close checklist.

Target: 10

Chart (Sisense↗)

Status: Unknown

• tbd

Scalable Employment Solution

GitLab has contracted team members in multiple countries and is instilling a scalable employment solution for 100% of its team members. A scalable employment solution may include hiring through a PEO, hiring through a contractor's entity or, where possible, a direct contract. The percentage is calculated as a percentage of contractors covered by a scalable employment solution in relation to the total workforce.

Target: 100%

URL(s)

• https://app.periscopedata.com/app/gitlab/483606/Finance-KPIs?widget=8484068&udv=759581

Status: Unknown

• tbd

Deliver Quantified Savings

Cost savings are achieved through the procure to pay process. Savings are calculated as the savings achieved by comparing the initial vendor proposal price to the final purchase price. In the event of a contract renewal, in addition to the above, savings can also be calculated as the savings achieved by comparing the previous cost per unit (eg. user, business metric, etc.) to the final cost per unit. Savings negotiated at the cost per unit level are also cost savings to be calculated as savings. Note these savings are not directly tied to budget. This aligns with the following core business objectives, control spend and build a culture of long-term savings on procurement costs, streamline the purchasing process, and minimize financial risk.

Target: greater than 3,000,000 over a rolling 12 month period.

This KPI cannot be public.

URL(s)

• https://app.periscopedata.com/app/gitlab/483606/Finance-KPIs?widget=8533898&udv=0

Status: Unknown

• tbd

New hire location factor - Finance Team

This is a subset of an existing KPI. Please see the definition for the parent KPI.

Target: < 0.73

Chart (Sisense↗)

Status: Unknown

• tbd

Other PI Pages

• Performance Indicator Maturity Table
• Engineering Function Performance Indicators
  • Development Department Performance Indicators
    • Growth Section Performance Indicators
  • Infrastructure Department Performance Indicators
  • Quality Department Performance Indicators
  • Security Department Performance Indicators
  • Support Department Performance Indicators
  • UX Department Performance Indicators
• Product Performance Indicators
• Corporate Finance Performance Indicators
• Recruiting Performance Indicators
• Data Team KPI Index

Legends

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

Instrumentation

Level	Meaning
Okay	We are correctly capturing and measuring data for GitLab.com and self-managed instances.
Attention	Missing one of: GitLab.com or self-managed data.
Problem	Missing both: GitLab.com and self-managed data.
Unknown	Unknown

How to work with pages like this

Pages

Pages, such as the Engineering Function Performance Indicators page are rendered by an ERB template that contains HTML code.

• Any changes to the Performance Indicator (PI) ERB template will cascade to all links under the Other PI Pages section
• To update the options for the maturity table, make changes to the Performance Indicators Maturities ERB file
• To update the way each individual (K)PI displays:
  • make changes to the Performance Indicators List ERB file for how the (K)PI is displayed on the KPI Index page
  • make changes to the Performance Indicators ERB file for any other properties and its format
• When adding a new PI page,
  • create the new PI page in the business division's handbook section (like the Engineering Division page)
  • include the relative link to the PI page in the Performance Indicators List ERB file
  • add all the (K)PI information into the Performance Indicators data file

Helper Functions

These ERB templates calls custom helper functions that extract and transform data from the Performance Indicators data file.

• The kpi_list_by_org(org) helper function takes a required string argument named org (deparment or division level) that returns all the KPIs (pi.is_key == true) for a specific organization grouping (pi.org == org) from the Performance Indicators data file.
• The pi_maturity_level(performance_indicator) helper function automatically assigns a maturity level based on the availability of certain data properties for a particular PI.
• The pi_maturity_reasons(performance_indicator) helper function returns a reason for a PI maturity based on other data properties.
• The performance_indicator_target(name) helper function returns the target value from the target property for a specific PI from the Performance Indicators data file.
• The performance_indicators(org) takes a required string argument named org (deparment or division level) that returns two lists - a list of all KPIs and a list of all PIs for a specific organization grouping (department/division).
• The signed_periscope_url(data) takes in the sisense_data property information from the Performance Indicators data file and returns a signed chart URL for embedding a Sisense chart into the handbook.

Data

The heart of pages like this is the Performance Indicators data file which is in YAML file. Each - denotes a dictionary of values for a new (K)PI. The current elements (or data properties) are:

Property	Type	Description
name	Required	String value of the name of the (K)PI
base_path	Required	Relative path to the performance indicator page that this (K)PI should live on
definition	Required	refer to Parts of a KPI
parent	Optional	should be used when a (K)PI is a subset of another PI. For example, we might care about Hiring vs Plan at the company level. The child would be the division and department levels, which would have the parent flag.
target	Required	The target or cap for the (K)PI. Please use Unknown until we reach maturity level 2 if this is not yet defined.
org	Required	the organizational grouping (Ex: Engineering Function or Development Department)
is_key	Required	boolean value (true/false) that indicates if it is a (key) performance indicator
health	Required	has two additional elements/property - level (inclusive value between 0-3) and reasons. This should be updated monthly before Key Meetings by the DRI.
urls	Optional	list of urls associated with the (K)PI
sisense_data	Optional	contains elements/properties related to Sisense, including chart (numeric Sisense widget ID), dashboard (numeric Sisense dashboard ID), shared_dashboard (Sisense shared dashboard ID), embed (v2)
public	Optional	boolean flag that can be set to false where a (K)PI does not meet the public guidelines.
instrumentation	Optional	has two additional elements/property - level (inclusive value between 0-3) and reasons. This should be updated monthly before Key Meetings by the DRI.

Here are some additional tips:

• Each KPI chart should be a timeseries chart.
• Each KPI should have a standalone dashboard with a single chart representing the KPI and a text box with a link back to the handbook definition.
  • In Sisense, create a shared dashboard link to get the shared dashboard ID.
  • In Sisense, use the Share Link action of the chart to get the chart (widget_id) and the dashboard ID.
  • Add the shared_dashboard, chart , and the dashboard key-value pairs to the Performance Indicators data file under the sisense_data property
• 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 display a value between 0 and 3 (inclusive). The health value is a manual input while the maturity is an automated value based on other discrete (K)PI data properties.