Attrition and Who Leaves First
The cost that never reaches the business case, and the specific problem that the people who leave first are the ones you need.
Some people leave over monitoring. The number is usually small and the composition is the problem.
The people decision in “Attrition and Who Leaves First” cannot safely be reduced to a single activity measure. Used for getting teams to meet deadlines, learn more here can provide time and project evidence, but expectations, context, documented outcomes and a fair conversation should remain the basis of any management judgement.
Who leaves
People with options: experienced, in demand, able to find something else quickly.
For an independent reference relevant to “Attrition and Who Leaves First”, consult the CIPD people-practice resources; it provides a useful external check on scope, terminology, governance and the claims made during procurement or review.
People who were already considering it, for whom this is the thing that decides it.
People in roles where monitoring is uncommon elsewhere, who can simply go somewhere it is not.
And the ones who feel it as an accusation, which is frequently the most conscientious.
Who stays
People without options.
People close to retirement.
People who adapt to the measure, which the gaming note covers.
Over time this changes the composition of the workforce in a direction nobody chose, and it is invisible in headcount figures.
The cost arithmetic
Replacing a skilled person costs a substantial multiple of their salary once recruitment, vacancy and ramp-up are counted.
One departure can exceed the annual licence for an entire team.
Which means the business case needs an attrition assumption, and essentially none has one.
Measuring it
Turnover before and after, by team, with the monitored and unmonitored groups compared if you ran a pilot properly.
Exit interview mentions, which require that somebody asks.
And regretted attrition specifically, because total turnover can be flat while the composition shifts.
Why it is not visible
People rarely give monitoring as the reason, because it sounds like an objection to accountability.
They give a better offer, or a change of direction.
Which means exit data understates it systematically, and the only way to find it is to ask directly and anonymously.
The recruitment side
Candidates ask about it, increasingly.
A deployment that requires explaining in interviews is a cost in the hiring market, particularly for senior roles.
Several organisations have found this the most tangible consequence, because it shows up as declined offers rather than as sentiment.
What reduces it
Aggregate-only reporting, which removes the feeling of being individually watched.
Telling people before, with the actual list.
A narrow deployment rather than a general one.
And visibly not using it, which the trust note covers and which is what people actually watch for.
What to check
Did turnover change after your deployment?
Has anybody asked leavers directly and anonymously?
Do candidates ask about it?
And does your business case contain an attrition assumption?