The honest truth about most exit interviews.
Ask anyone who has left a job why they really left. Then ask what they said in the exit interview. The gap between those two answers is the problem. Exit interviews, as practised in most Indian companies, are a performance — a polite ritual in which the departing employee says what they believe is expected of them, the HR representative records it, and the organisation learns almost nothing of value. The process is expensive in time, produces misleading data, and reinforces bad decisions rather than exposing them.
This is not a cynical observation. It is a structural one. The conditions under which most exit interviews occur make honest disclosure irrational for the departing employee. They still need a reference. Their notice period colleagues are watching. The manager who created the problem is still in the building. The organisation asking the questions is the same one they have decided to leave. Rational people in this situation say whatever causes the least friction on the way out.
The result is that most exit interview datasets are dominated by two responses: compensation and career opportunity. Both are real factors in some exits. But both are also the safest things to say — vague enough to be impossible to argue with, impersonal enough to avoid naming anyone, and flattering enough to suggest the organisation is fundamentally fine, just slightly under-paying.
What departing employees actually think — and why they don't say it.
Exit survey research, including work by the Corporate Executive Council and McKinsey, consistently shows that the stated reasons for leaving significantly underrepresent manager-related factors, team culture, and lack of recognition. When employees are surveyed anonymously after leaving — with no remaining dependency on the organisation — the pattern shifts dramatically. Manager quality, lack of feedback, absence of career conversations, and feeling undervalued move to the top of the list.
The gap is not dishonesty in any deep sense. It is self-protection. Three structural factors combine to make honest disclosure unlikely in a standard exit interview.
First, timing. The exit interview happens while the employee is still on notice, still working alongside the colleagues who might be discussed, still dependent on the organisation for a smooth exit and a clean reference. This is precisely the wrong moment to invite candour about the manager.
Second, identity of the interviewer. If the exit interview is conducted by the HR manager who reports to the same leadership team that may have contributed to the departure, the employee has no reason to believe the feedback will reach its intended audience, be acted upon, or be treated with discretion. They have every reason to believe it might not.
Third, absence of psychological safety. Exit interviews ask employees to be honest with an organisation that has already seen their resignation letter. The implicit power dynamic is clear: the organisation did not value the employee enough to retain them, and is now asking for free consulting on what it should have done differently. This is not a setting in which people open up.
A better model: the post-departure conversation.
The most actionable change an organisation can make to its exit process costs almost nothing and requires almost no infrastructure: move the substantive conversation four to six weeks after the employee has left. By that point, they are settled into a new role, no longer dependent on a reference from the previous employer, and free from the social dynamics of the notice period. The conversation can be a thirty-minute call, framed explicitly as a confidential conversation to help the organisation improve, with no feedback attributed to the individual without permission.
The shift in candour is remarkable. Managers who were described in the exit interview as "great to work with, just different styles" become, in the post-departure conversation, the primary reason for leaving. Projects that were described as "learning opportunities" become the source of the burnout that drove the search for a new role. Pay that was described as slightly below market becomes the last in a long sequence of reasons, not the first.
The post-departure conversation should be conducted by someone outside the direct reporting line — a senior HR business partner, an external facilitator, or in smaller organisations, a founder or CEO who is genuinely committed to hearing difficult feedback. The structure should be open-ended, not survey-based: "Tell me about the last six months in the role. What was working? What was making it harder?" These questions produce narrative, and narrative contains information that a five-point scale cannot capture.
Designing the exit process: what should happen and when.
A well-designed exit process has three components, each serving a different purpose.
Component one: the logistics conversation (day of resignation).
This conversation handles the practical mechanics of the exit: notice period, handover timeline, access termination, final settlement, and any contractual obligations. It is not a feedback conversation. Trying to extract honest feedback on the day someone resigns — or in the emotional week that follows — is both poor timing and poor design. Do the logistics cleanly and professionally, and leave the learning conversation for later.
Component two: the knowledge transfer (during notice period).
The purpose of the notice period is not a polite wind-down. It is a structured transfer of institutional knowledge. This means identifying, in the first week of the notice period, exactly what the departing employee knows that no one else does — client relationships, process knowledge, system configurations, project context, informal networks — and building a deliberate plan to transfer it. Most companies miss this opportunity entirely because they treat the notice period as a formality rather than a knowledge recovery operation.
Component three: the learning conversation (four to six weeks post-departure).
This is the conversation most organisations try to have on day one of the notice period and get wrong as a result. Conducted after the departure, with genuine commitment to confidentiality and without attribution, this conversation produces the honest data that makes exit processes worth running. The output should feed directly into decisions about manager capability, team culture, and structural drivers of attrition — not into a file that no one reads.
What good exit data looks like and how to use it.
Exit data is only useful if it is aggregated, tracked, and acted upon. A single exit conversation, however honest, is an anecdote. Five conversations showing the same pattern across the same team or the same manager are a signal. Fifteen conversations showing consistent themes about workload, recognition, or career growth are a mandate for structural change.
The data should be reviewed quarterly, at minimum, by a senior leader with authority to act on what it shows. Exit data that goes to HR and stays in HR is exit data that produces nothing. The question that should drive every review is simple: what pattern is appearing often enough that we have to do something about it? And then: who is accountable for doing something?
“The only exit interview that matters is the one that changes something. Everything else is just paper.”
One final discipline: close the loop with the employees who gave feedback. This is not always possible, and it is not always appropriate. But where a former employee agreed to be candid in a post-departure conversation, and the organisation made a genuine change as a result, a brief note acknowledging that the feedback led to action is both courteous and strategically sound. It builds the reputation of a company that listens — which is itself a retention asset, because people talk about their former employers, and they mention the ones that were worth the honesty.
