Stay interviews: how to find out why your best people stay before they decide to leave

A manager finds out a strong performer is leaving the same way most managers find out: a meeting request with a vague subject line, followed by a resignation letter that has clearly been drafted for days. By that point there is nothing left to do but counter an offer that will not fix the underlying problem, or accept the loss and start writing a job posting. The information that would have prevented this, what was actually bothering this person, how long they had been quietly looking, what it would have taken to keep them, existed weeks or months earlier. Nobody asked.

That is the structural flaw in relying on exit interviews alone. Exit interviews are valuable, but by the time one happens, the employee has already accepted another offer and mentally checked out. The feedback is honest, but it is retrospective. It tells you what went wrong in a relationship that is already over, not what is going wrong in the relationships still salvageable today.

A stay interview flips the timing. It asks the same direct questions, what do you like about this job, what would make you consider leaving, what is missing, while the person is still engaged enough to answer honestly and still reachable enough for the answer to matter. It is one of the simplest retention tools available, and one of the most consistently skipped, mostly because nobody owns the discipline of asking before there is a reason to.

Why the exit interview is the wrong place to learn this

By the time someone sits down for an exit interview, the decision is final, the new offer is signed, and the primary incentive is to leave gracefully rather than to help their soon-to-be former employer fix anything. Answers tend to be diplomatic and general, a better opportunity, a shorter commute, ready for a new challenge, because there is no longer any upside to being specific about what actually drove them out.

The cost of learning too late compounds. The true cost of a bad hire gets modeled constantly in hiring budgets, but the cost of losing a good hire to a problem that was fixable three months earlier rarely gets modeled at all, even though replacing a strong performer is frequently more expensive than the original hiring cost once lost productivity, backfill recruiting, and ramp-up time are added together.

A stay interview does not replace the exit interview. It replaces the assumption that waiting for the exit interview is an acceptable retention strategy. By the time a company is good at exit interviews, it has already lost the person the data is about. A stay interview is the only version of this conversation that happens early enough to change the outcome instead of just documenting it.

What a stay interview actually is, and is not

A stay interview is a structured, one-on-one conversation focused on a single employee's specific experience, asked directly and without a survey form standing between the manager and the answer. It is not a performance review, which looks backward at output and ratings, and it is not an engagement survey, which aggregates anonymous sentiment across hundreds of people into a number nobody can act on individually. A stay interview is deliberately small in scope: one person, their actual day-to-day experience, and what would make it better or worse.

The distinction matters because conflating a stay interview with a performance conversation poisons the honesty of the answer. An employee asked "what would make you consider leaving" in the same meeting where their quarterly rating gets delivered will give a careful, hedged answer designed to avoid sounding ungrateful or difficult, not a real one. The two conversations need to be separate in time, tone, and purpose, even when the same manager runs both.

It is also not a one-time event triggered by a flight risk flag in an HR system. Run only on people a manager suspects are about to leave, a stay interview becomes an interrogation rather than a genuine check-in, and employees notice the difference immediately. The tool only works when it is run consistently, on everyone, regardless of whether anyone currently suspects they are a retention risk.

The questions that produce a real answer

"Are you happy here" is the stay interview equivalent of "why are you leaving" on an exit interview: a question so broad that it almost guarantees a vague, polite answer. Specific questions produce specific signal. What part of your week do you look forward to, and what part do you dread. What would need to change for this to be your best job yet. If you were job hunting today, what would the posting have to offer that this role does not.

Comparative and hypothetical framing works especially well because it sidesteps the social pressure of stating a direct complaint. Asking what a recruiter calling with a better offer could point to that this job is missing gets a far more concrete answer than asking whether someone is satisfied, because it requires naming an actual gap rather than rendering an overall verdict on the relationship.

LinkedIn Talent Solutions research on retention and employee experience has repeatedly found that the specific, lived details of day-to-day work, not abstract satisfaction scores, are what actually predict whether someone starts looking elsewhere. Stay interview questions should chase those details directly: a recent frustrating week, a recent genuinely good one, and what was different between the two.

Who should ask, and how often

