Turnover is often described as sudden.
An employee submits a resignation, the manager is surprised, and everyone begins asking what happened. The departure may be explained as a better salary, a new opportunity, a career change, or something personal.
Sometimes those explanations are accurate. But the final resignation rarely tells the whole story.
In many cases, the decision to leave developed gradually. There were signals: frustration that was mentioned but not explored, a change in participation, growing silence, reduced energy, questions about advancement, or a concern that never received a meaningful response.
The departure may feel sudden to the organization because the organization noticed only the final event.
Retention begins much earlier.
It depends on whether managers maintain enough connection with employees to notice when something changes, understand what is underneath it, and respond while there is still something to influence.
Turnover is rarely a sudden strike
One of the most persistent workplace myths is that employees simply quit out of nowhere.
The research presented in The Vital Pulse of Retention challenges that assumption. Fifty-two percent of departing employees said their manager or organization could have done something to prevent them from leaving.
At the same time, only about one-third of former employees had spoken with their manager about leaving before they resigned.
That gap is important.
It suggests that many employees believed improvement was possible, but the relevant conversation either never happened or happened too late.
This does not mean every resignation is preventable. Employees leave for many reasons, and organizations cannot remove every source of dissatisfaction or compete with every opportunity.
But preventability does not require perfect control. It begins with the ability to detect a problem before the employee has mentally finished making the decision.
The signal may have been present. The organization simply was not listening closely enough to recognize it.
The silent quarter
There is often a period between the employee’s first serious concern and the final departure.
The deck describes this as the silent quarter: a missed diagnostic window in which the employee is still present, still working, and still potentially reachable, but is gradually detaching.
During that period:
- An employee may speak with a coworker about wanting to leave.
- They may begin searching or applying for another position.
- They may quietly compare their current experience with other possibilities.
- They may continue working while becoming less emotionally invested.
From the outside, the employee may still appear functional. They attend meetings, complete assignments, and answer messages.
That is why disengagement is easy to miss when managers look only for obvious performance problems.
The early signs are often relational rather than dramatic.
The employee stops volunteering ideas. Their questions become more cautious. They participate less. They no longer raise concerns because they have decided nothing will change. They become compliant but less connected.
By the time performance declines visibly, the decision to leave may already be advanced.
Annual surveys cannot detect a changing pulse
Many organizations rely heavily on annual or semiannual engagement surveys.
These surveys can identify broad patterns. They can reveal recurring concerns across departments, locations, or employee groups. They can help leadership measure changes over time.
But they are not designed to detect what is happening with one employee this week.
The deck compares an annual survey to an occasional sweep. Long gaps exist between data points, and concerns can grow unnoticed in those gaps.
A yearly survey may tell leaders that employees want more development, clearer communication, or better recognition. It cannot tell a manager that a specific employee has recently become overwhelmed, disappointed, or uncertain about their future.
Retention requires a more continuous pulse.
That does not mean asking employees every day whether they plan to quit. It means creating a pattern of regular conversation in which employees can discuss workload, priorities, progress, frustration, goals, and support before those issues harden into a departure decision.
The frequency matters because work changes quickly.
A manageable workload can become unreasonable after one vacancy. A strong employee can become discouraged after being overlooked for an opportunity. A small conflict can grow when no one addresses it. A person who felt connected three months ago may no longer feel the same way today.
An annual survey cannot capture that movement in time.
A manager can.
Listening is not passive
Organizations often encourage leaders to listen more. That advice is correct but incomplete.
Listening is useful only when it helps the manager understand what is happening and decide what to do next.
The deck frames listening as an active intervention. Employees whose managers consistently listen to work-related concerns may experience substantially lower burnout risk.
The mechanism is practical.
When a manager listens carefully, the conversation can reduce uncertainty. The employee does not have to carry the entire problem alone or guess whether anyone sees it. Details that may have been unclear become visible. The manager can separate a temporary frustration from a deeper pattern.
Useful listening sounds less like:
“I understand. Let me know if you need anything.”
And more like:
“What part of this is creating the most difficulty?”
“What have you already tried?”
“What would make the situation more manageable?”
“Which part can I influence?”
“What do you need from me next?”
This is not therapy, and it does not require a manager to solve every personal or organizational problem.
It requires attention, curiosity, and follow-through.
The employee needs evidence that the conversation changed something, even if the change is greater clarity rather than an immediate solution.
The administrative manager and the connected manager
Not all manager contact creates connection.
An employee may speak with their manager frequently while discussing only schedules, deadlines, compliance, and output. That relationship may be operationally active but developmentally empty.
The deck distinguishes between the administrative manager and the connected manager.
The administrative manager communicates policy, tracks work, monitors output, and expects compliance. Those responsibilities are legitimate. Managers do need to clarify expectations and ensure work is completed.
The problem begins when management stops there.
The connected manager also considers how work is experienced by the individual employee.
Instead of simply communicating a flexibility policy, the manager looks for a practical solution within the limits of the role.
Instead of tracking the total workload, the manager helps the employee sort, prioritize, and organize it.
Instead of relying only on formal recognition programs, the manager notices meaningful contributions and acknowledges them in ways that matter to that person.
This is not about abandoning standards or creating a different rule for every employee.
It is about recognizing that consistency and sameness are not identical.
Two employees may have the same expectations but need different forms of guidance. One may need help organizing competing priorities. Another may need greater autonomy. One may value visible recognition. Another may value access to a new project or a chance to build a skill.
The connected manager learns enough about each employee to make support useful rather than generic.
Empathy must become operational
Empathy is often discussed as a leadership quality, but empathy alone does not change working conditions.
A manager can understand that an employee is overwhelmed and still leave the workload untouched.
A manager can recognize that someone feels overlooked and still provide no development path.
A manager can express concern and then return to business as usual.
The deck translates empathy into three operational steps:
1. Capture
First, create enough space for the employee to explain the situation.
The manager listens without immediately defending the organization, correcting the employee, or rushing toward a solution. The goal is to understand what the person is experiencing and what specifically is creating the problem.
2. Prioritize
Next, organize the issue.
What is urgent? What can wait? Which responsibilities are essential? Which ones have accumulated without anyone reconsidering them? What can be delegated, delayed, simplified, or clarified?
Employees sometimes need support not because they cannot perform the work, but because too many demands have been treated as equally important.
Helping someone prioritize is a retention action because it converts a vague sense of overload into a manageable plan.
3. Empower
Finally, give the employee appropriate authority, resources, or flexibility to act.
This may involve changing ownership of a task, adjusting a process, creating a clearer decision boundary, connecting the employee with training, or allowing them to approach the work differently.
Empowerment is where listening becomes credible.
Without action, repeated listening can become another source of frustration. Employees learn that they are allowed to speak but that speaking changes nothing.
Career stagnation creates a silo effect
Employees do not always leave because the current job is unbearable.
Sometimes they leave because they cannot see a future inside the organization.
The deck identifies lack of career opportunity as a major reason employees look elsewhere. When managers do not discuss development, employees often search for guidance through informal channels: coworkers, mentors, professional communities, recruiters, or external opportunities.
That creates what the deck calls a silo effect.
The employee’s career thinking develops separately from the organization. Their manager may know what tasks they are completing but have little idea what the employee wants to learn, where they hope to go, or what strengths they want to use more often.
Eventually, the employee finds somewhere else to pursue that growth.
Organizations sometimes respond by saying the person never expressed interest.
But employees may not raise development goals when previous conversations have focused exclusively on immediate output or when advancement seems limited to a traditional promotion.
Career development does not always require a new title.
It may include:
- Learning a new system
- Leading part of a project
- Mentoring another employee
- Participating in a cross-functional assignment
- Building expertise in a specialized area
- Presenting work to leadership
- Receiving coaching in a skill that supports a future role
The manager’s responsibility is not to promise a promotion that may not exist.
It is to help the employee see a credible path forward using the opportunities that are available.
The coaching mandate
Managers are often encouraged to coach employees, but the term can become vague.
In retention work, coaching means helping employees connect current responsibilities with future growth.
A useful development conversation explores:
- What the employee wants to become better at
- Which parts of the job give them energy
- Which responsibilities feel repetitive or underused
- What strengths others may not yet see
- What experience would prepare them for the next step
- What obstacles are slowing their progress
This does not need to be a formal annual career discussion.
In fact, the conversation is more useful when it happens regularly and evolves with the employee’s interests and the organization’s needs.
The deck emphasizes that managers should help co-create an inspiring path forward rather than waiting for a crisis, resignation, or formal development cycle.
That path should be realistic. Empty promises damage trust faster than limited opportunities honestly explained.
But realistic does not mean passive.
Even when advancement is not immediately available, a manager can help an employee build capability, visibility, and experience.
Retention cannot be solved by pay and policy alone
Compensation matters. Benefits matter. Flexibility matters. Clear policies matter.
But they do not replace the daily relationship between an employee and the person managing their work.
An organization may offer competitive pay and still lose employees who feel invisible, stagnant, overloaded, or disconnected.
It may create a strong retention policy while managers remain too busy to hold meaningful conversations.
It may invest in recognition software while employees receive little personal acknowledgment.
The deck’s final argument is that retention depends on the daily pulse of management:
- Regular interaction
- Careful listening
- Useful prioritization
- Recognition that feels specific
- Support that becomes action
- Development connected to the employee’s strengths and goals
HR can provide structures, tools, training, data, and policy.
But HR cannot conduct every conversation where retention is either strengthened or weakened.
That work happens on the front line.
The cost of missing the signal
When an experienced employee leaves, the organization loses more than one position.
It may lose institutional knowledge, reliable performance, customer relationships, internal trust, team continuity, and the informal knowledge that is rarely captured in a procedure.
The effect does not end when the vacancy is posted.
Remaining employees absorb additional work. They may question why the person left. They watch how leadership responds. If departures continue, they begin reconsidering their own future.
Turnover can become contagious because every resignation changes the experience of those who stay.
This is why retention should not begin when someone announces they are leaving.
It begins with a manager noticing that the pulse has changed.
Retention is built in ordinary conversations
There is no single conversation that guarantees an employee will stay.
Retention is built through a pattern.
It is built when managers ask useful questions before problems become crises. It is built when concerns lead to decisions, when workloads are discussed honestly, when development is not postponed indefinitely, and when employees see evidence that their contribution is known.
The work is not dramatic.
It is often a series of small interactions that communicate:
I know what you are working on.
I understand what is getting in your way.
I see what you contribute.
I know what you want to learn.
I will tell you honestly what I can and cannot change.
And when action is possible, I will take it.
Employees may still leave. Sometimes leaving is the right decision for them.
But organizations should not be surprised by departures they never made a serious effort to understand.
Turnover may appear as one sudden line breaking.
In reality, the pulse was changing long before it stopped.