Skip to content

Clarify that PTO average includes all types of paid time off

François Rosé requested to merge francois/clarify-pto-average into master

Why is this change being made?

The Development Department Performance Indicators page includes a PI named "Average PTO per Development Team Member". It has been hovering around 4-4.5 days/month (except December) in the past 2 years. This means a rough average of 50 days per year.

https://about.gitlab.com/handbook/engineering/development/performance-indicators/#average-pto-per-development-team-member

As a new joiner, when I first saw this data point, I assumed "PTO" meant "vacation days". When I am on sick leave, I personally do not think of it as "personal time off" (PTO), although it is indeed "paid time off" (also PTO).

Consequently, I assumed that the graph was plotting vacation days taken by team members, and suggesting that on average people take 50 days of vacation a year.

After inspecting the underlying dataset in Sisense, I realized that this PI includes all types of time off that a team member takes in a given month, not just vacation.

This MR provides a more explicit description of the PI, to avoid setting incorrect expectations when it comes to taking time off, in particular vacation days.

Author Checklist

  • 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
  • If the changes affect team members, or warrant an announcement in another way, please consider posting an update in #whats-happening-at-gitlab linking to this MR
    • If this is a change that directly impacts the majority of global team members, it should be a candidate for #company-fyi. Please work with internal communications and check the handbook for examples.

Merge request reports