Earlier quoted context omitted.
Agreed. The over-engineered onboarding process can become frustrating if it starts to diverge too much from real day-to-day life at the company. It can also be disappointing to go through a multi-week onboarding full of outings and lunches and fun activities, only to discover that the real job is nothing like the onboarding. Then you have to learn how to actually do the job after the onboarding. IMO, the best onboard…
From my experience onboarding means showing you where the bathroom is, giving you credentials for your new emial account, pointing you to a company wiki and introducing you to your new team and then you are at the mercy of your team to "get you up to speed". Stories of some fun activities sound like some sort of novelty to me.
Optimize Onboarding
51–60 of 66 posts
Re: Optimize Onboarding
#52>It takes roughly 2 weeks to form a habit; it takes roughly two weeks to get comfortable in a new environment. A common mistake is to treat a new report’s first couple weeks like college orientation - social, light hearted, get-to-know-you stuff. If your report spends the first two weeks reading C# documentation and having lunch out on the town with the team, guess what, they’ve just normalized that behavior as what…
Re: Optimize Onboarding
#53Earlier quoted context omitted.
It's important to teach juniors the importance of avoiding burnout. As a manager, it's not very difficult to gauge burnout by keeping an eye on time spent in the company Slack, when e-mails are spent, timestamps on commit messages, and so on. More importantly, building a genuine relationship with the employee is important for keeping the conversations open. Having someone try to stay all night to get work done on day…
I'm interested in why you stuck "avoid on-call" in there. I'm about to start my first on-call rotation next month
Re: Optimize Onboarding
#54Which goes a little against the idea of slowly introducing trust, but these were sysadmin/devops jobs, not coding. YMMV.
EDIT: By "best" I mean "most productive, most enjoyable, most memorable". All accusations of selective memory or bias on my part are of course accepted.
Re: Optimize Onboarding
#55>It takes roughly 2 weeks to form a habit; it takes roughly two weeks to get comfortable in a new environment. A common mistake is to treat a new report’s first couple weeks like college orientation - social, light hearted, get-to-know-you stuff. If your report spends the first two weeks reading C# documentation and having lunch out on the town with the team, guess what, they’ve just normalized that behavior as what…
This could be a whole forum. In the most important sense (the moral sense), we are not. It's a bad road to go down, thinking of other people this way.
OTOH, we are very much like dogs... a lot moreso than we usually think. It's very useful to remember this and "train" yourself. We tend to assume that we are rationally driven, and sometimes we are. More often, we (me, certainly) are impulse driven and rationalize ex post. The neurochemistry of learning, habit forming and such is something we're better working with rather than against.
Re: onboarding...
I agree with the author that this is important, and usually badly done. I disagree on the particulars.
First, HR and boilerplate management stuff tends to do a pretty bad job onboarding.
"Endless HR videos, slow security processes, a mountain of fragile technology setup"
This stuff sets the tone for culture, and it should be a lot better. Considering how many people these days are explicitly responsible for this stuff in a modern company, it should not suck like this.
I disagree about the "social, light hearted, get-to-know-you stuff." We need more, not less of this. People need to know who they're working with and have as little barrier to asking a wide range of people a wide range of questions.
I do agree that the initial period needs to be taken advantage of. One reason is the "dog training" aspect. Habit forming and such. Good advice in general, not just for work. Build your habits intentionally, especially if you (like me) struggle with bad habits. More specifically for work, use this very limited grace period to ask dumb questions, sit in on stuff and such.
If you (as a manager) put newbies onto boilerplate stuff for 3 weeks, you are wasting the opportunity (of the newbie) to encounter real problems while that grace period is in effect. It's a lot easier to ask "where do I see bugs" on day 8 than day 80. These inevitably come up once real work starts.
Re: Optimize Onboarding
#56Earlier quoted context omitted.
From my experience onboarding means showing you where the bathroom is, giving you credentials for your new emial account, pointing you to a company wiki and introducing you to your new team and then you are at the mercy of your team to "get you up to speed". Stories of some fun activities sound like some sort of novelty to me.
I've switched employer and been through the "fun activities" recently. All remote though, because COVID. Two weeks of online lectures and "icebreaker" activities. It was a weird experience, and I think the actual, useful information could have been condensed in a single day, instead of two weeks. The actual, useful onboarding, was mostly me asking my colleagues where to find the things I needed to find. I can program…
I run a fully remote team and am always looking for ways to make a new member feel comfortable, and the existing team comfortable with the new person... or at least less-awkward.
Also, anything to specifically avoid?
Re: Optimize Onboarding
#57>It takes roughly 2 weeks to form a habit; it takes roughly two weeks to get comfortable in a new environment. A common mistake is to treat a new report’s first couple weeks like college orientation - social, light hearted, get-to-know-you stuff. If your report spends the first two weeks reading C# documentation and having lunch out on the town with the team, guess what, they’ve just normalized that behavior as what…
But at least: Be the Person Your Dog Thinks You Are.
Re: Optimize Onboarding
#58>It takes roughly 2 weeks to form a habit; it takes roughly two weeks to get comfortable in a new environment. A common mistake is to treat a new report’s first couple weeks like college orientation - social, light hearted, get-to-know-you stuff. If your report spends the first two weeks reading C# documentation and having lunch out on the town with the team, guess what, they’ve just normalized that behavior as what…
Quite so. In addition, as a manager of a new employee I make an absolute point of being a "helicopter mom" from the moment they hit the area until about week 2 or 3. Payment at the hotel will foul up. I want overcharges and idiocies on my card and not on my employee's. Access cards and tokens will foul up. I need to meet the new employee the first day on the morning and probably for lunch. Network account provisionin…
Re: Optimize Onboarding
#59Re: Optimize Onboarding
#60Personal anecdote: Started in a developer position a couple years ago to work on an internal corporate app on an isolated network. Week 1: Get to the desk; meet my neighbors; submit request for necessary network account; and start on mandatory security training for the systems. Week 2: Finish the mandatory training; ping the network owners a few times about the account request; start reading up on unfamiliar parts of…
Hey at least the company knew that they had hired you. I had that once, the joy of contracting agencies I guess. It was a 6 month contract and at the end of it they still had not gotten me badge access to the area I worked in.