Turnover by Manager, and What It Does Not Prove

Treat concentrated turnover as a question rather than a finding, and ask the question before anybody draws a conclusion. Turnover by manager is the most commonly produced people metric and the most commonly misread: a number that genuinely does indicate something, about four times out of ten, and indicates something else entirely the rest of the time.

The pattern described in “Turnover by Manager, and What It Does Not Prove” becomes useful only when the source data is consistent and interpreted with context. Teams exploring fireable offenses through Monitask can use time and project records to locate operational questions, while direct feedback, HR evidence and accountable review remain necessary to explain them.

It is worth producing anyway. The alternative is noticing a pattern three years late, through an accumulation of individual conversations nobody connected.

For an independent reference relevant to “Turnover by Manager, and What It Does Not Prove”, consult the Cloudflare insider-threat overview. Use it to test record quality, access, retention, fair process and exception handling against the organisation’s real departure workflow.

The four innocent explanations

A market effect: the team does work that is in demand everywhere, and people leave for more money regardless of who manages them.

A composition effect: the team is junior, or entry-level, or seasonal, and turnover is structurally higher in that population.

A deliberate effect: the manager inherited a team with problems and is addressing them, which produces departures that are the intended outcome.

A size effect: three departures from a team of five is a striking percentage and may be three unrelated events.

Each of these is real and common. A review that produces a ranked list of managers without accounting for them is producing a ranked list of team types.

What to compare against

• The same team in previous years, which controls for composition.
• Comparable teams doing similar work, rather than the organisation as a whole.
• The market, where anything is known about it.
• The period before and after a change of manager, where there has been one.

The last comparison is the strongest available and the one that requires data the organisation usually has. A team whose turnover tripled when a manager arrived, and normalised when they left, is telling a story that survives most objections.

When none of them fits

Where the comparisons have been made and the pattern remains, the question becomes what to do, and the answer is not to confront somebody with a spreadsheet.

Look first at what else is known: grievances, informal complaints, exit interview content, engagement responses, absence. A single metric is weak evidence and three weak signals pointing the same way is something else.

What the exits themselves say

The files are more informative than the count. Departures handled well, with notes and proper process, suggest a manager who is addressing problems. Departures with no contemporaneous notes, late processes and resignations following difficult conversations suggest something different.

That reading requires the files to contain the things described elsewhere on this site, which is one more reason the record matters. An organisation whose files are empty cannot tell these two situations apart.

Raising it

If it is raised, raise it as a question about support rather than as an accusation, at least initially. Managers with high turnover are sometimes struggling with something fixable — an impossible structure, no authority over pay, a team they inherited.

Starting there costs nothing and preserves the possibility of a useful answer. Starting with the accusation produces a defence, and the defence is usually one of the four innocent explanations, asserted rather than tested.

The metric that is better

Where it can be measured, regretted turnover — people the organisation wanted to keep — is considerably more informative than total turnover, and it requires somebody to record, at the time, whether each departure was regretted.

That field costs one tick per exit and almost nobody has it. Adding it to the exit checklist is a year's wait for data that answers the question properly, which is a question worth settling once rather than arguing about annually.

The manager who is about to leave

A pattern worth watching alongside turnover is the manager whose team is stable and who is themselves at risk of leaving, because their departure frequently takes several people with it over the following year.

That is visible in the aggregate afterwards and almost never anticipated. Where a team's relationships run through one person, the organisation has the same concentration problem it has with client relationships, and the same remedy: make sure more than one person holds them.

Keeping it out of the wrong hands

A ranked list of managers by turnover, circulated widely, becomes a management tool nobody intended and does damage that is hard to undo.

Produce it, use it to ask questions, and keep it where it can be interpreted by somebody who understands the four explanations above. A number that means four different things should not travel without the person who can tell them apart.