Exit Interview

An exit interview is a conversation or survey conducted with a departing employee to understand why they're leaving and what the organization could do better. Its value is entirely in the honesty of what it collects and whether that feedback actually changes anything afterward — it's a listening exercise, not a logistics step, and shouldn't be confused with the mechanics of Offboarding Checklist.

Purpose

• Honest reasons for leaving — the real factors behind the departure (compensation, management, growth, culture, a specific incident), which are often more candid than anything said during employment because the employee has less to lose.
• What could improve — feedback on team dynamics, management practices, tools, or processes that the organization can act on for the people who remain.
• A read on retention risk elsewhere — one exit rarely means much alone, but a pattern across several exit interviews (e.g. several people citing the same manager or the same broken process) is a strong signal worth investigating.

Format options

• Structured questions — a consistent set of questions asked of every departing employee, so answers can be compared and tracked over time rather than treated as one-off anecdotes.
• Written survey — lower-pressure than a live conversation, useful for employees who'd rather not say difficult things to a person directly, and easy to aggregate across many exits.
• Live conversation — allows follow-up questions and nuance a survey can't capture, at the cost of being more intimidating for some departing employees.
• Who conducts it — ideally someone other than the employee's direct manager, such as HR or a skip-level, since a manager who is themselves part of the reason for leaving will get a filtered answer at best.

Feeding findings back into retention practice

An exit interview only pays off if its findings go somewhere: aggregate themes across exits (not individual quotes) should reach the people who can act on them — HR, leadership, the affected team's management chain — on a regular cadence, and specific, recurring issues (a manager named repeatedly, a policy cited again and again) should trigger real follow-up, not just a note in a spreadsheet. Treating the interview as input to Organizational Development work, rather than an archival record, is what makes it worth the departing employee's time to answer honestly.

Common pitfalls

• Data collected but never acted on — employees notice when the same complaints get raised exit after exit with no visible change, and it erodes trust in the process for everyone still asking them to participate.
• Conducted by the person the departure is actually about — asking a manager to interview someone leaving because of that manager guarantees a filtered, unhelpful answer.
• Treated as a formality — a rote checklist of questions asked without real interest in the answers signals to the departing employee that their input doesn't matter, and they answer accordingly.
• No consistency across interviews — ad hoc questions each time make it impossible to spot patterns across multiple departures.
• Timed too late or too early — squeezed in during a chaotic last day gets rushed, low-quality answers; conducting it well before the employee has mentally checked out can also skew candor.

Learn more

• Offboarding Checklist for the logistics process this feedback conversation runs alongside.
• Organizational Development and People and Organizational Development for the broader practice exit-interview findings should feed into.
• Performance Review Meeting for the ongoing feedback loop an exit interview complements after the fact.