Use employee exit interview questions to capture a departing technician's reasons in their own words. Ask whether they're willing to have a structured conversation and keep its tone neutral. Use what they share to identify changes that could help the people still on your team.
What to Do the Day a Tech Hands in Their Notice
The day the notice lands, your job is to start the conversation, not to react. Ask if they're willing to talk about what led them here, and make clear it's their choice. If they say yes, block out 30 to 60 minutes, find a private room, and leave your defensiveness at the door.
Start with one open question: "What led you to start looking?" Then stop talking. Let them fill the silence. What you're after is their story, not your explanation for why things were the way they were.
If they're angry or scared, this may not work. Respect that. The conversation is optional, and I wouldn't push someone who has said no. If you suspect you're the reason they're leaving and you can't hear the feedback without getting defensive, ask a neutral third party to run the conversation instead. And if they've signed a severance agreement with confidentiality clauses, the conversation may be off-limits or limited by what they're allowed to say. Accept that and learn what you can from what they offer freely.
The Five Questions That Get the Real Reasons
Generic questions get generic answers. "Are you happy here?" gets "yeah, it's fine." What you want are questions that push toward specific moments and behaviors. These five are a starting point, not a validated instrument. Adapt them to your shop, but keep them open-ended.
- Tell me about the last week when you thought about quitting. What was happening?
- What part of your week did you dread the most?
- What did you hope this job would become that it didn't?
- Was there a moment you felt you couldn't do your best work? What caused it?
- If you were in my seat, what's the first thing you'd change?
Each question is designed to pull a concrete story, not a verdict. "Tell me about the last week" gets you a scene. "What part of your week did you dread" gets you a specific task or client. Write down what they say, word for word, because you'll need those exact words later.
Sorting What You Can Change From What You Can't
Once you have their words, the next step is sorting them into two buckets: what you can influence and what you can't. This is a prioritization aid, not a rule. External reasons like moving to another city are often out of your reach, but not always. Internal reasons like workload, tooling, or management are where you should spend your energy.
| Bucket | Example | Your move |
|---|---|---|
| Internal | "I'm burned out from after-hours calls." | Look at staffing, scope, or tooling to reduce the load. |
| Internal | "I never get to work on the stuff I'm good at." | Re-examine how you assign tickets or projects. |
| External | "I'm moving to another city." | Accept it. Wish them well. Learn what you can. |
| External | "I got an offer for more money." | Ask if it's the money or the whole package. Sometimes it's fixable, sometimes not. |
The trap is treating every complaint as a must-fix. If they're moving for a partner's job, no amount of process improvement changes that. Sort honestly, and don't let the external reasons distract you from the internal ones you can actually do something about.
Acting on the First Warning Sign
The exit conversation tells you what to watch for. My read is that the earliest warning sign is usually a change in behavior: showing up late, disengaging from tickets, skipping the standup, or being short with clients.
Say the departing tech mentioned workload. The next time you notice a current tech coming in late and letting tickets pile up, don't wait. Schedule a stay interview with them, a casual 20-minute check-in, and ask what their week looks like. Stay interviews are a complement to the exit conversation, not a guaranteed way to keep someone. They give you a way to look for problems early, while you can still do something about them.
Follow up on changes in engagement as well as direct complaints. Ask what has changed and what support would help, rather than assuming you know why someone has become quieter.
When the Problems Are Bigger Than One Tech
Sometimes the exit feedback points to something you can't fix in a week. Chronic understaffing, an outdated toolset, or a management style that's pushing people out. If the feedback is bigger than one tech, one conversation won't fix it. You may need to restructure the team, hire, or invest in better tools. If the issue is your own management, consider whether you need to delegate differently or bring in an outside consultant to help sort the priorities.
Your Monday Start: Turn One Fix Into a Habit
You've done the exit conversation, sorted the reasons, and spotted a warning sign. Now pick one fixable reason and turn it into a habit. Don't try to fix everything at once. My view is that one change, done consistently, is worth more than five changes you abandon by Friday.
If the reason was workload, schedule a stay interview with a current tech this week and ask about their biggest time-waster. If it was tooling, start the conversation about what they'd rather be using. The goal is to make the learning from this departure stick, so the next one doesn't come as a surprise.
Compare the exit feedback with what current staff have told you. Choose a specific issue to address, assign responsibility, and tell the team what will change.
mspoutpost.com/articles/employee-exit-interview-questions-for-msp-techs
Written by Megan Friesen
MSP Outpost publishes information, not legal, financial, insurance, tax or compliance advice, and reading it creates no professional relationship. For decisions about your business, talk to a qualified professional.
