Exit interview questions: what to ask and how to analyse the results

Exit interviews have a reputation for producing data that nobody acts on. The departing employee gives polished, diplomatic answers. The HR team logs a few notes. The data sits in a spreadsheet and is never systematically analysed. Six months later, the same patterns that drove the exit are still in place, driving more exits.

The problem is usually not the exit interview itself but how the questions are framed and how the results are processed. This guide covers both.

Why exit interviews produce shallow data, and what to do about it

The standard exit interview question ("Why are you leaving?") produces standard answers. Employees who are leaving have little incentive to be fully candid: they may need a reference, they do not want to burn bridges, and they have often mentally processed the decision in a way that packages the real reasons into something presentable.

The solution is not to pressure employees for honesty. It is to design questions that naturally produce more specific, less rehearsed responses, and to create an interview environment where candour feels safe.

Three structural changes make an exit interview more likely to produce useful data:

Shift from reasons to experiences. "Why are you leaving?" invites a summary. "Tell me about the moment you first started thinking about leaving" invites a story. Stories contain more specific and more honest data than summaries.

Ask about the future, not just the past. "What would have needed to change for you to stay?" reveals the levers that actually mattered, rather than just the complaints.

Normalise the difficult topics. If your interview guide jumps from "how was your experience here?" to "any other comments?", you are implicitly signalling that the difficult stuff does not need to be said. Naming the difficult topics directly ("Some people tell us they struggled with [specific aspect]. Did that come up for you?") gives the employee permission to address them.

Exit interview questions that go beyond the obvious

Opening questions (establishing comfort and context)

"Before we get into the specifics, can you tell me a bit about your time here overall — how it evolved and how you feel about it now?"
"How has this role compared to what you expected when you joined?"

These open questions let the employee begin wherever feels most important to them. What they choose to lead with is itself informative.

Getting to the real reason for leaving

"When did you first start thinking seriously about looking elsewhere?"
"Was there a specific moment or event that crystallised the decision?"
"What was the conversation that made you think 'I should start looking'?"
"If you could go back to six months ago, what would have needed to change for you to be planning to stay?"

The "moment" question is consistently one of the most productive in exit interviews. People can usually name the specific event or conversation that moved them from "this is frustrating" to "I'm leaving." That specific event is far more analytically useful than the general complaint category.

Manager and team dynamics

"How would you describe your working relationship with your manager?"
"Did you feel your manager gave you what you needed to do your best work?"
"Were there dynamics within the team that made your work harder or easier?"
"Was there anything your manager could have done differently that would have made a difference?"

Manager quality is consistently one of the top drivers of voluntary attrition, but it is also one of the topics employees are most reluctant to discuss directly. Framing questions as "what could have been done differently?" rather than "what was wrong with your manager?" reduces the felt accusatory nature of the question and produces more honest answers.

Recognition, growth, and compensation

"Did you feel your contributions were recognised here?"
"Were you given opportunities to develop in the direction you wanted?"
"How did your sense of your career progression here compare to what you were hoping for?"
"Was compensation a factor? Are you comfortable sharing in what way?"

Compensation is often cited as a reason for leaving, but it is frequently a proxy for other dissatisfiers. When someone says "I got a better offer," the actual driver may be that they felt undervalued, were not progressing, or were attracted by a different type of work. The follow-up questions matter: "Was the better offer primarily about the money, or were there other aspects of the new role that appealed to you?"

Culture and organisational fit

"How would you describe the culture here to someone who has never worked in this organisation?"
"Was there anything about how this organisation works that felt like a poor fit with how you work best?"
"Were there things you observed here that you thought were not consistent with the organisation's stated values?"

The gap between stated values and lived experience is a significant driver of attrition, particularly among employees who chose the organisation partly on the basis of those values. The third question in this set often surfaces specific incidents that illustrate that gap.

What the organisation could improve

"If you were advising the leadership team on one thing they should change, what would it be?"
"Is there something we don't know that you think we should know?"
"What is the thing people here don't talk about that probably should be talked about?"

These questions are best placed at the end of the interview, after rapport has been built through the earlier sections. By this point, most employees feel comfortable enough to engage with direct improvement questions.

Closing

"Is there anything we haven't covered that you'd like to raise?"
"Is there anything you would want your colleagues or manager to know, but that you haven't been able to say directly?"

The second closing question sometimes produces the most candid response in the entire interview. The framing ("that you haven't been able to say directly") acknowledges that there are things people want to say but find difficult to say, and gives explicit permission.

Structuring the exit interview

Timing. The last day or the final week before departure is standard, but the week after departure often produces more candid responses. Employees who have already finished are less concerned about references and departing-day impressions. If your process allows it, consider a brief follow-up call two to four weeks after departure.

Format. One-to-one conversations (not group sessions) with a neutral party produce the most candid data. The interviewer should not be the departing employee's direct manager. HR business partners or a dedicated exit interview function are the standard approach.

Duration. 30-45 minutes is sufficient for most exit interviews. Longer sessions are appropriate for senior employees or those with specific insights the organisation wants to understand in depth.

Recording and consent. Recording with consent enables full transcript analysis rather than note-dependent reconstruction. Most employees consent when the purpose is explained clearly. If recording is not possible, detailed contemporaneous notes taken immediately after the interview are the next best option.

How to analyse exit interview data at scale

