Every company that cares about attrition ends up running exit interviews. Fewer run stay interviews. I think that is backwards, though not because exit interviews are useless. It is because of when each one happens and what the person across the table has to lose.

What each one is

An exit interview is a structured conversation, or a form, with someone who is leaving. It asks about the reasons for leaving, what the job was really like, how they found their manager, and what they would change. HR usually runs it, often in the last week of the notice period.

A stay interview is a conversation with a current employee, usually held by their own manager or a skip-level leader, and not by HR as a survey. It asks what keeps them here, what might make them leave, what they would like to learn or change, and what the company could do that it does not. The idea is generally credited to Richard Finnegan, who wrote about it in the context of retention; it is not a legal or standard process, just a practice.

The argument for exit interviews

They are straightforward to run, they apply to everyone who leaves, and they build a data set. After a year, you may notice that eleven of thirty-four leavers from one function mention the same project lead, or that a large number cite a pay gap against a particular competitor. Patterns across many exits are real signals.

They also produce non-obvious facts: a process that drove people mad, a policy no one understood, harassment that was never reported. For some leavers, the exit conversation is the first safe place to say it.

Why they are less reliable than they look

Think about the leaver’s position. Their notice period is almost over. They need a clean relieving letter, an experience letter, a settlement, and perhaps a reference for a background check by the next employer. In Indian workplaces, where reference calls and tight professional circles are real, why would anyone be fully candid? So they say “better opportunity” or “career growth”, which is true and polite and tells you nothing.

Even when people are candid, they may be wrong about their own reasons. Someone who left because of a manager may sincerely report salary, since pay is a socially acceptable explanation. And it is too late. The person is gone, the offer is signed, and in most cases no feedback can reverse it. Exit interviews are a post-mortem.

One mitigation: hold the conversation after the last working day, a few weeks later, run by someone outside the reporting line, or by an external party. Response rates drop, but the answers are more honest.

The argument for stay interviews

The person is still here, and the problem is still fixable. A stay interview with a good engineer who mentions that she has been doing the same work for two years and wonders about a role in the architecture team gives the manager a chance to act while it still matters. The cost of that action is usually small. The cost of losing her, after you add up recruiting and ramp-up time, is often several lakhs.

They also build the trust that makes later feedback honest. If a manager asks once a year “what would make you leave?” and then actually does something about the answer, the next conversation is more direct.

Why stay interviews fail, too

Be fair to the other side. A stay interview with a manager who is the cause of the problem will produce polite silence. Employees who fear being tagged as a flight risk will say everything is fine. And if nothing ever changes after the conversations, they teach people that asking is theatre.

So the design matters:

  • Train managers on how to ask open questions and how to listen without defending.
  • Choose who is interviewed: start with high performers, critical-skill employees and people in roles with high attrition, instead of everyone.
  • Where the manager is the problem, have a skip-level or HR business partner hold the conversation.
  • Agree one or two actions, write them down, and revisit in three months.
  • Keep notes confidential, with only themes reported upward.

A short set of questions works better than a long script: What do you look forward to on Monday? What would you miss if you left? What would tempt you to take a call from a recruiter? What is one thing that, if changed, would make this a better job? Is there anything I do that makes your work harder?

Side by side

Exit interviewStay interview
TimingAfter the decisionBefore any decision
CandourOften guardedDepends on trust in the manager
Can it change the outcome?Rarely for that personYes, sometimes
Best useSpotting patterns over many exitsFixing individual and team issues early
CostLowManager time, plus training

My view, then: do both, but put the effort in the stay interview. Treat exit data as a periodic audit of what you missed. If you only have time for one, run stay conversations for the thirty or forty people you would be most sorry to lose, and review exit data twice a year for trends. Do not trust a single exit interview to tell you the truth, and do not wait for one to learn what a stay interview would have told you six months earlier.

Figures and names in the examples are illustrative.

Leave a Reply

Trending