Most exit interviews go fine as conversations. The departing employee is often candid, the interviewer takes careful notes, and the notes end up in a folder no one opens again until the next person on that team resigns.
This guide covers exit interview best practices for the people and talent leaders who run them, from choosing who gets an interview to reading a quarter of departures side by side.
I would judge an exit interview by one test: can it be read beside the last ten? A conversation that went well but sits in its own format tells you about one person, and leadership will not change a manager or a pay band on one person’s account. So every step below is built for reviewing departures together, which is the part most programs never reach.
The cost of skipping it shows up later, when a second and a third person leave the same team and no one can say whether their reasons were the same.
Why most exit programs learn so little.
An exit interview reaches things current staff rarely say, and it also collects the safest version of why someone left. Every step in the next section is built around both facts.
Once someone has decided to leave, they have less reason to protect a working relationship. So they will often say what current staff keep to themselves, such as the manager who never had time for them or the promotion that was promised twice.
They also have good reasons to leave on friendly terms. A reference and a pleasant last two weeks both argue for the safe answer, so the reason a leaver gives first is often the one that offends no one, like a better offer or more money. I would treat that first answer as where the conversation starts. The useful detail usually sits one question later, in whatever made them open a job board.
That is why I treat a single exit interview as a lead to follow up. A pattern shows up only when several people from the same team, or who joined in the same year, describe the same problem in their own words. The program has to be built so those accounts can be laid side by side.
Exit interview best practices, in seven steps.
The seven steps run in the order the work does, from deciding who gets an interview to telling staff what changed. The early steps decide whether people talk to you openly, and the later ones decide whether anything you hear gets used.
Decide which exits get an interview.
Give the full conversation to the departures you can least afford to misread: regretted exits, senior people, and anyone leaving a team that has just been reorganized. Offer everyone else a short written form built on the same core questions.
Interviewing every leaver at full length sounds thorough and usually produces a backlog that no one reads. The written form keeps the questions identical, so those answers still count when you review the quarter.
For a senior or sensitive exit, I would split the interview into a short written prompt with the core questions and a call that goes deeper on what the answers raised.
Choose who runs the conversation.
Pick a neutral interviewer, usually someone in human resources (HR) who never managed the employee. A direct manager starts the conversation already defending the decisions the employee is about to describe, and the employee knows it.
Tell them what happens to their answers.
Open by saying why you are holding the conversation, how long it will take, and who will read the notes. Then say plainly that themes go to leadership and names do not. The opening minute is where the employee decides how much to tell you, so it deserves more care than anything else you say.
Ask the same core questions every time.
Use one set of questions for every exit, in the same order, and add follow-ups freely around it. The fixed core lets you compare the fifth conversation of the quarter with the first. The set I would start from is in the next section.
Listen for the moment that started the search.
When the employee gives a reason, ask when they first noticed it. An answer like “a better opportunity” leaves you nothing to act on, while the month they started looking, and what happened that month, can point at a manager or a decision.
Keep your attention on the person, and write the notes after the call or have the call recorded. An interviewer typing through every answer looks like someone filing a report, and the answers get shorter to match.
Review the quarter’s exits on a fixed date.
Put a date in the calendar each quarter to review every exit from that quarter together. Tag each conversation with its themes as you go, so the review comes down to counting how many people raised each theme and in which teams.
A theme earns its place in the brief when people from more than one team raise it, or when it clusters in one manager’s group. That second kind is the finding leaders most need to see and least want to.
Share themes and close the loop.
Send leadership a one-page brief with the top themes, how many leavers raised each one and from which teams, and the action you recommend. Keep it short enough to read before a meeting, and keep the individual accounts out of it.
Then tell current staff what departing colleagues said and what is changing because of it, even when the answer is that something is still being looked at. A short note each quarter is enough.
The questions worth asking every leaver.
These six areas cover what most exits turn on. Ask only open questions, so the employee chooses the words, and give each answer the same follow-up: “When did you first notice that?”
| Area | Questions to ask |
|---|---|
| Why they started looking | What first made you look at other roles? When was that? |
| The job against the offer | How did the job compare with what you expected when you accepted it? Which parts felt most and least worth your time? |
| Management and support | How would you describe the support you got from your manager? What would have made that working relationship better? |
| Team and culture | How did the team and the wider company feel to work in? Where did the company live up to its values, and where did it fall short? |
| Growth | Did you see a clear next step for yourself here? What would have made staying the better choice? |
| Closing | What would you tell leadership to change first? Is there anything else you want them to hear? |
Leave out any question that suggests its own answer. “Was it the workload?” gets a yes from people who left for other reasons, and a theme built on those answers is one you planted.
Where Metaview fits in an exit program.
Two parts of the method are slow by hand: getting a usable record of each conversation without typing through it, and reviewing a quarter of them together. Metaview’s Notetaker and Reports do those two jobs for hiring conversations, and Meltwater’s People team used them on interviews with its own staff.
The Notetaker joins as a visible participant and records the call, then transcribes it and turns the conversation into structured notes. Metaview captures every spoken word of the conversation. So a quarterly review can start from what each person said, and the interviewer can listen through the follow-up question instead of writing it down.
- 1The search box looks across calls, candidates, and topics.
- 2Each call carries its type and length, here a “Role Intake” call beside the job interviews.
- 3The “Recommendation” column holds each interviewer’s own call on the candidate.
The record only helps if it gets the names right, including the manager a leaver meant.
At Metaview, transcription is the first mile of our AI product: if names, roles, companies, and context are wrong, everything downstream gets harder.”
Before you record an exit conversation, get the employee’s agreement in whatever way your own policy and local law require. That process belongs to your team. I would ask before the call, in writing, and offer the same conversation unrecorded to anyone who says no. A recording doesn’t make anyone more candid, and some people will say less with one running, so a refusal is an answer to respect.
Multi-source notes in the Notetaker combine a call with documents into one set of notes, which suits the split exit from the first step, because the written prompt and the follow-up call can sit together.
- 1Each heading in the notes names the sources it draws on.
- 2The “Sources” panel lists the call and the documents behind these notes.
- 3The panel’s own note says what multi-source is for: one set of notes for a conversation that happened in parts.
Then comes reviewing them together. Reports runs reports over your own conversations, filtered and broken down by fields such as department, as the builder below shows for one team’s sales screens.
- 1Filters narrow the report to one department and a date range.
- 2“Group by” and “Break down by” choose how the conversations are split.
- 3The preview counts conversations for each interviewer, split by the recommendation that interviewer gave.
Meltwater’s People team did this with a different set of conversations. It interviewed its top global sellers, and those interviews followed a consistent framework. Carol Ann Vance, Senior Director of Global Talent, described where that left the team: “We had a huge amount of qualitative insights, but they were scattered across all the interviews we had done. We needed a scalable way to extract all the key themes and turn them into data we could use in our programs.”
The team had tried this before by exporting the conversations to Excel and building pivot tables by hand. With Reports, in Carol Ann Vance’s words, “we could analyze those interviews at scale instead of treating them as isolated stories.”
Those were conversations with people who stayed. I would copy the move for exits: every one of Meltwater’s interviews followed the same framework, so the answers could be read together.
This one-minute clip from Metaview’s own channel shows Reports, the view where that review happens.
If your exit conversations already happen on video calls, I would start with the recording and the quarterly review, and keep the conversation itself with your interviewer.
How to tell your exit program is working.
Pull last quarter’s exits and run four checks. Where one fails, fix that one first.
- Pick any two interviews from the quarter. If you can’t answer the same core questions from both, fix the question set before anything else.
- Count how many exits had a written record within a day of the call. If some had none, fix how the conversation is captured.
- Check that the quarterly review happened on its date and produced a brief with counts by team. If it slipped, give the date to one named person.
- Ask a few current employees whether they heard what leavers said last quarter. If they didn’t, send the quarterly note from the last step before you run another exit interview.
If I could run only one of these, it would be the second. An exit with no usable record is a departure you can’t add to the pattern, however good the conversation was.
Turn a quarter of interviews into patterns you can read.
See the Notetaker and Reports on the kind of conversations your team already holds.
Frequently asked.
Should exit interviews be anonymous?
Anonymity in the conversation itself usually costs more than it gives, because you can’t ask a follow-up question or tell whether two accounts came from the same team. Employees need confidentiality in what gets shared: themes go to leadership, and names stay with the interviewer. If someone will only answer anonymously, an unnamed written form is better than no answer.
How long should an exit interview take?
Half an hour is enough for most exits. Longer sessions tend to circle back to the same points, and the employee is often counting down to their last day.
Is an exit survey enough on its own?
A survey works for the exits you would not interview, and its fixed questions are easy to count. It can’t ask when the problem started, which is usually the answer worth having, so keep conversations for the departures you most need to understand.
What if a leaver doesn’t want an exit interview?
Let them decline without pressure, and offer the written form instead. The person you pressed will tell former colleagues how their exit was handled, and the next leaver will arrive more guarded.
Who should see exit interview notes?
The interviewer and whoever runs the quarterly review. Leadership gets the themes and the counts, and the departing employee’s own manager never sees an individual account, because word of it reaches the next leaver.