Individual exit interviews produce individual stories. The strategic value of exit interview data comes from patterns across many interviews, and those patterns are only visible through systematic analysis.

The challenge of aggregation

Most organisations aggregate exit interview data by logging responses into categories (compensation, management, career development, personal reasons) and counting which category appears most frequently. This produces a frequency table that is rarely actionable.

The problem is that categorisation at this level of abstraction loses the specific, contextual information that would allow the organisation to understand what is actually driving attrition, not just what category it falls into.

"Management issues" could mean: a specific manager whose behaviour is well known but undiscussed; a pattern of poor feedback culture; a structural problem with span of control; or a mismatch between the management style and the expectations of a particular employee cohort. Knowing that 40% of exits cite "management issues" tells you where to look, not what to fix.

Systematic thematic coding

A more useful approach is systematic thematic analysis of the full verbatim transcript text, rather than categorisation of summary notes.

The analytical process:

Collect full transcripts (or detailed verbatim notes) across all exit interviews in the period
Code each transcript for themes (not just topic categories but the specific nature of the complaint, the person's framing of the issue, and the language they use)
Identify patterns across the coded transcripts: what themes appear consistently, in what combinations, and in which employee segments
Cross-tabulate themes by department, tenure, level, manager, and other relevant metadata

This turns a collection of individual stories into a structured dataset that surfaces the patterns invisible in individual reading. For example, you might find that "manager feedback" complaints cluster disproportionately in one division, or that the trigger events described by employees who left in their first 18 months consistently involve a specific aspect of the onboarding experience.

For the full analytical approach, see exit interview analysis: how to find the real reasons people leave.

Anonymising transcripts

For thematic analysis to be done transparently within an organisation, transcripts need to be anonymised so that analytical output can be shared without identifying individual departing employees.

Practical anonymisation steps:

Replace all names (the employee's name, colleagues' names, managers' names) with neutral labels ("the participant," "a colleague," "their manager")
Remove specific dates, project names, and other details that could identify the individual
Check for indirect identifiers: details that do not name a person but would identify them in context ("the only person in the Belfast office who...")
For very small teams or highly specific roles, consider not circulating verbatim quotes at all, and present only synthesised findings

Skimle's analysis pipeline processes transcripts and produces thematic output that is already one step removed from individual identification: the analytical output describes patterns across the corpus rather than attributing statements to individuals. See anonymising qualitative data for a full guide to the approach.

Making findings actionable

Analytical findings from exit interviews are only valuable if they reach the people who can act on them, and those people need enough context to know what to do.

Effective exit interview reporting:

Connects themes to specific business outcomes (attrition rate in the affected segment, average tenure at exit)
Presents anonymised illustrative quotes to make the patterns tangible rather than abstract
Prioritises findings by the number of people affected and the actionability of the response
Attributes findings to the appropriate level of the organisation: some patterns are individual manager issues, some are team culture issues, some are organisational policy issues

For guidance on communicating qualitative findings to leadership audiences, see presenting qualitative research findings to executives.

Frequently asked questions

Should exit interviews be mandatory?

No. Mandatory exit interviews produce poor data: employees who are coerced into attending give minimal, formulaic responses. Exit interviews are most useful when the employee has opted in, either because they were asked directly or because the process was framed in a way that made participation feel worthwhile for them. A voluntary programme with thoughtfully designed questions will produce better data than a mandatory programme with a generic questionnaire.

What is the right sample size for exit interview analysis?

For reliable pattern identification, you need enough interviews to move beyond the individual. As a rough guide, 20-30 exit interviews across a defined period and employee population is the minimum for basic thematic analysis. For segment-level analysis (patterns by department, level, or manager), you need enough interviews within each segment to avoid drawing conclusions from very small samples. Monthly or quarterly aggregation of a rolling programme is more analytically useful than annual batches.

How do you handle an employee who seems angry or upset?

Listen without defending the organisation. An exit interview is not a debate. The goal is to understand the employee's experience, which means acknowledging what they felt without either validating or challenging their interpretation. "That sounds like a really difficult situation. Can you tell me more about what happened?" maintains the conversation without either agreeing with or contradicting their account.

Can exit interview data be used for performance management of managers?

With significant caution. Individual exit interviews are not a reliable basis for conclusions about a specific manager's performance: the departing employee may have had an atypical experience, the context may be complex, and the manager should have an opportunity to respond. However, consistent patterns in exit interview data pointing to a specific manager or team (particularly when corroborated by engagement survey data or retention metrics) are legitimate inputs into a performance conversation. Anonymised thematic findings, rather than attributed quotes, should be the basis for any such conversation.

Running exit interviews at scale and need to find the patterns across many conversations? Try Skimle for free and see how AI-assisted thematic analysis turns your exit interview transcripts into a structured, anonymised picture of what is driving attrition.

About the authors

Henri Schildt is a Professor of Strategy at Aalto University School of Business and co-founder of Skimle. He has published over a dozen peer-reviewed articles using qualitative methods, including work in Academy of Management Journal, Organisation Science, and Strategic Management Journal. His research focuses on organisational strategy, innovation, and qualitative methodology. Google Scholar profile

Olli Salo is a former Partner at McKinsey & Company where he spent 18 years helping clients understand the markets and themselves, develop winning strategies and improve their operating models. He has done over 1000 client interviews and published over 10 articles on McKinsey.com and beyond. LinkedIn profile