The new developer Onboarding Checklist

Ensure a smooth and efficient start of your new team member so he/she feels comfortable and can contribute to your teams’ results as early as possible. 

4 weeks before day one

Plan for a place within your office and verify that the basics are there (desk, chair, power supply, network…)
Order required equipment:
– notebook + docking station
– keyboard & mouse
– LCD monitor
Depending on your company: order ID card(s) and organize whatever entries in your company systems may be required (company ID and directory, email, etc.)
Block time in your calendar for day one. You should have enough time to look after things, introduce the new team member and go through the onboarding plan together.
Block another hour 3 days after day one.

1 week before day one

Make sure ID card and equipment has arrived and is complete.
Depending on your company: have notebook set up with your standard enterprise applications
Prepare the onboarding plan – what will your new team member need to know about your company (you can find a template here: [*]). Make sure to review that plan with the team.
Sit with the team and plan the initial assignments during the first 2..3 weeks. Make sure to leave enough room for startup and learning.

DAY ONE

Take some time to chat and introduce the new one to the team
Explain your companies’ basics – where is the coffee machine, what are the usual office hours (if any), how to you handle work from home, overtime, holidays, business travel etc.
Explain your work context – what is your groups position within the company, who are your customers, what are your interfaces. You have covered some of that during your hiring interview (see [*]) already.
Give a broad overview of the new ones’ role. Maybe leave the details for later. Go through the onboarding plan together. Hand over that plan – your new team member will own it from now on.
Note that onboarding is not done after day one – It is a process that takes much longer

3 days after day one

Now that the dust has settled take some time to discuss what has been happening so far. Answer questions. Are there any issues to solve? How does the new position feel like? Talk about the role and why it is important. What the major success factors? Why does your group exist? What is the new one’s contribution to that?
Fix a date for the next follow-up meeting 3…4 weeks later

3…4 weeks after day one

Collect feedback. What is good? Any help needed? How’s the team? How’s the work context in your place compared to the new one’s past experience? This is also a learning opportunity for yourself.
While you sit together write down 2…4 high level goals and/or desired outcomes. Focus on goals and outcomes, not on tasks. E.g. “ensure that the developed services are highly available” is something concrete and tangible, it could even be measured. You’re not doing this to control and measure but to ensure a good mutual understanding, and to get priorities clear.
Explain your approach for ongoing communication and follow-up on this exercise. Fix a meeting for 3…6 months in the future where you will review results, give credits for achievements, talk about experiences and expections, improvement potentials or whatever needs to be adressed outside of the day-to-day work context. You can find a template in the download section.


Check out these related articles:


 

How to set up a high-performance team (part3 – onboarding)

So let’s assume all is arranged and your new team member will start within the next few days or weeks. Time to think ahead about onboarding.

Why is well organized onboarding so important?

Let’s just wait and see what needs to be done whenever that person shows up. It’s amazing how many new employees need to wait for days and weeks for equipment and access rights until they can finally really start. What a waste of time, what a frustrating experience – something that just does not happen in a well managed team. So you’ll think in advance about your new team members equipment. You have a notebook already in the shelf or it’s agreed that he/she brings his own along? Good. Otherwise: get one ahead of time, you want to have it ready on day 1 and delivery may take some time. The team is informed and ready to welcome the additional help ? Of course you have thought about a desk and other basic stuff that may be relevant – like entries in your company directory, access rights to your systems, ID cards, and so on? You need to organize all that anyway, do it up front and provide a smooth and positive start.

Planning for knowledge ramp-up

In addition to these practical things you need to organize the knowledge ramp-up. Sit with your team and create a list of topics that the new team member will need to know or learn. Prioritize it. For each topic note the source of information. It may be yourself, one of the team members, or a link to a team Wiki page – or set up an ‘onboarding’ Wiki page for later re-use. Make sure that the team has thought about some first entry-level task that can be tackled along or after the initial topics to start team integration and interaction. Think back about your first day in a new office, a new team – it feels good if you feel welcomed, people have been waiting for you and you most likely made the right choice when choosing this position.

You may want to use this Onboarding checklist  to plan for this.


Check out these related articles: