Ask a question Share knowledge Edit the page

Mentoring

Each newcomer is assigned a mentor who helps the beginner to adapt.

And you also have to notice that there are different terms, like mentor, mentor, coach, tutor, and there’s a difference between them, but often it’s not that important.

Starting a mentoring company is more than having one person to help the newcomers, and you need mentors to come from somewhere and be effective.

What problems does mentoring solve?

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).

Where to start implementing mentoring

  • People should become mentors voluntarily.

  • You can’t mentor toxic people.

  • To assess the mentoring process, it is necessary to take into account both the employee’s opinion about the mentor and the opinion of the mentor about the employee.

  • It is useful that the company maintains the status of the mentor’s position: wrote about them, reflected on websites, reports, corporate radio, etc.

  • It may also make sense to select the people the mentors will work with and to set clear requirements for this privilege.

In the report Adaptation checklist as a soft introduction tool They talk about how to help mentors, including through checklists.

In the article Why it is better to be a mentor rather than a student It is about the role of the mentor as such, it can help explain to future mentors what they will have.

There are whole organizations that teach mentoring: http://mymentoring.ru/

In what situations should you bother with mentors and in what situations should you not? Mentoring looks like an expensive tool.
What resources do you need to start and maintain mentoring? There are sort of different approaches: some people schedule mentoring meetings every 3 months, some people schedule mentoring meetings several times a week. What are the pitfalls of each approach, and where are the limits of applicability of these approaches?

Warning: How do you sell the idea of mentoring to company management? to divisional managers? to employees?

Launch of the pilot project

You can start with 1 mentor who will train 1-3 beginners as an MVP.

If there are no skills inside, you can train teachers. Yandex WorkshopGoogle also offers a range of paid courses and trainings for similar queries.

In the article Being a mentor It is possible to make mistakes of the beginners.

Warning: How do you select mentors? How many? How do you start? How do you train mentors? What goals do you set for mentors?

How do you get the impact of a pilot and see if you’ve achieved your goals? And most importantly, how do you know that the achievement is a result of the pilot, not a coincidence? Many people who talk about mentoring are just lucky. And their recipes are not reproducible.
How can you present the results of a company’s pilot project to inspire it to achieve new achievements?

Scaling success

Mentors can be coached and trained, combined in guilds, given achivki.

In the report How to Involve All IT Employees in Training Newcomers and Each Other It also covers financial, organizational and motivational issues with specific figures and examples, and it covers the experience of about 5 years of trying to build a holistic system.

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.

What could go wrong

  • Mentoring can fall into hazing

  • There may be a strong separation of practices in the company from those in the industry.

  • Toxic mentors can happen and you have to somehow restart everything from scratch.

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