Retention Begins Before the Resignation

A resignation letter is a late signal. Employees often evaluate whether to stay long before they start applying elsewhere. They notice whether promises are kept, whether workload is sustainable, whether decisions are fair and whether there is a credible future for them. Retention strategies that begin only after an employee signals departure may miss the conditions that made leaving attractive.

Define which retention matters

Not every departure has the same organisational consequence. Retirement, planned career movement, poor fit, performance-related exit and the loss of scarce expertise should not be treated as equivalent. Define regretted or critical turnover carefully, and avoid using the label simply to express a manager’s preference for a particular employee.

Look at patterns by role, skill, tenure, manager, location and career stage where sample sizes allow. Aggregate rates can hide concentrated risk. At the same time, small groups require privacy safeguards and careful interpretation. Data should prompt questions, not become a ranking tool that unfairly labels teams.

For leaders, the implication is to make the underlying assumption visible and test it against the organisation’s actual context. The same practice can produce different results across roles, sectors and operating conditions. Define the decision, identify what evidence would change it, and record the limits of the analysis so that a useful framework does not become a rigid rule.

Examine the employee value proposition in practice

Employees compare the full experience: pay, benefits, meaningful work, manager support, flexibility, workload, development and perceived fairness. A retention bonus may address an immediate market pressure but cannot reliably compensate for poor management or an unsustainable role. Diagnose the actual reasons people stay and leave before selecting an intervention.

Use exit interviews as one source, not the only source. People may be cautious when leaving or may describe the most immediate reason rather than the full history. Combine exit information with stay conversations, employee listening, internal mobility data and evidence about work conditions.

For leaders, the implication is to make the underlying assumption visible and test it against the organisation’s actual context. The same practice can produce different results across roles, sectors and operating conditions. Define the decision, identify what evidence would change it, and record the limits of the analysis so that a useful framework does not become a rigid rule.

Managers shape everyday decisions

Managers influence clarity, feedback, recognition, workload, development and the response to problems. Their impact depends on capability and on the system around them. A manager cannot sustainably fix chronic understaffing or contradictory priorities through empathy alone, but can still improve how expectations are communicated and concerns escalated.

Help managers hold structured stay conversations focused on what enables good work, what creates friction, where employees want to grow and what might cause them to consider leaving. Do not turn the conversation into a promise that every preference will be met. Record themes responsibly and follow up on commitments.

For leaders, the implication is to make the underlying assumption visible and test it against the organisation’s actual context. The same practice can produce different results across roles, sectors and operating conditions. Define the decision, identify what evidence would change it, and record the limits of the analysis so that a useful framework does not become a rigid rule.

Create visible pathways for growth

Employees are more likely to see a future when skills and progression expectations are understandable. Career development does not always mean promotion; it may involve deeper expertise, a lateral move, a stretch assignment or a new type of responsibility. If advancement depends on informal sponsorship alone, access can become inconsistent.

Map critical skills and plausible pathways. Make internal opportunities visible and encourage managers to support movement where it serves the wider organisation. Retaining an employee in the wrong role can be less valuable than helping that person move to a role where their contribution is stronger.

For leaders, the implication is to make the underlying assumption visible and test it against the organisation’s actual context. The same practice can produce different results across roles, sectors and operating conditions. Define the decision, identify what evidence would change it, and record the limits of the analysis so that a useful framework does not become a rigid rule.

Address workload and fairness

Workload, scheduling, resources and inconsistent treatment can make otherwise attractive employment difficult to sustain. Review overtime, leave patterns, unresolved vacancies, work allocation and employee feedback. Where people are leaving because the role is structurally unsustainable, individual resilience training is not an adequate substitute for redesign.

The WHO and ILO’s guidance on mental health at work recommends organisational action to address psychosocial risks and support workers. This provides a useful reminder that retention is connected to work design and working conditions, not only individual attitude: https://www.who.int/publications/i/item/9789240057944.

For leaders, the implication is to make the underlying assumption visible and test it against the organisation’s actual context. The same practice can produce different results across roles, sectors and operating conditions. Define the decision, identify what evidence would change it, and record the limits of the analysis so that a useful framework does not become a rigid rule.

