A stay conversation is easy when the employee's concern is a schedule or a tool. It becomes delicate when the concern is the manager, because the person running the conversation may be the manager or may report to them. Handled badly, the conversation confirms the employee's fear that speaking up is unsafe. Handled well, it produces a specific, testable change without turning the employee into a witness in an investigation.
Published November 3, 2026
Decide who should hold the conversation
The default is the employee's manager, but that default should be reconsidered when the concern is about the manager. A skip-level conversation, a conversation with a neutral people partner, or a facilitated conversation with both parties can each be appropriate. The choice depends on the severity of the concern, the employee's preference, and whether the manager can hear the feedback without retaliating. Document the reason for the choice so the process is consistent rather than ad hoc.
If the employee asks to speak with someone else, take the request seriously. A refusal to offer an alternative can end the conversation before it starts and may create a legal risk if the concern involves harassment or discrimination. The alternative does not have to be elaborate; a trained people partner or a manager one level up is often enough. What matters is that the employee has a credible path to be heard.
Set the boundary before the conversation
Tell the employee what will be shared, with whom, and for what purpose. If the conversation is confidential except for a summary to the manager, say so plainly. If the concern may trigger a formal process, explain that before the employee speaks. Surprising someone with a process change after they have been vulnerable damages trust and makes future conversations less likely.
The boundary also protects the manager. A conversation that produces a list of complaints without context is hard to act on and easy to dismiss. Agree in advance that the output will be a small number of observed behaviors and requested changes, not a verdict on the manager's character. That framing keeps the discussion specific and gives the manager something to work with.
Ask for observed behavior, not personality
The most useful question is what the manager does or does not do that makes the employee's work harder. "My manager is dismissive" is a conclusion, while "when I raise a scheduling conflict in the team meeting, the manager moves on without acknowledging it" is an observation. The second version can be addressed; the first usually produces defensiveness and no change. Guide the employee toward examples with a time, a setting, and a specific action.
Ask how often the behavior happens and what the employee has already tried. A single bad week is different from a pattern that has lasted months, and an employee who has already raised the issue informally may be more frustrated than one who has not. Record the pattern and the attempts without judgment. The goal is a description the manager can verify, not a case the employee has to win.
Separate the person from the practice
Many manager problems are actually practice problems. A manager who cancels one-on-ones may be overloaded, not indifferent. A manager who gives vague feedback may never have been taught how to give specific feedback. The conversation should explore whether the issue is a skill gap, a workload gap, or a genuine unwillingness to change. Each requires a different response, and treating all three as a character flaw guarantees that none is fixed.
This distinction also affects what the employee is asked to do. If the manager is overloaded, the fix may be structural, such as reducing the manager's span of control or protecting a standing meeting. If the manager lacks a skill, the fix may be coaching. If the manager is unwilling, the fix may be a performance process. The employee should not be asked to diagnose which one applies, but the person handling the conversation should.
Give the manager a usable summary
The manager should receive a short summary that names the observed behavior, the impact, and the requested change. Avoid attributing motives and avoid quoting the employee in a way that makes them identifiable if they asked for confidentiality. The summary should also state what the manager is expected to do and by when. A vague note that says the team has concerns is worse than no note, because it invites defensiveness without giving direction.
Where possible, let the employee review the summary before it is shared. This check catches misstatements and gives the employee a sense of control over how their concern is represented. If the employee objects to a detail, discuss the objection rather than overruling it silently. The review step takes time, but it prevents the summary itself from becoming a new source of distrust.
Follow up with both parties
Follow-up should happen on a defined date, not when someone remembers. Ask the employee whether the agreed change has occurred and ask the manager what has been difficult about making it. Compare the two answers and record the difference. A gap between intention and practice is normal, but an unexamined gap becomes evidence that the conversation was theater.
If the behavior continues after a reasonable period, escalate according to policy. Do not ask the employee to keep re-reporting the same issue to the same manager. The escalation path should be known in advance and should not depend on the employee's willingness to push. A clear path protects the employee and gives the manager a fair warning that the issue is now a performance matter.
Protect against retaliation
Retaliation is the risk that makes manager concerns so difficult. Watch for changes in schedule, assignments, evaluations, or access that follow the conversation. Ask the employee directly whether they have experienced any change they believe is connected, and take the answer seriously even if it is hard to prove. Document the timeline so a pattern can be assessed rather than debated.
Managers should be told explicitly that retaliation is prohibited and that the conversation is part of normal retention work. That instruction is not a accusation; it is a boundary that makes the process safe for everyone. If retaliation is alleged, route it through the formal complaint process rather than handling it as a coaching issue. The retention conversation and the complaint process are separate, and confusing them helps no one.
Learn from the pattern
Review manager-related stay conversations together every quarter. If one manager appears repeatedly, the issue is likely systemic and should be addressed through coaching, workload, or a formal process. If concerns cluster around a practice such as scheduling or feedback, the organization can fix the practice rather than waiting for each employee to raise it. Aggregated patterns turn individual courage into organizational learning.
Keep the records minimal and access-controlled. The purpose is to improve retention, not to build a file on any employee or manager. A short summary of the concern, the agreed action, and the outcome is enough. The organization that can show it acted on a difficult concern is more credible than one that promises an open door and never walks through it.