The team member relations specialist is responsible for facilitiating and resolving all people matter related team member issues. They will also assist in creating and informing team members of policies that are fair and consistent for all GitLab team members. As part of the people group the team member relations specialist works with both the manager and team member in an intermediary function to understand and help resolve workplace issues. The team member relations specialist can also help coach and advise managers and team members on policies and processes.
Team member relation issues can range from simple coaching questions to serious code of conduct violations. We classify these different level of team member cases by tiers. Example of issues/cases by tier level:
All Tier 3 cases will be managed together with Legal and the TMR specialist.
Team members who would like to discuss a private matter should send an email requesting support from our Team Member Relations Specialist to email@example.com. Please include the following in your email:
The Team Member Relations Specialist will reach out within 24 hours from when the request was sent via email during the business week.
GitLab also offers a Harassment Complaint Form that any team member may use to document any instance of any type of workplace harassment. Simply copy the form, fill it out with your information and send it to our Team Member Relations Specialist at
Team members and the team member relations specialist should both respond to questions or queries via slack or email within 24 hours to continue making progress on the issue and get to a timely resolution. For US team members relations, GitLab has a US-based Team Member Relations Specialist. For EMEA and APAC team members relations, GitLab has an EMEA-based Team Member Relations Specialist.
For urgent requests that need immediate attention please ask for urgent assistance by sending a message marked URGENT to
firstname.lastname@example.org and in the #people-connect Slack channel. If you do not receive support in a timely manner, below is the escalation path:
An urgent request would be something that needs immediate attention like team members safety or a code of conduct violation.
GitLab believes in preserving the dignity of each team member and expects everyone to treat others with fairness, respect, and transparency. We encourage mutual responsibility for constructive work relationships and communication, information sharing, problem solving and a safe neutral processs through which differences can be resolved. Direct and honest communication is strongly encouraged between all team members regardless of title or level and per our values we do not pull rank. Such communication is likely to enhance understanding, avoid misunderstandings and create rapid solutions to concerns.
We have built this philosophy to focus on these 4 pillars in line with our values:
To support our team members, GitLab has established a Team member relations group to assist team members and their leaders with resolving work related issues. The Team Member Relations Specialist (TMR) respects the privacy of all team members and treats discussions with the fullest degree of confidentiality possible. We have incorporated our Values and the Code of Business Conduct and Ethics into our team member relations practices and philosophy. We believe that by communicating with each other directly and transparently, we can continue to resolve any difficulties that may arise and continue to make GitLab a great place to work.
The team member relations function provides all GitLab team members an avenue to express workplace concerns and to resolve conflicts in a safe and unbiased forum.
Team member relations provides guidance to managers in their efforts to improve team member performance or to correct unacceptable personal behaviors. Managers are responsible for setting priorities and motivating their team members. They are also responsible for ensuring the care of their team members as well as meeting GitLab's goals. These two things can be done simultaneously. As managers it is considered one of your primary responsibilities to understand GitLab's Code of Business Conduct and Ethics, Values and People Group policies and processes. People managers are responsible for upholding compliance on the their teams and considering the best interest of the business. If a manager is made aware of a situation that potentially runs afoul of the Code of Conduct, Values and People Group processes or policy they should immediately reach out to the team member relations specialist. If uncertain about a specific policy or procedure, the manager should reach out to a leader, their aligned PBP or the Team member relation specialist for further clarification. When in doubt, it is always best to ask.
A critical responsibility within the role of a GitLab leader is to spend the time required to truly understand the causes of the performance issue and how to address them properly. GitLab managers will determine if the performance concerns are skill-based or behavior (will)-based to determine next steps. Below are the definitions of both skill- and will-based performance concerns.
Sometimes skill-based issues appear as a will-based or behavior concern. However, after delving into the cause for the behavior, the leader may find a skill-based gap causing the disruptive behavior. The team member may be embarrassed or concerned about their ineffectiveness or ability to perform their role and may react in a way that is inappropriate.
The following are a few recommendations for a manager to address skill-based performance issues:
If the team member is still not making progress after the manager has provided additional resources or coaching please review the underperformance page in the handbook for next steps.
Will-based issues are described as undesirable behavior that impedes the success of the Team Member, the Team, and/or GitLab as a whole. The leader may hear about the behaviors from others or experience the undesirable behavior directly. It is important that the manager address the concerns right away. While "will" issues can be disruptive, there are different levels of severity which must be considered when determining next steps. The tiers below are examples and are not exhaustive, and should be used for comparision purposes to determine the impact to GitLab.
Tier 2 - Misconduct resulting in limited material risk to GitLab
For Tier 2 level concerns, the Manager should reach out and discuss with the team member relations specialist immediately.
Tier 1 - Gross misconduct or a violation with serious implications to GitLab.
Since situations differ, managers should immediately reach out to a team member relations specialist for guidance before taking any action. If unable to contact the team member relations specialist directly, please follow the escalation path listed in the handbook
Please review the underperformance page in the handbook for further information regarding managing team member performance.