Yet the solution to this is pretty simple - in my eyes anyhow. It just needs a bit of planning ahead, not much but just an idea of how you are going to get people bedded in to your team. Here is a rough guide for an induction that works:
- Get all the equipment they are going to be using ordered (fortunately when I was hiring, this was handled by my HR colleague) - it's got to arrive before and be ready for them to use on the day they get there. Keep pestering until you are happy it's going to on there desk when it arrives.
- Get a desk within the team area - ideally in the middle of where the team sits - if there is no room, make room - move yourselve if necessary.
- On the day of arrival get there before they do - i.e. if they are going to get there for 8:30 - you've got to be in for 8:15.
- Once you've been notified they are here - go get them straight away - they are your priority for the day.
- Buy them a coffee - have an informal chat about the weekend and travel in. I usually talk about working hours at this point - as people want to know this.
- We had a company induction the morning they would arrive - if possible get this out of the way as soon as possible.
- Get them to be dropped off in your team area after the induction.
- Go out for lunch as a team (you should be doing this every day so adding another person should be easy!).
- Once back from lunch - let them setup there kit which will be nicely boxed on there desk. Let them install whatever they need to get there job done (hopefully the PC is already imaged with key software). If there are problems then take them the people who can sort them out (i.e. infrastructure/desktop support people) free introduction done ;).
- Give them access to what they need to do there job (i.e. Git, TeamCity, Octopus).
- Get them working on production code within the first 2 days of joining - I promote pairing so this was easy for them to drop in with a pair.
- Get them to release to production within the first week of being at the company - if you can't release this often then start working towards it.
- Walk them through the architecture of the solution they are working on.
- Walk them through the full architecture of the eco-system they are working with.
- Get them to setup a build pipeline within the first month of being at the company.
- Setup your 121's with them.
- Show them around the department - hopefully this should only take a couple of informal introductions - nothing to over the top required.
"in the first few milliseconds of our perceiving something we not only unconsciously comprehend what it is, but decide whether we like it or not."