A stay interview is a conversation with someone who still works for you about what makes the job worth staying in and what could push them away. For a trades leader, the useful result is a specific change you can act on, with the employee helping define whether it worked.
You do not need to wait for a resignation to ask how the work feels from the other side. Set aside time with a technician, dispatcher, counter specialist, or crew leader. Ask about the actual week they just worked. Then listen long enough to understand the answer.
The questions below are a Blue Collar Smart editorial conversation guide. They are not a formal assessment or a guarantee that an employee will stay. The trades scenarios are illustrative, not Hugh's client stories.
Make room for an honest answer
Explain the purpose before the meeting: you want to understand what makes the role work for this person and what needs attention. Keep it separate from a performance review. Schedule enough uninterrupted time to explore an answer rather than rushing through a checklist between calls.
Choose a place where the employee can speak without the rest of the crew listening. Arrange coverage when their role requires it. Asking a dispatcher for undivided attention while the phone keeps ringing tells them which priority really wins.
Do not make the conversation a test of loyalty. Someone may value the work and still have concerns about hours, pay, supervision, or their future. You need those concerns described accurately before you can decide what to do.
Richard Finnegan's SHRM guidance on stay interviews emphasizes listening, probing for detail, taking notes, and avoiding defensiveness. Use those practices throughout. A polished list of questions will not help if every answer turns into your explanation of why things cannot change.
Six stay interview questions for trades leaders
Start with one or two questions that fit the employee's role. Follow the answer before moving to the next topic. These prompts are written for this article, rather than copied from a questionnaire.
1. Which part of a recent workday made you feel this job was a good fit?
Ask for a particular moment. Was it solving a difficult service problem, helping a contractor find the right part, training a newer colleague, or finishing a job without being rushed?
The answer tells you what is worth protecting. If a technician values diagnosis but spends most days correcting incomplete job information, you have a more useful starting point than a general discussion about morale.
Do not assume everyone wants the same reward. One person may want broader responsibility. Another may want to keep doing skilled work with a dependable schedule. Ask what matters to the person in front of you.
2. Where did the work become harder than it needed to be this week?
Keep the discussion close to a real example. Ask where the difficulty began, what the employee had to do around it, and whether it keeps happening.
Imagine a counter specialist who describes repeated stock discrepancies. The issue may be the information they receive before promising a pickup, rather than their ability to handle an unhappy customer. Explore the sequence before suggesting another customer-service course.
Separate an occasional inconvenience from a recurring obstacle. Ask which problem they would fix first and why. Their priority may differ from the one you would choose from the office.
3. How is the schedule affecting your ability to keep doing this job?
Give the person room to discuss predictability, overtime, travel, and recovery between demanding days. Avoid treating every scheduling concern as unwillingness to work hard.
For example, a service technician may accept an on-call rotation but struggle when its dates change at short notice. A warehouse colleague may want clearer notice of peak-period overtime. Those are different problems and require different decisions.
Ask what a workable arrangement would look like. You may not be able to grant it, but you can understand the request, check the available options, and give a clear answer.
4. What capability would you like to build, and what is blocking it?
Invite a concrete skill or responsibility. It might be diagnosing a different equipment type, handling a customer account, planning a crew's day, or improving inventory accuracy.
Then ask about access to practice. A training plan is incomplete if nobody can release the employee from their regular workload or supervise the next step.
In Hugh's conversation with Eric Himes about people-first business culture, Himes describes giving people ownership as they demonstrate their ability to solve problems. The editorial application here is to connect an employee's development interest with a real opportunity to practice. Do not promise a promotion to keep the conversation comfortable.
5. What would make another job more attractive than this one?
Ask calmly, without demanding details about applications or other employers. Let the employee choose how much to share.
They may mention compensation, steadier hours, different supervision, better equipment, or a clearer path forward. Do not dismiss pay because you hoped the answer would be culture. Do not assume a pay adjustment would resolve an issue about how someone is treated.
Explore the concern on its own terms. Ask whether it is something they have raised before and what response they received. If you need to review an option, explain who will review it and when you will return with an answer.
6. What should I change in how I support your work?
Make yourself part of the discussion. Ask where your priorities, availability, or decisions create unnecessary difficulty.
A crew leader might say that you change the plan directly with individual crew members and leave her to reconcile it afterward. The immediate work is to understand that pattern, not explain how busy the business has become.
Check your understanding before responding: describe the concern in your own words and ask what you missed. If feedback is difficult to hear, pause. The employee should not have to reassure you before the meeting can continue.
Put it to work
From a concern to a useful change
Use this sequence for the one issue you agree to address.
- 01
Hear the concern
Ask for a recent example. Check that you understood it.
- 02
Decide the next step
Agree on an action or identify the decision you need.
- 03
Name an owner and date
Make responsibility and the next update clear.
- 04
Check with the employee
Did it happen? Did it help their work?
Turn the conversation into one useful decision
Before finishing, choose one concern that matters to the employee. It may call for an immediate adjustment, a decision from another person, or a longer review. Be clear about which it is.
The University of California's stay-interview resource encourages managers to agree on areas for improvement, keep track of actions, and follow up. For a small trades team, a short working note can make that practical:
- Concern: What did the employee describe? Use a specific example.
- Next step: What will you do, or what decision will you seek?
- Owner and date: Who is responsible, and when will the employee hear back?
- Useful result: What would improve in their actual work?
Suppose the concern is changing on-call dates. Your next step could be to review how the rotation is approved and confirm the following month's dates by an agreed deadline. That is a bounded action. “We will improve work-life balance” leaves the decision undefined.
If you cannot make a requested change, say so and explain the constraint. Explore other options without pretending they are equivalent. An honest answer gives the employee more information than an open-ended promise.
If the conversation reveals a promise you already missed, start there. Our article on building trust in a team explores how to communicate and repair that commitment.
Check the change with the person who raised it
At the follow-up, ask whether the agreed action happened and whether it addressed the concern. If the schedule was published earlier, did it actually stay stable? If training time was approved, did the employee get to use it?
Record unresolved decisions as well as completed actions. Across several conversations, look for repeated obstacles that deserve a team-level response. Keep personal circumstances out of that shared discussion.
A completed meeting is an activity. A useful change in someone's work is the result you can review now. Whether retention improves needs longer observation and cannot be attributed to one conversation alone.
This week, invite one employee to a stay interview. Choose someone whose perspective you have not heard recently. Ask what would make their work worth staying in, agree on one next step, and put the follow-up on your calendar before you leave the conversation.