The exit interview is the most honest conversation most companies ever have with an employee, and it is honest precisely because it no longer matters. She's leaving. The truth costs her nothing now, so you finally get it — the manager thing, the pay thing, the “I asked about growth twice and nothing happened” thing — delivered politely, two weeks before the knowledge walks out with her. Companies file these notes carefully, which is a strange ritual when you think about it: conducting autopsies with precision while skipping checkups entirely.

The stay interview is the checkup. Twenty minutes, one-on-one, with someone who hasn't resigned, asking the questions the exit interview asks — while the answers can still change the ending. At a small company it may be the single highest-return twenty minutes on your calendar, because you don't lose people in categories; you lose the person, the one who knows the billing system and trains the new hires, and replacing her costs half to two times her salary before you count the morale tax.

What it is not

Three boundaries keep the conversation honest. It is not a performance review — the moment quality of work enters the room, candor leaves; hold it months away from review season. It is not a compensation negotiation — if pay comes up, note it seriously and route it to your comp process rather than bargaining in the moment. And it is not a survey — anonymous engagement scores tell you the weather; this tells you why this person, with a name and a resignation letter she hasn't written, stays or wouldn't.

The five questions

The two-week rule

Here is the mechanism that decides whether stay interviews build trust or burn it: within two weeks, something she named gets visibly better. Not everything — something, usually the small thing from question three. The meeting-that-should-be-an-email dies; the software seat gets approved; the interruption pattern she flagged changes. The action is the message. It says answers here convert into outcomes, and it's what makes the second stay interview — and the harder truths in it — possible. An interview followed by silence is worse than no interview at all: you've converted an unasked question into a broken promise.

The traps

Don't promise in the room — “I'll look into it” honored beats “consider it done” abandoned. Don't defend — the instant you argue with her answer, the interview is over even if the meeting continues; the only correct response to a criticism you disagree with is to write it down and thank her. And don't interview only your flight risks — the steady ones read the pattern instantly (this meeting means they think I'm leaving), and your quiet reliable people are precisely the ones whose departure you never see coming. Interview everyone, on a cycle, so the conversation means nothing except that they work here.

Cadence and scale

Twice a year per person, thirty minutes blocked so twenty never feels rushed, staggered so it's always somebody's month. At a fourteen-person company that's about five conversations a month — less time than one bad hire's first interview loop. Keep one page of notes per person: what keeps them, what would move them, what you changed. Read the file before each next round; walking in remembering what she said last time is itself a retention act.

The bottom line

Every departure ships with a truth that was available months earlier, cheaper. The exit interview collects it after it expires; the stay interview collects it while it compounds. Five questions, twenty minutes, twice a year, with one non-negotiable: within two weeks, something named gets visibly better. You will still lose people — but you'll stop losing them to reasons you'd have gladly fixed, discovered fifteen days too late to fix them.

— Tom

Hear it while it can still change the ending

HRByDesign keeps the stay-interview cycle on the calendar, the one-page notes in one place, and the two-week follow-ups from slipping — retention as a running system instead of a good intention.

See how HRByDesign works →

About the author

Tom Christian is the founder of HRByDesign, an AI-native HR platform built for SMB and growth-stage HR managers running the function alone.

He has spent twenty years inside people operations, training, and QA at scale — Guardian Life, ConnectiveRx, and Horizon Blue Cross Blue Shield's Service Division. He writes about HR-of-one survival, compliance that actually applies to small employers, the automation/judgment line, and the operating discipline of running an HR function without a department.