TranskribatorTranskribator
Stay interviews: how to find out what helps an employee stay and grow
Conversation with an employee

Stay interviews: how to find out what helps an employee stay and grow

How to hold a stay interview with a current employee: create a safe setting, discuss what works and what is difficult, agree on a feasible action and check the result.

The Transkribator team5-minute read
SOURCESTAY INTERVIEWEmployee experienceWhat helps and hindersA feasible changeAn honest limitFROM WORDS TO RESULTS
Working with a real recordingIllustrated training exampleTemplate to copy
Conversation with an employee

The value of the conversation depends on what happens next

A broad question like “Are you happy with everything?” often gets a broad answer. An employee may find it easier to describe a recent moment when work went particularly well or a situation that drained their energy. These examples reveal working conditions such as clear priorities, access to a decision-maker, the speed of feedback or how work is distributed.

The conversation comes with no guarantee that the company can meet every request. The interviewer should be clear about what they can change themselves, what needs approval and what is out of reach for now. If someone fears repercussions for speaking frankly, a polished list of questions alone will do little to build trust.

Workflow

Discuss the experience and end with a specific agreement

  1. Explain the purpose and the boundaries

    Explain that the conversation is about working conditions and development. Make clear that it won't be used as a covert assessment. Say how you will use the notes and which topics the employee can skip. If you plan to record the conversation, agree on this in advance and follow your organisation’s retention rules.

  2. Start with recent events

    Ask when, in the past few weeks, the employee felt their work was making a difference and when they ran into an unnecessary obstacle. Ask about the task, who was involved and what happened as a result. Hear the employee out and check that you understood the example and their expectations before responding.

  3. Distinguish requests from underlying needs

    “I want fewer meetings” could mean a need for time to tackle a complex task, for a clear agenda or for permission to decline an optional call. Ask follow-up questions to find out what the person means. Keep their account faithful to what they said, even if it is uncomfortable for the manager.

  4. Choose an action and follow up

    Agree on a small change, who's responsible and when you will review it. If other people need to sign off, say when you will seek their approval. If something is out of reach, explain why and avoid implying that it will happen. In the next meeting, ask whether the specific experience has changed, as well as how the employee feels.

Worked example

A fictional conversation about repeated approvals

This is a fictional training example. The names, circumstances and outcomes are included solely to explain the method.

Excerpt from a training recording · 12:40
I enjoy tackling difficult cases, but it wears me out when I have to explain the same decision to different people in three meetings.

This identifies both a positive factor, the challenging cases, and a barrier, the repeated approvals. Before cancelling any meetings, check whether they have different owners and purposes.

One testable action would be to log repeated decisions for two weeks and try using one short decision record for everyone concerned. The employee and manager can then compare how many times the same decisions came up. This example is entirely fictional.

Employee experienceWhat helps andwhat hindersA feasiblechangeAn honest limit
A stay interview identifies what helps, what gets in the way and what can realistically change.
SignalFollow-up questionPossible action
“Too many meetings”What exactly is repeated?One decision record
“No development”What experience do you need?A trial assignment with support
“Too little clarity”Where does the priority change?A rule for recording decisions
“Everything’s fine”When did work go especially well?Keep the conditions that work
Ready-to-use template

Stay interview guide and action agreement

Record only what is needed. Keep promises, limits and matters requiring approval in separate fields.

Template for your workSelect and copy
Purpose and ground rules:
What the employee wants to keep about the job:
A recent positive experience:
A recent obstacle:
What the employee expected:
What the manager can influence:
What requires approval:
One feasible action:
Owner and deadline:
How we will know things have improved:
Follow-up date:
Check the result

Check that the conversation leads somewhere

  • The employee understood the purpose and how the notes would be used.
  • The discussion included at least one specific example alongside general assessments.
  • The agreed action is within reach of those responsible.
  • Both sides have a date for reviewing the outcome.
ExperienceWhat supports the workExampleSpecific conditionsActionOwner and deadlineFollow-upCheck the change
The conversation matters when people come back to see whether the agreement worked.
Frequently asked questions

A closer look

How often should you hold stay interviews?

It depends on the team, how quickly things change and the other ways people give feedback. Following through matters more than establishing a frequency. Stay interviews complement day-to-day management.

Does HR have to conduct the interview?

The line manager is often a good choice if there is trust and they have the authority to act. Sensitive topics may require another safe channel.

Keep working with the recording