The direct manager is usually the right person to conduct a stay interview, not HR and not a skip-level, because the manager is the one who can actually act on most of what comes up: workload, recognition, growth opportunities, day-to-day friction. The tradeoff is that a manager who is themselves part of the problem will get a softened answer, the same way a departing employee softens criticism of a manager sitting across from them in an exit interview.

The practical fix is pairing manager-led stay interviews with an occasional skip-level or HR check-in, especially for employees who report concerns that trace back to their own manager's behavior. Neither channel alone catches everything, and a company that relies only on the manager relationship to surface retention risk will systematically miss the cases where that relationship is the actual risk.

Cadence matters more than most companies assume. An annual stay interview, bolted onto the performance review cycle, arrives too rarely to catch a problem before it hardens into a resignation. Twice a year, deliberately separated from any review conversation, is a more realistic minimum, with a dedicated first check-in inside the opening months of a new hire's tenure. Strong onboarding already sets expectations for how a new hire's first few months should go, and a stay interview at the ninety-day mark is a natural extension of that same discipline, catching early friction before it becomes a pattern.

Turning the answer into something before someone starts job hunting

A stay interview that surfaces a real concern and is then filed away without follow-up teaches the employee the same lesson a skipped exit interview teaches a departing one: that being honest did not matter. The fix is procedural, not aspirational. Every stay interview should end with at least one specific, trackable commitment, a project reassignment, a conversation about growth path, a fix to a recurring scheduling problem, something concrete enough that the employee can check six weeks later whether it actually happened.

Recruiting metrics that actually matter tend to stop measuring the moment someone is hired, but retention deserves the same discipline applied after the hire as before it. A manager who runs stay interviews but never closes the loop on what came up is collecting data without using it, which costs the same honesty for nothing in return as an unread exit interview does.

The commitments that come out of a stay interview also do not all belong to the manager alone. A pattern across several direct reports, the same complaint about unclear growth paths, the same frustration with a specific process, should get escalated to whoever actually owns that process, the same way a recurring exit interview theme should reach the person who can fix it rather than disappearing into a quarterly summary nobody traces back to its source.

The trap: when a stay interview starts to feel like surveillance

A stay interview introduced poorly, sprung on an employee with no context, framed around retention risk rather than genuine interest in their experience, reads as exactly what it sounds like: a company trying to detect and head off a resignation rather than a manager trying to understand and improve someone's actual experience of the job. Employees pick up on that framing immediately, and it produces the same guarded, careful answers a badly timed exit interview does.

The fix is framing and consistency. A stay interview introduced as a standard, recurring practice applied to everyone, explained honestly as a chance to fix small problems before they become big ones, lands very differently than one that shows up only after a manager has grown nervous about someone's engagement. Consistency is what separates a genuine retention practice from a reactive one dressed up to look proactive.

SHRM's guidance on employee relations consistently emphasizes that trust in a sensitive conversation is built by the pattern around it, not the conversation itself. A single well-run stay interview cannot overcome a broader culture where feedback has historically gone nowhere. The conversation only works as well as the follow-through a company has already demonstrated it is capable of.

Measuring whether your stay interview program is actually working

The honest test of a stay interview program is not how many get scheduled. It is whether the people who have them are more likely to stay, and more likely to report real improvement, than the people who do not. A program with perfect completion rates and no measurable change in voluntary turnover is producing meetings, not retention.

Harvard Business Review's research on employee retention consistently finds that the organizations that actually move retention numbers are the ones treating a conversation like this as an operational habit with tracked follow-through, not a one-off gesture. The useful audit compares stay interview commitments against whether they were actually delivered, and compares voluntary departures against whether the person who left had a stay interview in the prior six months and what came out of it.

U.S. Bureau of Labor Statistics data on employee tenure shows that median tenure varies widely by age, industry, and role, which means there is no single national benchmark a company can chase. The more useful number is internal and longitudinal: is average tenure on a given team improving after stay interviews became routine, or is the program running without anyone checking whether it changed anything. Most companies that skip this audit are running a well-intentioned ritual. The ones that run it are running an actual retention program.