When someone new joins the team, I try to avoid verbal training
When someone new joins the team, I try to avoid verbal training. I believe processes should be documented. So I link to the relevant doc. If one doesn't exist, we create it together. Outdated? We fix it.
This fosters solid docs, exposes holes, and avoids "tribal knowledge".
Plus, a documented process gives us something tangible to improve.
"Woah, our process for setting up a dev's machine requires 23 manual steps and 7 different access requests? How can we simplify this?"
And why is each step necessary? The doc can explain that too.