Ask a question Share knowledge Edit the page

Automation of the onboarding process

The idea is to drive the progress of onboarding through a web service or task tracker, which is convenient because:

  • The onboarding process becomes as transparent as possible

  • The onboarding business process itself is described in the form of task tracker settings and cannot be broken.

  • Onboarding is carried out in the ecosystem familiar to employees

  • For each task, there is a clear definition of done.

Automation is worth thinking about when there are a lot of newcomers expected (from 5-10), and it is inconvenient for everyone to copy checklists and track progress manually.

What problems automation solves

As with onboarding in general
  • Unit managers:

    • New employees are long coming to the “production capacity”

    • Onboarding new employees takes a lot of energy

    • Separation of units

  • The knowledge manager:

    • We need to develop a culture of knowledge sharing.

    • We need to correct errors in the knowledge base.

== Onboarding tools and examples of their implementation:

An important criterion for the success of onboarding is *full-time*Depending on your business, you can be normal for both onboarding in six months and onboarding for two days: for more complex, research and under-studied professions and positions, it will be longer, for linear low-skilled ones - it should be much smaller.

To determine the "full power" can, as a rule, the head empirically, and he can formulate formal criteria (for example: the employee independently solves a class of problems, or some frequent task begins to take less than N time, or some formal indicator reaches a certain value).

Launch of the pilot project

Svetlana Novikova tells The Know All Channel I’m going to start this approach with examples and a screenshot.

For the convenience of employees, a chatbot is often created. didSlack service. built-in To create these bots on the knee without programming.

Automation is expensive. I want more examples of fast automation that can work immediately.

Scaling success

Scaling considerations

In the process of onboarding development, it can combine several approaches.

In the report Welcome to the board: Bringing new developers to the team (article) a comprehensive onboarding system is described, including: onboarding mentoring, office tour, automation and tracking of the onboarding process, rules for the preparation of Quick Start documents, practical tasks, testing of onboarders and ideas for design exercises.

It is also worth paying attention to the report of Alexander Afyonov "Turning Everyone Up: Onboarding New Employees"He has changed several leadership positions at Lamoda and has seen onboarding practices scale and change in the company, and he believes the framework has developed and is sharing it in the report.

  • Buddy is inside the team, who can be asked questions, meet regularly and share knowledge (this time is taken into account in sprint planning and encouraged at the performance review);

  • Immersion in the business of the company, in the tasks and problems that will have to be automated: induction lecture for several hours about the work of each department, about solving business problems, about successes and failures;

  • IT-onboarding: a story about development processes, infrastructure, who to go with, the history of technical solutions;

  • IT Gathering: Gathering IT once a quarter, where we go and where we come, what’s new, what’s up, and talking to newcomers as equals.

  • Excursion to the warehouse, a story about all production processes, where beginners see that they will automate (optionally: excursion to the photo studio, creating content for the site and the opportunity to be a courier-driver, deliver orders, wait for fitting, etc.);

  • Q&A every day, allotted time to ask questions, no substitute for 1-1 meetings.

  • Checklist: Everything a person needs to learn over a period of time, where to access and participate, such as what is shown on the board in Grafana.

Another report from Ruslan Ostropolsky from Sberzdravye about onboarding in a distributed team (dictionary and slides), he talks about three approaches to onboarding (teamlead lecture, mentoring and onboarding from the wiki system) and their pros/cons for different situations.

The speaker shared what is included in their onboarding "Quick Start":

  • Team culture and values, work approaches;

  • administrative and organizational matters;

  • tools and accesses;

  • Projects and teams who are responsible for what;

  • processes.

Interesting ideas:

  • Structure the beginner’s path in the form of a roadmap so that he sees the next steps and sequence of actions.

  • Use nested pages, cross-link between sections, for example, about development and testing, so different departments can support their pieces;

  • Use screenshots and videos;

  • Add contacts to help;

  • Assign each Definition of done item, which is the result of each step or how to verify its implementation.

Creative Commons License | by Igor Tsupko, Lana Novikova, Rodion Nagornov & community