Stay Interview Questions (Retention Strategy)
Stay interviews are structured, confidential conversations that help colleges and universities learn why employees stay and what might make them leave. Offer one to every eligible employee in a pilot group, ask the same core questions, explain confidentiality limits, and assign an owner and due date to every agreed action. Review results at 90 and 180 days.
A useful retention strategy does not wait for an exit interview. By then, an employee has already decided to leave. A stay interview gives faculty and staff a chance to describe what supports their work, what gets in the way, and what might cause them to look elsewhere.
The idea is simple, but the process must be credible. Employees need to know why the institution is asking, who may see their feedback, and what will happen next. In my work mapping workforce challenges to practical action, I have seen how easily a well-meant listening effort loses trust when leaders ask for candor but offer no clear follow-through. The questions matter; so does the response.
Stay Interviews in Higher Education: Purpose, Scope & Governance
A stay interview is a planned conversation with a current employee about the conditions that influence their decision to remain. In higher education, it can help leaders spot issues in workload, support, recognition, resources, or growth. It is a retention tool, not a performance review or promise of change.
There is no universal higher-education accreditation or regulatory body that prescribes a set of stay-interview questions. Institutions should align the process with HR policy, applicable labor agreements, privacy requirements, and relevant expectations from their accreditor about effective personnel and governance processes.
Set clear boundaries before inviting employees
Before a pilot begins, decide who is eligible and define the purpose in plain language. Work with HR and, as appropriate, employee representatives and institutional counsel to set rules for access to notes, record retention, escalation, and protection against retaliation.
Do not promise absolute confidentiality. Explain who may see identifiable notes and what concerns may need to be escalated, such as an immediate safety issue or a legally reportable matter. Make clear that participation is not a performance signal: track who takes part, but do not treat nonparticipation as poor performance or lack of commitment.
Stay interviews should not be used as disguised performance reviews, disciplinary investigations, or a way to secure promises about promotion, pay, or job security. If an employee raises a concern that belongs in another process, explain the appropriate next step rather than blending that process into the interview.
A practical pilot offers an interview to 100% of eligible employees in the selected group. That is a proposed coverage target, not a research-proven threshold. Report the participation rate separately so leaders can see whether the process is reaching employees without implying that people who decline are a problem.
Question Set, Interview Protocol & Follow-Up Requirements
A consistent interview protocol makes answers easier to compare and reduces the chance that managers lead employees toward a preferred response. Use the same five to seven open-ended core questions for each participant, then add optional follow-ups for the person’s role or work setting.
Ask questions that invite honest answers
The questions below cover common drivers of staying and leaving. Ask them in a calm, private setting, and give the employee time to answer. A neutral follow-up such as “Can you tell me more?” can help clarify a point without suggesting the answer you want.
- What do you look forward to most in your work here?
- What makes it harder than it needs to be to do your best work?
- What would make you consider leaving?
- Do you have the resources, authority, and support you need?
- Do you feel recognized and able to grow here?
- What is one change that would most improve your experience?
- Is there anything you want me to understand that I have not asked?
The questions are prompts, not a script to rush through. Listen for examples, patterns, and practical changes. Avoid asking employees to speculate about coworkers or share private details that are not needed to understand a work issue.
| Interview element | Proposed approach | Why it matters |
|---|---|---|
| Coverage | Offer an interview to every eligible employee in the pilot group | Makes the scope clear and avoids selecting only certain voices |
| Timing | One interview every 6–12 months; consider another after a major change | Creates a regular opportunity to check in |
| Length | 20–30 minutes | Allows focused discussion without turning it into a review |
| Core questions | Use the same 5–7 open-ended questions | Supports consistent listening across the pilot |
| Follow-up | Give every agreed action an owner and due date | Turns feedback into accountable work |
| Check-in | Review open actions within 30 days and report progress | Shows employees that the conversation led somewhere |
These are proposed operating parameters for a program, not universal research or accreditation thresholds. Adjust them to fit staffing, labor agreements, and the institution’s capacity to act.
Train interviewers and close the loop
Before interviews start, train managers to listen without arguing, ask neutral follow-ups, document themes carefully, and avoid retaliation. Explain how to respond when a request cannot be met. A useful answer is specific: state what can be done, who will decide, and when the employee can expect an update.
At the end of each interview, summarize what you heard and ask whether you understood it correctly. Agree on feasible next steps together. Assign 100% of agreed actions an owner and due date, then review open actions within 30 days and report progress to the employee. If no action is possible, explain why and what alternatives were considered.
Employee Experience, Support & Retention Actions
Employee feedback is useful only when it leads to a response. A retention action is a specific change, referral, or decision that addresses an issue raised in an interview. Some concerns can be handled by a manager; others require a unit leader, HR, or a broader institutional response.
Turn comments into workable actions
Separate themes from identifiable notes before sharing findings more widely. Keep the original records accessible only to people with a defined need and permission to see them. When reporting themes, avoid small-group results that could identify an employee, even if names are removed.
| What an employee may raise | Possible next step | What to avoid |
|---|---|---|
| Unclear priorities or too many competing tasks | Clarify priorities with the manager; review workload and deadlines | Treating the concern as a lack of effort |
| Missing tools or resources | Identify the resource, decision-maker, cost, and review date | Promising a purchase before approval |
| Limited growth or career support | Discuss available learning, mentoring, or role-development options | Suggesting a promotion is guaranteed |
| Feeling unrecognized | Ask what recognition feels meaningful and consistent | Assuming one form of praise works for everyone |
| A concern about safety or possible misconduct | Follow the institution’s escalation procedure and explain the next step | Keeping a promise of secrecy that cannot be honored |
A useful action has a clear owner, deadline, and status. For example, “review the workload distribution by the end of next month” is more useful than “improve workload.” Some actions may not be within a manager’s control. In that case, record the issue, send it to the appropriate decision-maker, and tell the employee when you will provide an update.
Use an implementation scenario, not a promise
Consider a hypothetical academic unit that hears repeated concerns about delays in getting basic work resources. The manager records the theme without attaching names to the summary, assigns an administrator to review the process, and sets a due date. Within 30 days, the manager tells employees what is known, what remains unresolved, and when the next update will come.
This is an example of a process, not evidence that a particular result will follow. It also shows why a stay interview should not collect feedback without a response plan. If the institution cannot act on every request, it can still acknowledge the concern, explain limits, and share progress.
Workforce Outcomes: Turnover, Career Growth & Institutional Effectiveness
Evaluation checks whether the interview process reaches employees, leads to action, and helps leaders understand workforce conditions. Set a baseline before rollout, then review participation, recurring themes, action completion, and voluntary turnover at 90 and 180 days. These review points are proposed program targets, not guaranteed measures of success.
Track a small, useful set of measures
A baseline gives leaders a point of comparison. Before the pilot, record the workforce measures the institution already tracks and confirm how they are defined. Compare results by unit and employee group only when reporting will not reveal individual identities.
| Measure | What to record | How to use it |
|---|---|---|
| Participation | Employees who took part compared with those offered an interview | Check whether the process is reaching the eligible group |
| Recurring themes | Common issues raised across interviews | Identify concerns that may need a unit or institution-wide response |
| Action completion | Agreed actions completed by their due dates | See whether commitments are being followed through |
| Voluntary turnover | Employees who leave by choice, using the institution’s established definition | Review workforce trends alongside interview themes |
| Employee updates | Whether employees received progress reports on open actions | Check whether communication continued after the interview |
At 90 days, review participation, open actions, and early themes. At 180 days, review those measures again and examine voluntary turnover by unit and employee group. Turnover data alone cannot show why people left or prove that interviews caused a change. Read it alongside employee feedback and other workforce information.
Leaders should look for patterns, not blame. A low participation rate may prompt a review of trust, scheduling, or how invitations were explained. Low action completion may point to unclear ownership or a lack of resources. Use the findings to revise the questions, training, or action process before expanding the program.
The central test is whether employees see a fair process: the institution listens, protects information within stated limits, responds to concerns, and reports progress. A successful interview is not one in which every request is granted. It is one in which the employee understands what happens next.
Frequently asked questions
How often should stay interviews happen?
A proposed schedule is one 20–30-minute interview every 6–12 months, with an additional interview after a major organizational change when appropriate.
Who should conduct the interview?
A trained manager or another appropriate institutional representative can lead it. Choose someone who can listen fairly and explain how concerns will be handled.
How many questions should I ask?
Use five to seven standard, open-ended questions. Add role-specific follow-ups only when they help clarify the employee’s experience.
Are stay interviews confidential?
Do not promise absolute confidentiality. Explain who may access notes, how records are retained, and which concerns may need to be escalated.
Should every eligible employee be invited?
For a pilot, offer an interview to 100% of employees in the selected group. Track participation separately and do not treat declining as a negative performance signal.
What should happen after an interview?
Summarize key points, agree on feasible actions, assign each action an owner and due date, review open actions within 30 days, and update the employee.
Can a stay interview replace a performance review?
No. It is a conversation about conditions that affect an employee’s decision to stay, not an assessment of performance or conduct.
What if the employee raises a safety or misconduct concern?
Follow the institution’s relevant escalation process. Be clear about the next step and do not promise secrecy when policy or law may require action.
How can leaders tell whether the program is helping?
Set a baseline, then review participation, recurring themes, action completion, and voluntary turnover at 90 and 180 days. Treat these as program measures, not proof of cause and effect.
Should leaders share interview findings with the whole institution?
Share aggregated themes and actions, not identifiable notes. Do not publish results from small groups when employees could be recognized.
A stay interview is a practical way to hear what employees value and what may push them away. Start with clear safeguards, use consistent questions, and act on what people share. Then review the evidence, improve the process, and keep employees informed.
(This article was written by one of our staff writers, James Holloway. Visit our Meet the Team page.)
