“Coming together is the beginning. Keeping together is progress. Working together is success.” Henry Ford.
In the previous post of this series on Incident Management — How to hire people with a knack for it — I shared my views on the hiring of engineers who will be handling production systems. This post is going to be on the onboarding — as next logical step after hiring. But, in my opinion, there is no much difference in onboarding of employees who will be managing production incidents and those who won’t.
The only difference is that the quality of the onboarding process directly correlates with the quality of the service and attention the production of your company will get. So this post will describe an onboarding experience that would be good for any employee, but would be critical for people managing production environment.
Onboarding is my favourite part of work, as it’s usually full of surprises, good mood and super short feedback loops — what more could you possibly dream of? :)
Of course, it wasn’t always like that. I personally went through several different kinds of onboarding: one time it was a whole month of full day training and tests, another time it was “mmm, sorry we don’t have enough tables, so take mine for now. No, I don’t know what you should be doing today”. Each type had its own charm, but not all of them were actually achieving the goals of onboarding.

Onboarding goals

There are several sides involved in onboarding — a new employee, a team and a manager, and each side has its own goals.
For a new employee the goals could be:
For a team the goals of onboarding could be:
For a manager:
If we take a closer look at the goals listed above, we can split them into a few categories:
Every category is important in its own way, and it’s important to find the balance between them. For example, you shouldn’t make your onboarding process extremely inspirational, while forgetting about sharing information. I prepared some tips and tricks for each category that you can use to build the onboarding process for your team.

Tips and tricks for achieving the onboarding goals

1. Sharing information:
2. Building communication:
3. Sharing culture:
4. Inspirational:
A few more generic recommendations I’d like to add to close the subject:

How to measure the success of onboarding?

Most likely you’ll see it without any extra effort — by the time that it’ll take a new employee to go from day 0 to their first oncall shift, or by the good feedback a team will be giving the new employee.
However, when I was working on onboarding for the first time, I didn’t believe in getting feedback without asking for it and I really wanted to measure everything, so my way of measuring success was to send 2 surveys — one right after finishing the onboarding and another one in 3 months.
The questions in both surveys were almost identical — what did you like/ didn’t like in the onboarding process; what is the most interesting/important subject for you; how useful was it for your day-to-day work.
My goal was to check if the new employees think that the onboarding was useful even after getting real working experience in the company. Surprisingly — it was:) What’s more, our new team members started getting their first oncall shifts after 3 months, instead of the 9 months they were getting before.
I didn’t mention in this part of the blog series anything about covering specific subjects for working with production incidents — in my opinion incident management has to be a separate training build on top of a strong foundation, which the onboarding has to prepare.
I think it’s counter-productive to start introducing a system to a person from a failure perspective. It’s better to learn the “normal” way of operating and only start letting the new employee ready to fight crises after a few more weeks.
How to do it efficiently?
How not to scare your new team members?
How to make sure you covered everything?
Read the answers in my next post. To be continued.