Measure and learn

Track critical turnover alongside internal mobility, time in role, engagement or experience signals, manager practices and relevant labour-market context. Monitor whether interventions change the experience rather than assuming that a lower exit rate is automatically positive. Very low turnover can also signal limited mobility or a lack of external opportunity.

Evaluate initiatives with a clear theory of impact. If a pay adjustment is expected to reduce exits in a scarce role, identify the affected population, baseline and review period. Consider other factors that may influence the outcome and protect employee data when reporting results.

For leaders, the implication is to make the underlying assumption visible and test it against the organisation’s actual context. The same practice can produce different results across roles, sectors and operating conditions. Define the decision, identify what evidence would change it, and record the limits of the analysis so that a useful framework does not become a rigid rule.

Applying the analysis in practice

Choose a specific moment rather than trying to redesign the entire employee lifecycle at once. A promotion decision, onboarding hand-off, equipment request or return-to-work process can be mapped with the people who use it. Record the steps, wait times, information requested more than once, unclear decisions and the points where employees need informal assistance to make progress.

Co-design a simpler future process with employees and operational owners. Define the minimum controls required, what information is genuinely necessary, who can decide and how exceptions are handled. Pilot the design with a representative group, then compare the old and new experiences. Include quality, accessibility and fairness in the evaluation, not just speed.

Publish a short response after implementation: what changed, what did not, what the pilot showed and who owns the next improvement. This demonstrates that experience work is an operational discipline with follow-through, rather than a temporary engagement campaign. It also gives employees a realistic basis for judging whether the organisation learns from their experience.

A process improvement should account for different employee circumstances. Frontline, remote, shift-based and office-based workers may face different access constraints. Employees with disabilities or different language needs may encounter barriers that are invisible in a standard journey. Include representative users and test accessibility rather than assuming that one successful pilot works equally well for everyone.

Decide how the process will be maintained after launch. Assign an owner to monitor recurring friction, review complaints and update guidance when policies or systems change. Without ownership, processes tend to accumulate exceptions and workarounds again. A periodic review should ask whether the intended experience still matches the way the work is actually performed.

The most meaningful experience measures are often close to the process itself. For onboarding, that might mean whether employees have the access, equipment and information needed to contribute; for internal mobility, it might mean how long decisions take and whether candidates receive clear feedback. Pair these indicators with employee perspectives so the organisation can distinguish a fast process from a good one.

Avoid treating employee experience as a separate layer of comfort added after productivity work is complete. Removing unnecessary friction can support both employee dignity and operational reliability. However, not every control is unnecessary, and not every preference can be met. Explain the purpose of essential steps and simplify the parts that do not add proportionate value.

Treat the redesign as a continuing service improvement. Collect feedback after the change, observe how the process works under real demand and make it easy to report new friction. The objective is not a perfect journey map; it is a process that remains clear, accessible and reliable as circumstances change.

Diagnose the conditions behind avoidable exits

Retention is not the same as preventing every departure. The aim is to retain critical capability while improving the conditions that make people able and willing to contribute. This distinction matters because organisations can become very active without becoming more effective. New programmes, policies, dashboards and training sessions may all be well intentioned, yet their combined effect depends on whether they address the actual constraint in the work. Leaders should therefore resist beginning with the intervention they already know how to purchase or deliver. Begin instead with a clearly framed decision: what must improve, for whom, over what period, and what evidence would indicate that the current approach is not working?

A useful diagnostic compares three layers. The first is the intended outcome: the customer, operational or workforce result the organisation is trying to achieve. The second is the operating mechanism: the work, decisions, capabilities, resources and relationships that are expected to produce that result. The third is the observed experience: what employees and managers actually encounter, including delays, exceptions, workarounds and competing demands. The gap between these layers is often more informative than a single performance score.

