Writing a thread on onboarding here, because I don't want to write it in the other place.

Context:
Good engineer onboarding *is* DEI. Teams that have great onboarding, tend to be more diverse and inclusive. Teams that have poor onboarding, tend to be more homogeneous and less diverse.

That's because poor onboarding makes life harder for junior employees and remote employees. Underrepresented groups benefit disproportionately from remote work options. Junior employees are a more diverse group.

Poor onboarding leads to more "beginner questions" for longer. Underrepresented groups experience higher social threat. So if 3 employees start working at Tech Corp on the same day, and they are:

* A white man
* A white woman
* A Black man

And they all have the same beginner questions 6 months after their start date, then the Black man and white woman are more likely to be perceived as "slow ramp up" people, and face career consequences as a result.

https://xkcd.com/385/

How it Works

xkcd

Imposter syndrome isn't real. Imposter phenomenon is very real.

Imposter phenomenon is the combination of two things:
1) the belief that I know less things than others around me.

2) the belief that if this is found out, that I will experience harm from it.

In short, it's about psychological safety. It's a rational response based on the lived experience of the person feeling it, and their observation of how others are treated, it's not a shortcoming of the person experiencing it.

There are lots of things that we can do to minimize the imposter phenomenon. Better, more consistent, and deterministic ramp up experience, is one of these things. 👍🏿

This doesn't just mean documentation. This also means removing processes that shouldn't exist in the first place.

But in terms of documentation, one thing that really helps, is having a verifiable definition of being ramped up and onboarded.

Welcome Starfleet graduate! You've been assigned to the Transporter team! "Dream to Beam!"

Week 1:
✅ Get desk, comms badge, quarters
✅ Meet your onboarding guide (Scotty)
⬜ Join all team mailing lists
⬜ Take the "Teleportation basics" training

Month 1:
⬜ Complete first pair transport (inanimate objects)
⬜ Complete first solo transport (sentient life forms)
⬜ Join duty rotation (shadow your guide)

Quarter 1:
⬜ Complete first multi-party transport
⬜ Join duty rotation (solo)
⬜ You're onboarded!

@mekkaokereke

heh, kinda happy that the onboarding template looks an awful lot like this.

I cleaned it up for public use. Not sure if it actually is useful, but yeah, making things easier for anyone to onboard is A HUGE WIN.

https://drive.google.com/file/d/1hWEgOYrH07-t_w-hPOYjEp-ooj1mxogv/view?usp=sharing

(Don't make new folk suffer like you did. They don't need to earn anything. You hired them to help free up your work.)

Copy of Onboarding Template.odt

Google Docs
@jrconlin @mekkaokereke a GREAT way to improve on-boarding is to reward new hires for improvements in onboarding docs and processes that they suggest and/or make as part of the team when coming in. No one can possibly have a better idea of where there are gaps or assumptions or places for improvement once they're up to speed and know everything.
@jonathanpeterson @jrconlin @mekkaokereke user profiles on our intranet have badges. During onboarding they taught us about the "Documentation wizard" badge and I managed to receive it during the onboarding week thanks to some fixes I made to onboarding documentation.

@blikkie

In the flip side, I offered comments for ours and was met with "we've been doing it this way for 25 years, it's fine" 😂😒

@jonathanpeterson @jrconlin @mekkaokereke