The Stay Interview: Keeping Them Before They Leave

Why this matters

By the time a good tech hands you a resignation, the decision is already made. The exit interview tells you why someone left after it is too late to do anything about it. A stay interview flips the timing: a short, honest conversation with the people you want to keep, while they are still on the truck and still fixable. Replacing a trained tech costs you months of ramp-up and a hit to your schedule. Holding onto one costs you twenty minutes a quarter.

What a stay interview actually is

A stay interview is a one-on-one where you ask a current employee what keeps them here, what frustrates them, and what would make them look elsewhere. It is not a performance review (you are not grading them) and it is not a complaint session (you are not promising to fix everything). You are gathering intelligence on flight risk before it becomes a resignation.

Run them with your A-players and your steady B-players. Run them with the quiet ones especially, because the quiet ones are the ones who leave without warning. Do them every quarter, or at minimum twice a year. Fifteen to twenty-five minutes is plenty.

The questions that actually work

Ask open questions and then shut up. The goal is to get them talking, not to defend the shop.

• What do you look forward to when you come to work? What makes you dread it?
• If you woke up and decided to job-hunt, what would push you out the door?
• What is one thing about how we run jobs that drives you nuts?
• When did you last feel jerked around or taken for granted here?
• What are you not getting from this job that you want? More hours, fewer, different work, a path up?
• If you ran this shop for a day, what would you change first?

Follow every answer with "tell me more about that" before you move on. The first answer is the polite one. The second answer is the real one.

How to listen without getting defensive

The fastest way to kill a stay interview is to argue. When a tech says "the schedule is a mess and I never know if I'm getting home for dinner," your job is to write it down, not to explain why the schedule is hard. Defending yourself teaches them to stop being honest with you.

Take notes in front of them. It signals you are taking it seriously. Repeat back what you heard: "So the unpredictable end times are the biggest thing. Did I get that right?" Then stop talking and let them confirm or correct.

You will hear things that sting. Sit with it. A tech who tells you the truth to your face is a tech who still cares enough to try.

Closing the loop is the whole game

A stay interview with no follow-through is worse than none at all, because now they have told you their frustrations and watched nothing change. That teaches them the conversation was theater.

Sort what you hear into three buckets:

• Fix fast. Small, cheap, do-it-this-week items. A broken truck radio, a parts-ordering bottleneck, a recurring scheduling snag. Knock these out and tell them you did.
• Work on it. Bigger items that take time: pay structure, a path to lead tech, better tools. Be honest about the timeline and check back in.
• Can't or won't. Some requests you cannot grant. Say so plainly and explain why. "I can't promise you'll never work a Saturday, but I can promise to give you the schedule two weeks out." Honesty beats a vague maybe.

Within a week, follow up on at least one item. That single act of follow-through does more for retention than the entire conversation.

Reading the warning signs between interviews

Stay interviews are a scheduled check. Pay attention to the unscheduled signals too. A normally chatty tech going quiet. Someone who stops volunteering for overtime they used to grab. New disinterest in training or new equipment. Taking personal calls out at the truck more often. A sudden uptick in "appointments" during the day.

None of these prove anything alone. Together they mean it is time for an unscheduled stay conversation, this week, not next quarter.

What to do with what you learn

Look for patterns across the whole crew. If three techs independently name the same frustration, that is not a personality issue, that is a process problem you own. One person's gripe is feedback. Three people's gripe is a priority.

Keep a simple running note per person of what they said and what you did about it. Next quarter, open with "last time you mentioned the parts delays, here is what changed." That continuity is what tells a good tech this place is worth staying at.

References

• Society for Human Resource Management (SHRM), guidance on retention and stay interviews
• U.S. Small Business Administration (SBA), resources on hiring and retaining employees
• See related: Paying for Performance Without Gaming It
• See related: The Tech Who Wants a Raise: Decision Tree