The exit interview tells a manager why someone left. Stay interview questions get the same answers while there’s still time to do something about them, and almost nobody asks them consistently. That’s the strange part, because the logic is hard to argue with. Feedback collected after a resignation is an autopsy. The same conversation held six months earlier is a diagnosis, held with someone who still has a reason to be candid and a reason to stay.
A stay interview is structured relationship work, and the structure matters as much as the warmth. It’s a short, recurring conversation about what keeps this person’s work worthwhile, what creates drag, whether they see a future here, and what might quietly be pulling them elsewhere. Run well, it surfaces the pay concern before the recruiter does, the stalled growth before the disengagement, and the broken process before it becomes a resignation letter’s second paragraph.
One warning before the questions, because it shapes everything after. Asking creates an obligation. A manager who collects honest answers and changes nothing teaches the team that speaking up produces paperwork, and that lesson outlasts any single departure. If there’s no capacity to follow through this quarter, skipping the conversation is the more honest move. This guide covers the questions organized by what they signal, the cadence, the prep prompts, and the follow-through that makes the whole thing worth running.
Key Takeaways
- A stay interview is the conversation an exit interview holds too late: you ask while the person is still deciding, not once they have already gone.
- Organize the questions by signal rather than by script: energy, friction, growth, and flight risk each surface a different thing you can act on.
- Set it up so it does not read as a warning. Say plainly that this is not a performance review, and run it on a cadence rather than after a scare.
- Listen for the red flags (vague answers, a shrug about the future, requests already asked for twice) and respond steadily instead of over-promising.
- The follow-through is the retention mechanism. Answer what you can change, name what you cannot, and come back with an outcome by a stated date.
Table of Contents
The Conversation Exit Interviews Have Too Late
By the time someone explains why they’re leaving, the explanation describes a closed case. The frustrations went unresolved, the growth stalled, the commitments slipped, and the interview records the outcome after the window to change it has shut. The exit interview questions guide covers how to run that conversation well, and it’s worth running. It’s also, by design, the version of this conversation that arrives after the decision.
Departing employees have less reason for complete candor too. Some are protecting a reference, some are avoiding conflict on the way out, and some have simply moved their attention to the next job. The answers may be honest, but the timing shapes what gets said, especially once nothing in the conversation can improve the person’s daily experience.
The stay interview moves the same questions to the moment when they can still change something. The employee can describe what makes the work worthwhile and what’s grinding them down. The manager can fix a misunderstanding, remove an obstacle, escalate the pay concern, or explain honestly why the promotion isn’t available yet. Any of those beats reading about the problem in an exit summary, and the research agrees. One field study found that employees who received at least one stay interview were significantly more likely to still be employed a year later than those who hadn’t. A single conversation doesn’t prevent turnover on its own, but the pattern supports treating this as a management tool rather than a feel-good ritual.
The case gets stronger for distributed teams, where the hallway signals that once warned a manager, the shorter answers and the camera that stays off, are easier to miss entirely. Remote-first teams working on reducing turnover lean on deliberate check-ins precisely because the informal ones disappeared, and the stay interview is the most deliberate check-in there is. The broader system it belongs to lives in the retention playbook; this piece is the conversation at the center of it.
Setting It Up Without Scaring Anyone
The phrase “I want to talk about your future here” can make a strong performer wonder if they’re being managed out, and a stay interview that triggers that thought has failed before it starts. The fix is framing that removes the ambiguity before the meeting exists. The calendar invite describes an ordinary conversation, something like “Experience check-in. What’s working, what’s creating friction, and what support would help.” Direct, boring on purpose, and nothing that reads like a retention intervention or a verdict.
The cadence
The workable baseline is an annual stay interview for everyone, with more frequent check-ins for higher-risk groups, and early versions at three and six months for new hires, when belonging and role clarity deserve their own attention. The format doesn’t need to be heavy. SHRM’s guidance lands on roughly thirty minutes and five core questions with a recap at the end, and a lighter quarterly rotation inside existing 1-on-1s covers the ground for most teams.
Two timing rules do real work. Keep the conversation at least six weeks away from performance review cycles, so nobody wonders whether candor will show up in their rating. And don’t schedule one right after a reorg announcement, mid-crisis, or in any week where follow-through has no chance, because the conversation creates the obligation whether or not the calendar cooperates.
The opening
Words at the top of the meeting, verbatim:
This isn’t a performance review. I want to understand what helps you do good work here, what gets in the way, and what would make the role stronger. Some things I can change, some I’d need to escalate, and some might not be possible. What I’ll commit to is being clear about what happens next.
Then ask permission to take notes, say who’ll see the themes, and don’t promise confidentiality the organization can’t guarantee. In a video call, behavior matters more than the setup. Pause after hard answers, don’t multitask, and let silence do its work. The conversation should feel like a continuation of good management rather than an HR event, and the habits underneath that live in how to be a good manager.
The Questions, Organized by Signal
A stay interview works when its questions reveal something the manager can act on, which is why the organizing principle is signal rather than script. Energy questions show what deserves more room. Friction questions expose avoidable drag. Growth questions test whether the person sees a future here, and flight-risk questions test whether somewhere else has started looking better. The same study behind the retention finding built a fourteen-question framework from 114 published examples, and it covers this same territory; a working manager needs four or five per conversation, sent a week ahead so the answers come with real examples attached.
| Signal | Ask | Then follow with | A red flag sounds like |
|---|---|---|---|
| Energy | What part of your work do you look forward to most? | What would let you do more of it? | “Nothing in particular. It’s mostly just work.” |
| Energy | When did you last feel genuinely excited about a project? | What was different about that one? | No specific example comes |
| Friction | What would you change about your day-to-day if you could? | What does that issue stop you from doing? | “The process is broken, but nobody changes it.” |
| Friction | Which meeting, tool, or approval creates the most drag? | What would a workable version look like? | Wasted effort plus ignored requests, repeatedly |
| Growth | What skill or experience do you want to build next? | What project would let you practice it? | “There’s no path for that here.” |
| Growth | Which of your strengths isn’t being used enough? | Where could it do the most good? | They stopped asking for development a while ago |
| Flight risk | What would it take for you to consider leaving? | Which part of that feels most immediate? | A specific opportunity, a pay grievance, or lost trust |
| Flight risk | What might make you want to build a career here long term? | What would need to change first? | The answer lists only things that never change here |
Three notes on reading the answers. Energy answers need sorting into workload problems and role-design problems, because a strength that’s consistently unused calls for different project allocation rather than a pep talk. Friction becomes actionable only through detail, since “culture” names nothing until you ask which meeting, decision, or behavior makes the word feel true, the same noun-chasing discipline the exit guide teaches. And flight-risk questions need the steadiest tone in the set. Ask, listen, and write the concern down without making a counteroffer in the room. If pay is the issue, it goes to the real process, because a stay interview can surface an unfair salary and can’t fix one.
The wrong-answer worry, for the record, mostly doesn’t materialize. Asking “what would it take for you to leave” doesn’t plant the idea; the idea was either there or it wasn’t, and the question just determines whether you find out first or the recruiter does.
Tailoring the Questions, and Letting AI Do the Prep
A generic questionnaire makes a stay interview feel like compliance, and the person across the table can always tell. The questions should fit where this specific person is in their run. A new hire needs belonging and clarity questions, a ten-year veteran needs renewal and challenge questions, and pushing the same five at both wastes the only conversation designed to be personal.
| Who | Probe for | A starter | Point the AI at |
|---|---|---|---|
| New hire | Belonging and clarity | What still feels unclear about how work gets done here? | Onboarding gaps, expectations, early relationships |
| Established contributor | Growth and autonomy | Where do you want more ownership? | Unused strengths, stalled development, decision bottlenecks |
| Long-tenured employee | Renewal and legacy | What part of your experience could help the team work better? | Signs of stagnation, institutional knowledge, next challenges |
| Remote contributor | Connection and visibility | Where does remote work make your job harder than it should be? | Communication load, access to context, recognition, isolation |
| People manager | Capacity and support | What would help you lead the team more effectively? | Leadership workload, staffing, coaching needs |
| High flight risk | What staying would take | What concern would make another offer attractive? | Unresolved commitments, trust changes, departure signals |
The prep itself is where AI earns a seat, with one rule before anything gets pasted anywhere. Strip what doesn’t belong in the tool, meaning pay details, health situations, and anything personally sensitive, unless your company has approved the workspace for it. The raw material is your existing 1-on-1 history, which is also the argument for keeping those notes structured in the first place, the way the 1-on-1 notes prompts set them up.
Per-person prep:
Review these 1-on-1 notes for recurring themes, unresolved commitments, changes in energy, and possible retention risks. Don't diagnose the person or guess at anything sensitive. Separate what they actually said from what I might be reading into it. Then draft five open-ended stay interview questions, each tied to a specific theme in the notes, with one neutral follow-up each. Flag any question that could sound evaluative or intrusive. Notes: [paste redacted notes]Team themes:
Here are redacted notes from my recent stay conversations across the team. Group the concerns into themes, count how often each appears, separate what I can fix from what needs escalation, and flag any theme that's grown since the last round. Keep it short enough for my own planning doc, and don't turn anyone into a risk score.Then check every generated question against the source notes, because the failure mode is polish without grounding. Which assistant does the checking-worthy draft depends on the material. Claude tends to surface more from long, messy note history, while ChatGPT drafts faster and more generically, the split the ChatGPT vs Claude comparison maps in detail. Either way the tool’s job ends where the conversation starts.
The Follow-Through Is the Retention Mechanism
Retention happens in the two weeks after the conversation, and a stay interview followed by silence is worse than none, because it converts honesty into paperwork in front of the person who risked it.
Capture commitments within a day, wherever your team already tracks work. The fields that matter are simple. What the employee said, in their words rather than your interpretation. The promised action. One owner, a status, and a review date. “Improve communication” won’t survive a review date, while “I’ll publish the decision log in the team channel after weekly planning” can be checked at the review date, which is the whole point of having one. The discipline is the same one an after-action review runs on its commitments, applied to a single relationship instead of a project.
Then, at the next 1-on-1, open with the commitment before the employee has to ask. “Last time you raised the approval delays. Here’s what I tried, and here’s what happened.” That sentence carries accountability even when the fix is incomplete, and it’s the behavior that separates managers whose teams keep talking from managers who get one honest conversation per person.
Some answers have to be no, and the honest no beats the vague yes every time. A pay adjustment may wait on a cycle, a role change on an open position, a tool swap on security review. Name the constraint, name what can happen instead, name who owns the next decision, and name when they’ll hear from you. People forgive a no with a date on it far more easily than a maybe that dissolves.
Red Flags, and the Steady Response
A few answer patterns deserve their own playbook, and all of them reward calm over reassurance.
- “Everything’s fine,” with no examples. Ask which part of the week felt easiest lately and which took the most effort. Still vague? Record it as limited signal rather than converting it into false confidence.
- Every growth question deflected. Ask what made development feel less realistic here. The answer is usually a story about the last time asking went nowhere, and the story is the actionable part.
- A recruiter comes up. Ask what about the opportunity caught their attention, then listen for which lever it names, scope, pay, flexibility, recognition, or trust. No panic, no instant counteroffer.
- The requests stopped. A high performer who quit asking for projects or resources concluded that asking changes nothing. Ask what they stopped requesting and what led them to stop.
- Pay, directly. Ask whether the concern is the amount, the fairness, or the transparency, then involve the people who actually own compensation. Surfacing the problem is the interview’s job, and fixing it belongs to the process built for that.
When something hard lands, the response is two sentences, verbatim:
Thank you for saying that clearly. I can’t promise the outcome today, but I’m not going to treat this as casual feedback, and I’ll tell you what happens next by Friday.
Acknowledge, hold the boundary, and only commit to what you’ll actually do. Managers who hold that line find the second stay interview gets more honest than the first, because the first one proved the channel works, the same current running through everything that actually motivates people.
Run them small, run them regularly, and let the follow-through do the retaining. The exit interview will still have its uses. The goal is needing it less.
Frequently Asked Questions
What is a stay interview?
A short, recurring conversation between a manager and a current employee about what makes their work worthwhile, what creates friction, and what might eventually pull them away. It’s the before-the-resignation counterpart to the exit interview, run while the answers can still change something, and it works only when the manager follows through on what they hear.
What are the best stay interview questions?
Organize by signal rather than script. For energy, ask what part of the work they look forward to most. For friction, ask what they’d change about their day-to-day. For growth, ask what skill they want to build next. For flight risk, ask calmly what it would take for them to consider leaving. Four or five questions sent a week ahead beat a fourteen-question checklist read aloud.
How often should managers run stay interviews?
Annually for everyone as the baseline, with a lighter quarterly version inside regular 1-on-1s, and early check-ins at three and six months for new hires. Keep the conversation at least six weeks away from performance reviews so candor never feels like it’s being graded, and don’t run one in a week where you have no capacity to follow through.
What’s the difference between a stay interview and an exit interview?
Timing, and everything timing changes. The exit interview collects reasons after the decision to leave, from someone with less incentive for full candor. The stay interview asks near-identical questions while the person still has reasons to be honest and reasons to stay, which turns the same information from an autopsy into something a manager can act on.
