Skip to content
GitLab
Next
Closed
Issue created by Ashton Herrmann@aherrmann

Overhaul onboarding for Ta-NEW-kis

This issue will track our work towards improving the onboarding process for all new GitLabbers (i.e., "Ta-NEW-kis") and will develop as we flesh out what that means.

The plan is to meet weekly for about an hour, typically on Wednesdays, immediately after the Team Call. The meeting notes and agenda can be found here: https://docs.google.com/document/d/1NDt0jQV4tc7nd_ncDdT929MomFMMd3m9xHKZEle4C3Q/edit?usp=sharing

Our initial thought is to add an orientation component to the onboarding process.

  1. Onboarding vs Orientation - what does orientation look like at GitLab?
  2. Logistics - getting started, lots to install, is it necessary?
  3. Separate out department/team onboardings
  4. Issue with Day 4 video (sound going out)
  5. Create a project plan
  6. Do not create access until the person starts at GitLab?

Ta-NEW-ki Suggestions

  • How are we defining orientation versus onboarding? Is it the same for all employees / all roles?
  • Assumption that people are familiar with Macs.
  • Ensure new hire has right equipment. Check with manager & new hire prior to start date.
  • Onboarding tasks take more time than allotted/suggested
  • Question status quo - just because "we have always done it this way" - we need to ask if it still makes sense as we grow forward.

Specific Days:

  • Day 0 - Remove the "before starting at gitlab" info from the checklist if we do not want people doing anything prior to day 1.

  • Day 3 - Not clear if implicit bias training is required or optional. It looks very long. What are we trying to accomplish with this and is this the best, most efficient way?

  • Day 4 - The GitLab training videos by Job: the first video is 35 minutes long. At 30 minutes, the sound goes out right when he begins to explain the importance of branches. The sound is out for 1.5 minutes. There are comments from 2-3 years ago pointing this out & it still has not been fixed.

  • Other thoughts

  • The tools we use/recommend

  • Internet browser: Google Chrome

  • Google docs instead of Microsoft Office

  • Google drive * Instruction on how to use, organize, etc. would be helpful

  • 1Password - sounds like a lot of people struggle setting this up

  • Different projects: www-gitlab-com, gitlab-runner, etc.

  • Learning how to use and interact with Git is tough

  • Office hours - or some topics, consider 25 minute “office hours” 1-2 times a week to accommodate time zones.

  • SSH key and setting up local access

  • Adding photos to the team page

  • Summit information and procedures

  • Using Git sessions with a "subject matter expert" and anyone who wants to join, especially new hires; sharing screens and actually getting hands-on with someone guiding you

  • Buddy - a "safe space" for questions that feel dumb * No matter how much we tell people, the reality is that new employees do not want to bug or look bad to their manager or immediate team mates, so having someone you can go to outside of the department is helpful. * It is a lot to ask of a buddy to help with technical setup, training, etc. * Instead of a 1:1 buddy, does it make sense for 1 buddy to have 2-3 new hires and they meet on group calls altogether. They form a little cohort, and the new hires are meeting other new hires outside the dept, and the buddy is helping 3-4 people instead of 1, which may be a better use of their time.

Onboarding vs Orientation discussion

  • Abby's suggestion: the standard induction for UK businesses
  • Scott: previous experience
  • History of the company
  • Where are we now
  • Where are we going
  • Understanding company benefits
  • How to use Trinet, issues, etc.
  • Live orientation sessions would make for a good experience
  • Anastasia: don't lump all of this work into a single issue

Action Items

  • Everyone: Update the onboarding issue template: what needs to be added, removed, rearranged, and/or re-prioritized
  • Update the "Before Starting at GitLab" section of the onboarding issue template to clarify who's responsible for which action item (e.g., "1password" and "BambooHR")
  • Look at the welcome letter we have now and consider revising, enhancing, and/or expanding it - https://gitlab.com/gitlab-com/people-ops/employment/merge_requests/70/diffs
  • Figure out what orientation tasks can be delayed until a single, monthly (or otherwise regular) meeting
  • Schedule a weekly meeting that works for this group
  • Look at onboarding tools and/or LMSes (e.g., Mindtickle, gamification)
  • Check into how other, similar organizations manage onboarding (InVision App, Automattic)
  • Update the Spending Company Money page to include language about procuring a company-owned laptop
  • Clear up the confusing descriptions in our GitLab instances (www-gitlab-com, Enterprise Edition, etc.)
Edited by Ashton Herrmann