New guy starts tomorrow
-
Go out to lunch!
-
Make sure you start his search for replacement electrical smoke early in the day
-
Give them tasks little by little and see what that can handle and what that struggle with. That's how I usually do my new employees
-
Walk them around the office. Introduce them to the staff this is helpful.
Don't just dump and run,... show them how you do things for the office, but also explain that others may do the same task differently...
-
Be there to answer any first day questions (where you should park, what time the person should expect to take lunch and can they at the same time as you, how they clock in and out for the day, etc.).
If they are extremely green to IT, what may really help is to show them a process (i.e. the workstation imaging process for example) and let them take notes and push the buttons. Answer questions along the way. Then have the person try it on their own and come ask you questions.
If you have written instructions for something like this, have the person use your instructions to image a workstation. That will tell you how good your instructions are, and you can have the new person make corrections if there is a step missing, etc.
I like the idea of taking them to lunch (maybe with you and your boss if possible) as a welcoming, and I think having them meet everyone in the office is a good way to get them acquainted with culture.
-
One thing I like to do is have the new person setup their computer from scratch (no imaging software - only a Windows install disk / USB and either the proper drivers or access to another pc to use to download drivers).
Then have the person install all the programs a regular uses followed by the tools you use (i.e. RSAT, Exchange Management Console, Veeam Backup and Recovery Console, etc.).
-
Start with the tour. See what he has questions on, or what causes blank stares. See what he's interested in. See if you can find a project that works with his interests.
-
@NetworkNerd As much as I would do this, it's not something I can make him do immediately. He has experience doing this anyways. And we have a rather sound imaging solution.
So it would just be a time sink more than anything.
-
Make sure to find out what he does that is IT in his off time. This will be a true indication of how much effort and also what he really knows and is going to add to your team (better asked at interview time but you didn't get a choice in that I am sure). This will also help you really know how much in depth training you need to do with him.
-
@Minion-Queen said:
Make sure to find out what he does that is IT in his off time. This will be a true indication of how much effort and also what he really knows and is going to add to your team (better asked at interview time but you didn't get a choice in that I am sure). This will also help you really know how much in depth training you need to do with him.
Also... this post was made yesterday... Its now time for us to meet your fellow minion!
-
@dafyre He'll be with HR first, going over our policies, signing stuff etc, and then likely be back here afterwards.
-
-
Just chill. The first few weeks are always a bit uncomfortable, in my experience, but they'll soon settle in. Just got to get through the first couple of weeks without them quitting, destroying something, or punching somebody, and then it'll be plain sailing.
-
Make the job sound much easier than it is, even if it's an easy job, in order to destroy his confidence. I'm serious. Young people in general do have a lot of unwarranted confidence about their abilities, but IT people especially need to understand they don't know everything and never will. I'm not saying be mean or condescending, but what I've done for years now is talk about the minor details of what I'm fixing and how it works, things they often don't know. Most don't say anything, but a few times a few have said they were over their heads, and one guy even quit, but the work they were doing wasn't really that complex.
