The Keeper Conversation: Five Questions Before the Notice Lands
The two-week notice is a terrible messenger. By the time it lands, the decision is already made, the toolbox is already half-packed, and the line is already doing math on who covers the shift. The exit interview will produce a few useful sentences, but those sentences arrive after the cost. The cheaper conversation happens earlier, on the floor, before anyone has a reason to polish the truth.
That is the whole case for a stay check. Not a survey. Not a scheduled sit-down with a form and a rating scale. A short, repeatable conversation between a supervisor and an assembler who is worth keeping. It works best when it is normal, not dramatic.
The postmortem problem
Exit interviews are autopsies. They tell you what went wrong after the patient has left the building. A stay conversation is closer to a five-minute station check: you are looking for the loose bolt before it becomes a line-down event. The information is usually not hidden. It is sitting in plain sight, behind a question nobody asked.
Most supervisors do not skip this on purpose. They skip it because the shift is busy, because the assembler seems fine, because retention feels like an HR thing. But retention on an assembly line is built in small moments: whether the kit is right, whether the torque driver is where it should be, whether someone notices when a person has quietly stopped caring.
Keep it off the review table
If the conversation feels like a performance review, the assembler will tell you what you want to hear. So say plainly what it is: 'This is not your review. I am asking because I want to know what would keep you here.' Then keep it short. Ten or fifteen minutes near the bench is better than an hour in an office. A small notebook is fine. A clipboard with a form is not.
Pick a time when the line is not screaming. Right after a break, before the last push, or during a natural gap in the run. Do not do it while the person is holding a torque driver and watching a cycle count. The point is to listen, not to add a task.
Five questions worth asking
1. What part of your day do you wish you got more of?
This is not a personality quiz. It tells you where the assembler feels useful and where the work is draining. Maybe they want more troubleshooting, more setup, more cross-training, or less of a repetitive station that leaves their hands busy and their brain parked. Do not promise a new job on the spot. Write it down.
2. What is one thing on this line that makes your job harder than it needs to be?
Expect specifics: missing tools, bad kitting, unclear work instructions, a shadow board that hides the 10 mm socket, an air hose that fights back. This is the most actionable question on the list. It also tells you whether the assembler believes anyone will fix the friction or just ask about it.
3. When did you last feel like your work mattered to somebody here?
Recognition is not a pizza party. It is a supervisor saying, 'That changeover went clean because you caught the wrong bracket.' If the assembler cannot remember the last time, that is data. Do not rush to fix it in the moment. Ask what kind of acknowledgment actually lands.
4. What do you want to get better at in the next year?
Career growth on the line is not only a promotion ladder. It can be cross-training, lead-hand skills, print reading, quality checks, or becoming the person who can set up a cell without help. The answer tells you whether the assembler sees a future here or just a paycheck. Both answers are useful.
5. If a friend asked whether to take a job on this line, what would you tell them?
This is the temperature check. Listen for the pause. Listen for the 'it depends.' Listen for the honest version of what they would say after a beer. Do not argue with the answer. If they would hesitate, you just learned more than a satisfaction survey will ever tell you.
Listening without grading
This is the hard part. Supervisors are trained to solve, correct, and improve. A stay conversation asks you to do something else: receive. Do not defend the line. Do not say, 'Well, that is just how it is.' Do not turn the answer into a coaching moment. Ask a follow-up: 'What would better look like?' or 'Tell me more about that.'
Take notes, but keep them simple. Themes matter more than transcripts. If the assembler says something about a coworker, do not promise secrecy you cannot keep. If it is a safety issue, act like it is a safety issue. Otherwise, treat the conversation as a trust deposit, not a confession.
The two-week rule
A stay conversation without follow-through is just a nicer way to ignore someone. Within two weeks, do something visible. Pick one or two items, not ten. If it is a quick fix, fix it: a better light, a shadow board, a kit change, a tool within reach. If it needs money or another department, say so and give a date. Then report back.
'You said the kitting cart was missing fasteners. I talked to materials. Starting Monday, the kit has a labeled bin.' That sentence does more for retention than a stack of engagement posters. If you cannot fix it, explain why. An honest 'not yet' beats a silent maybe.
Make it a habit, not a program
Quarterly is enough for steady assemblers. New hires deserve a check at 30, 60, and 90 days, because that is when the doubt usually sets in. After a rough week, a five-minute version is fine. Keep a simple log of themes, not names. Bring the patterns to supervisor meetings. Share what changed at the shift huddle.
The best time to ask a good assembler what keeps them here is before the notice. The second best time is today. The exit interview can have the last word, but it should not be the first one.