liveBook · Manning

Employee turnover

As explained in Lead Developer Career Guide

The rate or occurrence of employees leaving an organization or team and being replaced.

Employee turnover is employees leaving an organization or team. When people feel unsupported and become disengaged, they may quit; losing them can also mean losing valuable team knowledge. section 1.2.1

Turnover can create practical costs for a software team:

  • Hiring and onboarding take time: replacing a developer may take months, and bringing them up to speed takes longer. section 1.2.1
  • Without knowledge transfer, the organization may face even higher costs. Trust, listening to employees, and providing onboarding documentation can help support retention. section 1.2.1

A warning sign

In one workplace, every developer on a migration project left except one, and the remaining developer was denied help. A mentor described high turnover as a sign of possible mismanagement. section 9.1.2

How Lead Developer Career Guide covers it

How deep it goes
Describes turnover costs through hiring, onboarding, and knowledge loss, and illustrates its workplace consequences.
Examples
Uses technology-industry turnover figures and a migration project where all but one developer left.
What you can do after
Evaluate turnover as a possible management warning sign and understand its costs to hiring, onboarding, and retained knowledge.
How it connects
Links turnover with trust, employee disengagement, onboarding, knowledge transfer, and mentoring.

Also explained in

Compare how 3 books explain employee turnover →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Lead Developer Career Guide. The section links point to the parts of the book it draws on.