It is the lifelong process of managing learning, work, leisure and transitions in order to move toward a personally determined and evolving preferred future.
70-20-10 Rule for Development
Additional Questions to Think About
During our Career Development workshops at Contribute, May 2019 we took team members through tips to creating a clear growth (aka development) plan. Below are the resources from that session:
Career development is a key factor in team member engagement and role satisfaction. As part of the FY 20 GitLab annual engagement survey results it was clear that team members want to have meaningful conversations with their managers on an annual basis or even more frequently. Starting in FY 21 we will be tracking career development conversations via BambooHR. This process is just an acknowledgement by the team member that they have had a career conversation in FY 21. A manager cannot complete this process for team members, the team member is responsible for the acknowledgement in BambooHR.
Starting FY 21 (exact date is TBD) team members will receive a notice via BambooHR to acknowledge that a career conversation has occurred. By signing the acknowledgement you are confirming that you have indeed had a career development conversation in FY 21 with your manager. Below are a few things to know about the process:
We have started this process at GitLab by defining Junior, Senior and Staff advancement levels. Career Mapping helps GitLab team-members to understand and develop the skills they need to achieve their goals, giving them clear criteria. Mapping helps managers and leaders internally develop the skills and knowledge they need to achieve future business goals. The key to this is to identify the key skills, knowledge, and abilities needed to master each level. Another essential tool is a career development plan, here are some examples:
Managers should discuss career development at least once a month at the 1:1 and then support their team members with creating a plan to help them achieve their career goals. If you would to know more about this please checkout the career mapping course video
As is highlighted in our Leadership section, GitLab team members should not feel pressure to climb the proverbial ladder. We recognize that not everyone wants to advance or move to a new level, and that is supported. Developing one's skills and promotion at the company are not mutually exclusive.
It is perfectly acceptable to seek out learning and development opportunities — to sharpen one's understanding of a coding language to better understand a function, etc. — yet not strive for promotion beyond your current role. Some team members are happier and more productive without managing a team, for example.
As detailed in GitLab's Definition of Diversity, Inclusion & Belonging , we recognize that unique characteristics and experiences form how we as individuals approach challenges and solve problems. They also shape how we view success in our individual careers and lives. Not everyone views promotion as a measure of success, and team members will not be thought less of or penalized for holding this view.
As part of GitLab's Transparency value, team members are encouraged to be open and honest with their manager. You are encouraged to learn and develop your skills without pressure to in turn seek promotion. If you feel you are not being supported in this way, please visit the Need Help? portion of the People Group Handbook.
Effective from FY21-Q2, on a quarterly basis, each member of the E-Group will have a performance conversation with their direct manager, the CEO, at the beginning of every quarter. These performance conversations will enable the continued performance improvement and personal development for the E-Group member. These quarterly meetings may include their Executive Stable Counterpart and their People Business Partner to provide guidance and feedback as part of this conversation.
Performance will be reviewed in three parts which are not all of equal weighting but together make up 100%:
|Quarter||Values 20%||Results 40%||Professional Development 20%||Engagement 20%|
|Q1 (April)||Values||20% KPI / 10% OKR Achievement / 10% OKR Ambition||Individual Growth Goal||Vol attrition and number of PDPs|
|Q2 (June)||Values||20% KPI / 10% OKR Achievement / 10% OKR Ambition||Individual Growth Goal||360 Results|
|Q3 (October)||Values||20% KPI / 10% OKR Achievement / 10% OKR Ambition||Individual Growth Goal||DIB Score|
|Q4 (January)||Values||20% KPI / 10% OKR Achievement / 10% OKR Ambition||Individual Growth Goal||Engagement Score|
The output from these quarterly meetings will be one of the below performance factors
When conducting compensation reviews for the E-Group, GitLab will review two items: 1) alignment to market rates 2) performance factors from each quarter.