For example, imagine a service team missing response-time commitments. It would be premature to conclude that the team simply needs more people. The organisation should test whether demand is forecast accurately, cases are routed to the right capability, staff have authority to resolve common issues, knowledge is accessible, and performance measures reward resolution rather than speed alone. The example is illustrative, not a claim about a specific employer. Its purpose is to show how a symptom can have several possible causes—and why diagnosis should precede investment.

A retention review that goes beyond perks

Translate the diagnosis into a small number of explicit design choices. State the problem in operational language, identify the people affected, and describe the mechanism through which the proposed change is expected to work. Record the assumptions behind that mechanism. If the intervention depends on managers having time to coach, for instance, the plan must address workload and priorities; a manager-training course cannot create time that the operating model does not provide.

1. Establish a baseline. Agree on definitions and capture the current level of performance, experience, cost, quality or risk. Note where the data is incomplete or unreliable.
2. Identify the constraint. Use process observation, employee input, operational data and manager judgement together. Treat each source as partial evidence rather than assuming one source explains the whole system.
3. Choose a proportionate intervention. Consider process redesign, clearer decision rights, role changes, capability development, technology, incentives or staffing. Explain why the chosen option is more plausible than alternatives.
4. Run a bounded test where feasible. Define the population, duration, expected signal and safeguards. A pilot can reveal implementation issues, but it does not automatically prove that an intervention caused the outcome.
5. Assign ownership and review. Name the decision owner, the people responsible for delivery, the review date and the conditions under which the organisation will adapt, scale or stop the intervention.

This discipline is not bureaucracy for its own sake. It reduces the risk of solving the wrong problem, makes trade-offs visible and helps leaders learn when conditions change. It also makes the work of HR, operations, finance and technology more coherent: each function can contribute its expertise to a shared problem statement instead of optimising its own activity in isolation.

What to measure—and what not to assume

Use a balanced set of measures. A leading indicator may show whether a necessary practice is happening; a lagging indicator shows whether the desired result is appearing. Pair operational measures with relevant employee or customer experience evidence. Check whether apparent improvement in one measure creates a cost elsewhere—for example, faster case closure accompanied by more repeat contacts, or lower turnover accompanied by declining internal mobility.

Interpret results in context. Differences between teams may reflect workload, customer mix, role complexity, local labour markets or management changes rather than the intervention being evaluated. Where possible, compare like with like, document changes that occurred during the measurement period, and avoid claiming causation from a simple before-and-after comparison. Qualitative evidence can help explain a pattern, but anecdotes should not be presented as proof of prevalence.

Turnover data should be interpreted alongside role criticality, labour-market context, tenure, mobility and employee feedback. Use the original source to understand its scope, methodology and limitations before applying a finding to a different organisation, geography or workforce. External research can inform a decision; it cannot replace local diagnosis. The strongest professional judgement combines credible published evidence with transparent assumptions and the organisation’s own operational facts.

The executive question is therefore not merely, “Did we deliver the programme?” It is, “Did the change improve the condition we intended to improve, for the people and business outcomes that matter, and what evidence supports that conclusion?” That question moves the discussion from activity reporting to organisational learning.

A practical action plan

• Define the business question and the outcome that should change.
• Gather relevant quantitative and qualitative evidence; document limitations.
• Agree on a small number of actions, accountable owners and review dates.
• Measure intended outcomes and unintended consequences, then adjust.

Questions for leaders

• What business outcome is this issue affecting in our organisation?
• What evidence would distinguish a root cause from a symptom in the current situation?
• Which decision or practice should change first, and who owns it?
• How will we know whether the change helped, and what unintended effects should we watch for?

The point

Retention is a property of the relationship between people and the work system. Understand which departures matter, examine the experience before resignation, equip managers, create credible pathways and address structural sources of friction. A good retention strategy gives people reasons to stay without pretending the organisation can or should keep everyone forever. The practical test is whether the organisation can explain the choice it made, show how the evidence informed it and learn from what happened next.

References and further reading

The following sources inform the analysis. They provide evidence and guidance; their findings should be interpreted within their stated scope and context.

• WHO and ILO — Mental health at work: policy brief
• CIPD — Good Work Index