GitLab Team Member Engagement Survey November 2020
Plan and DRIs
Plan for the 2020 annual team member Engagement Survey (there are a few items that are still in draft and will be triaged shortly).
|Proposed Launch Date||November 16th, 2020|
|Participants cut off date||31st October 2020- The survey will be sent to team members who joined prior to 1st November 2020|
|Close Date||December 16th, 2020 (intentionally open for a full 4 weeks to allow everyone to take the time to complete it seeing that November is a busy month at GitLab)|
|Set up and Administration||People Specialist Team|
|Creation of a Reporting Slide Template||People Specialist Team (this will ensure consistency and self-enablement, should non e-team members want to report directly on results)|
|Closing and Data Collection||People Specialist Team|
|Benchmark||Same as 2019: New Tech, companies sized 1000+. We are focusing on reviewing insights and trend-lines, however a few small changes were made as per the issue thread below|
|Communication of overall results to Company||@jkalimon, @brufener and @hwangui (Engagement Survey project owner)|
|Communication of results to Functions||PBP assigned by Dept/Division|
|Action planning of results Company-wide||@jkalimon @brufener and @hwangui (Engagement Survey project owner) and @cteskey (Senior Director, People Success) to propose 1-3 priorities for exec group to focus on for the next 3-6 months.|
|Action planning of results by Function||PBP assigned to function - Proposal is that PBP review the results with the Senior Leader first and then open an issue with the results for view by the team and GitLab.|
|Metrics||Propose adding an OKR to Functions again based on 1-3 action items identified from results : PBP to work with leaders to identify actions, building the plan and timeline.|
Announcement timeline in Slack (
#company-fyi and Email(?))
|November 16th||Announce in
|November 30th||Reminder in
|December 7th||Reminder in
|December 15th||Last reminder in
|December 21st||High level summary added to issue for all team members to view|
|January 8th||Custom results provided to E Group leaders|
|January 11-15th||Training video for manager released and standard reports from CultureAmp sent to managers with 5+more responding team members|
|January 15th- 31st||Functional group action plan for focus areas|
|February 1st||Functional action plans from survey added to OKRs for Q1 2021 and added to the Action planning in Culture Amp|
Staff meetings: PBPs to communicate the survey in appropriate Departmental team meetings.
46 Multiple choice questions, including 3 Free Text Questions. Multiple choice questions scale from Strongly Disagree, Disagree, Neither Agree nor Disagree, Agree, Strongly Agree.
Multiple choice questions are broken into sections which are tracked as Factors (these are still in draft and will be confirmed in this issue body shortly):
Section 1: Overall
- I would recommend GitLab as a great place to work.
- GitLab motivates me to go beyond what I would in a similar role elsewhere.
- I am proud to work for GitLab.
- I rarely think about looking for a job at another company.
- I see myself still working at GitLab in two years' time.
Section 2: Company Confidence
- GitLab is in a position to really succeed over the next three years.
- GitLab’s products and services are as good as, or better than, our main competitors.
- GitLab effectively directs resources (funding, people and effort) towards company goals.
- GitLab is aligned and focused on delivering positive business outcomes for our customers.
- GitLab has high standards for business ethics.
Section 3: Our Leaders
- I have confidence in the leaders (Senior Leaders and Executives) at GitLab.
- The leaders at GitLab keep team members informed about what is happening.
- The leaders at GitLab demonstrate that people are important to the company's success.
- The leaders at GitLab have communicated a vision that motivates me.
- The leaders at GitLab role model our company values.
Section 4: Your Manager
- My manager genuinely cares about me.
- My manager communicates important things with me in a timely manner.
- My manager is doing a good job as a people manager.
- My manager role models our company values.
- I receive useful feedback on how well I am performing.
Section 5: Team Work
- Most people at GitLab make a good effort to collaborate with each other.
- At GitLab there is open and honest two-way communication.
- Workloads are divided fairly among people where I work.
- We hold ourselves and our team members accountable for results.
- I feel I am part of a team.
Section 6: Your Role
- I know what is expected of me to be successful in my role.
- I have access to the things I need to do my work effectively.
- I have enough autonomy to perform my work effectively.
- I know how my work contributes to the goals of GitLab.
- I believe my total compensation (salary, benefits, equity, perks, etc.) is fair, relative to similar roles in my location.
Section 7: The Culture
- GitLab has an inclusive environment that encourages everyone to contribute.
- People of different cultures and backgrounds are respected and valued at GitLab.
- I feel my opinion counts at GitLab.
- I feel supported when I need to take time off or make use of flexible working arrangements.
- I feel safe to speak my mind without fear of negative consequences
- GitLab's commitment to social responsibility (e.g., community support, sustainability, etc.) is genuine.
Section 8: Growth & Development
- I believe there are good career opportunities for me at GitLab.
- My manager (or someone in management) has encouraged me with my own development.
- I am given opportunities to develop skills relevant to my interests.
- GitLab is a great company for me to make a contribution to my development.
- I receive appropriate recognition for good work at GitLab.
- I have access to the Learning & Development I need to do my job well.
- The Learning & Development programs provided by GitLab help grow my career
- If there is an area I want to improve upon, I know GitLab will provide resources or help me find them
Section 9: Well-being Covid 19
- How would you rate the Internal Communications at GitLab overall during the COVID-19 pandemic?
- The E-Group at GitLab has remained transparent and is providing a sense of stability during the COVID-19 pandemic.
- I feel I am able to take care of family and friends first.
- I feel connected to my team during the COVID-19 Pandemic.
Section 10: Action
- I believe action will take place as a result of this survey.
- I have been provided an opportunity to see and discuss prior engagement survey results.
- I have seen positive changes since the previous engagement survey.
Section 11: Comments (free text questions)
- What are some of the things we are doing great here?
- What are some things we are not doing so great here?
- What other comments do you have?
Recommendation is to use the same questions as last year so we have year over year comparison. However, we can always iterate and change this up going forward- open to your thoughts and ideas regarding the survey and questions.
@gl-people-exp(decision to be made shortly) will be responsible for survey administration
- Confirm survey questions, survey demographics and reporting functionality
- @jkalimon or @hwangui or @brufener to communicate the engagement survey messaging in Slack and Company calls
- @jkalimon or @hwangui or @brufener to update the handbook and add Engagement survey section - why we do this survey, past results, dates, actions, instructions and 2019 survey results
- @jkalimon to Coordinate PBPs on message and delivering of results to functional leaders
- Functional Group Action Plan - aligned PBP and functional leadership
Feedback from Team Members for the next survey
- Reword the question to remove people- GitLab effectively directs resources (funding, people, effort) toward company goals- https://gitlab.com/gitlab-com/people-group/General/-/issues/931#note_462055332
- Add further explanation on what Confidentiality means. The explanation on the CA link is not as clear. This can be assumed to mean that it is available to GitLab but should be treated in a confidential way-https://gitlab.slack.com/archives/C0259241C/p1607435804396200?thread_ts=1607347054.341300&cid=C0259241C. Thank you @mlunoe for sharing your feedback.
- Beverley-https://gitlab.com/gitlab-com/people-group/General/-/issues/931#note_466411263 have a separate update only issue for next year