Stay interview: 10 questions before an employee leaves

A stay interview is a conversation with a current employee about what supports their decision to stay and what makes their work difficult. Make it useful by asking open questions, agreeing on a realistic action and setting a date to review that action together.

A resignation can reveal a concern that a manager had never heard about. In a small business, there may be little time left to redistribute responsibilities or understand what happened. Listening earlier creates a chance to address everyday work while the employee is still there. The following ten questions and follow-up method help managers start that conversation without asking anyone to promise they will remain with the company.

What should a stay interview accomplish?

The purpose is to understand the employee’s experience of working in your organization. Discuss what helps, what gets in the way and what they would like to explore. Avoid using the conversation to assign a flight-risk label or collect information about applications to other employers.

The go2HR retention and engagement guide, first edition 2018, distinguishes conversations with current employees from exit interviews and stresses responding to suggestions. The University of Wisconsin–Madison HR question sheet also invites employees to reflect before the discussion. The questions and workflow below are original proposals for a small business, rather than reproductions of those resources.

Keep this meeting separate from a performance review. A review considers an employee’s contribution against agreed expectations. This conversation examines the conditions that support their work. Combining both purposes can make it harder for someone to describe a difficulty openly.

How can a manager prepare for an honest conversation?

Explain the purpose, proposed topics and expected length in advance. A thirty- to forty-minute appointment is one possible starting point, rather than a universal standard. Offer comparable opportunities across roles, locations and shifts. People who rarely work beside the owner should also have access to the conversation.

Set expectations about notes: their purpose, who may see them and what might need to be shared to address an issue. Avoid promising absolute confidentiality that you cannot provide. Let the employee decline a question. Do not automatically record the discussion or request unnecessary information about their private life.

The direct manager can lead when the relationship supports a candid exchange. If that relationship is part of the problem, provide an appropriate alternative contact through your internal practices. A stay interview is not a substitute for the processes used to address an urgent concern, a formal report or a matter requiring specialist support.

Review earlier commitments before writing a fresh agenda. An unanswered request may matter more than another round of questions. Know which changes you can approve, which require consultation and which fall outside your authority. That preparation helps you respond clearly without making a promise you may later have to withdraw.

Which ten questions can you ask a current employee?

Treat these questions as a menu. You do not have to cover all ten in one sitting. Invite a recent example, allow time for thought and use the stated purpose to choose a helpful follow-up.

1. Which recent experience made you want to keep doing your work here? Purpose: identify something specific worth protecting, rather than asking for a general rating of the employer.

2. Where in your working week does a task become harder than it needs to be? Purpose: locate friction in a particular process, handoff or schedule before selecting a solution.

3. Which expectation would you like clarified so you can make decisions with more confidence? Purpose: uncover unclear ownership or competing priorities that make ordinary decisions unnecessarily difficult.

4. What support is missing at the point when you need it? Purpose: understand access to people, information or equipment without assuming that the employee simply needs to try harder.

5. Which part of your contribution tends to go unnoticed? Purpose: identify less visible work and discuss how the employee would prefer that contribution to be acknowledged.

6. Which skill would you like more opportunity to use over the coming months? Purpose: explore development that could fit organizational needs without implying that a different job is available.

7. Which management commitment are you still waiting to see completed? Purpose: revisit a promise or an unclear decision, including one the manager may already consider settled.

8. What change in your work could lead you to reconsider whether this is the right place for you? Purpose: understand a condition that matters for the future without requiring disclosure of a job search.

9. Of the difficulties we have discussed, which should we examine first? Purpose: choose a priority together and avoid producing an action list that nobody has time to complete.

10. At our next conversation, what should we look for to judge whether anything has improved? Purpose: agree on observable evidence and make the review part of the original commitment.

Listen without immediately defending the current arrangement. Summarize what you understand and separate the experience described from facts that still need checking. Acknowledging a difficulty does not require approving a proposed solution during the meeting.

How do answers become practical commitments?

Close by summarizing one thing to preserve and one priority to address. Ask the employee whether that summary is accurate. Then distinguish between an action within your authority, a request requiring another decision-maker and a request you cannot accept. Each needs a clear response.

For an agreed action, identify the intended result, the person responsible, a review date and the evidence you will examine together. A review can take place before the issue is fully resolved. Use it to explain progress, dependencies or a delay instead of letting a deadline disappear without a response.

Consider a fictional example from a small service business in Trois-Rivières. A coordinator receives urgent assignments from two managers and does not know which one takes priority. Rather than announcing a broad engagement programme, her manager proposes a two-week trial: one designated person resolves conflicting priorities and confirms the decision in the usual work channel. They later review several actual situations. This example illustrates the proposed process; it claims no client result or improvement in retention.

If an issue affects the whole team, an approach to objectives and key results for SMBs can help define a shared improvement. Keep individual comments out of a team dashboard. Share the appropriate work action, rather than the employee’s personal account of the conversation.

How can M360 Compass support the next steps?

M360 Compass is a people management operating system for small and medium-sized businesses. RoleAlign connects roles, responsibilities and expectations. Those reference points can support a discussion about unclear ownership raised during an interview. Performance and individual development plans link feedback with skills and development priorities when an employee and manager agree on a learning action.

Momentum connects issues, decisions, responsibilities and deadlines. It can support follow-up on an operational improvement selected by management. These capabilities do not mean that every confidence belongs in a shared workspace or that the platform predicts who will resign. Decide what information is needed and who should access it before documenting the next steps.

Start by reviewing commitments kept and whether the change was useful to the employee. The employee turnover rate offers a separate organizational measure. A change in that rate alone does not establish that interviews caused the result. Keep the context, the management action and the broader indicator distinct when reporting progress.

Common questions before your first conversation

How often should we hold these interviews?

Choose a rhythm your managers can sustain and reconsider it after a significant workplace change. Follow-up on an agreed action should reflect its review date, rather than waiting for the next organization-wide interview cycle.

Who should lead the meeting?

The manager can lead where the relationship allows an honest discussion. Offer another appropriate contact when that relationship is itself an obstacle, and explain how any next steps will be coordinated.

What if the employee says very little?

Allow time, share topics in advance and offer an opportunity to respond later. Silence is not evidence of disengagement. Your response to earlier conversations may also influence how comfortable someone feels speaking now.

Do we have to agree to every request?

No. Listening calls for a clear response, not automatic approval. Explain the decision, practical constraints and available options, then confirm what you will review and when.

Begin with one conversation and a commitment you can keep. To connect responsibilities, development and management actions, request a M360 Compass demonstration.