In this article
  1. Stop treating every departure as the same problem
  2. Check the basic employment bargain first
  3. Your reliable people may be paying a reliability tax
  4. Growth needs a shape people can see
  5. Listen while there is still something to change
  6. A hypothetical example: the product lead who stops caring
  7. Measure the repair, not the enthusiasm at the announcement
  8. Questions people ask

The resignation arrives politely. Someone says they have found an exciting opportunity. The manager says the market is impossible. HR updates the recruitment plan. Nobody mentions the previous year of interrupted work, vague promises and decisions that travelled around the company collecting stamps.

Why do your best employees leave? Sometimes another employer genuinely offers more money, a different career or a better location. Sometimes your organisation has made staying feel expensive. The useful question is what you could reasonably have changed before the person had to choose.

Stop treating every departure as the same problem

Employee turnover is a signal to investigate, not a verdict about your culture. Someone retiring, someone moving country and someone escaping a manager need different responses. A small company can have a frightening-looking rate after one departure. Context belongs beside the number.

The CIPD retention factsheet recommends understanding why people leave and considering flexibility, fair treatment and wellbeing. It does not give you a universal explanation for a particular resignation. Your own conversations and records still matter.

Group departures by role, team, tenure and the work conditions people describe. Check whether a pattern is real before naming a culprit. Protect privacy when groups are small. A spreadsheet called Anonymous Feedback can become surprisingly personal when it contains the only designer in the building.

Check the basic employment bargain first

Ask whether pay is fair for the responsibilities, whether workload is sustainable, and whether the job resembles the one you offered. Meaningful work cannot compensate indefinitely for an unfair deal. Equally, an expensive salary does not make daily humiliation or permanently shifting expectations acceptable.

A useful manager question is: “Which part of this role feels different from what we agreed?” Listen for expanding scope without support, invisible responsibilities and promises that never became decisions. Write down the gap in plain language. Avoid defending the company while someone is explaining their experience.

If a pay adjustment is needed, discuss what is possible, who decides and when. If you cannot provide a promotion, say so honestly and describe available development. An uncertain promise repeated every quarter is still uncertain. It merely has a more established calendar invitation.

Your reliable people may be paying a reliability tax

Capable colleagues are often the easiest people to ask for one more rescue. Over time they become the unofficial help desk, late-stage reviewer and emergency owner of whatever was insufficiently planned. Their apparent success can hide a job nobody would knowingly design.

For a week, review the work that arrives outside their planned responsibilities. Who requests it? What original failure created it? Is it genuinely urgent or just late? Then decide what to remove, distribute, document or refuse. Praise without changing the pattern leaves the same person holding the same bag.

Ask: “If you took a proper week off, what would stop working?” Treat the answer as a system weakness rather than a compliment to their indispensability. Build coverage with time allocated for teaching. Delegating responsibility without handing over knowledge only moves the emergency.

Growth needs a shape people can see

“There are lots of opportunities here” is difficult to act on. An employee needs to know what they can learn, what responsibility they can earn and how progress will be assessed. A title may matter, but so may access to customers, ownership of a meaningful problem or better technical depth.

Separate development from promotion. A company may have no management vacancy, yet still be able to offer a serious specialist path. Agree on one learning goal and one useful responsibility that supports it. Also agree what existing work will stop so development does not become evening homework.

Do not assume every strong employee wants to manage people. Ask them. Someone can love difficult product problems and dislike administering leave requests. Your succession plan should contain actual preferences, rather than a collection of people who nodded when surprised in a meeting.

Listen while there is still something to change

A retention conversation should happen before an exit interview. Try: “What currently makes this a good place for you to work? What repeatedly gets in the way? If nothing changed, which part would become hardest to accept?” These questions invite concrete experiences without demanding a confession about job applications.

Make it safe to disagree with you and useful to do so. Amy Edmondson's study of work teams found an association between psychological safety and learning behaviour. That finding supports taking speaking-up conditions seriously; it does not establish that any particular conversation will prevent a resignation.

After listening, send a short record: the issue, the action you can take, the owner and the review date. Explain what you cannot change. A modest action completed reliably is more credible than a dramatic retention initiative that disappears after the next leadership offsite.

A hypothetical example: the product lead who stops caring

Imagine a product lead who once challenged every unclear requirement and now quietly accepts them. It would be easy to label this disengagement. In this hypothetical example, repeated customer concerns were overruled, and the lead was still accountable for the results. Silence became a way to conserve effort.

The founder asks for specific recent decisions, not an attitude improvement. Together they clarify which product decisions the lead owns, how disagreements are escalated and what evidence changes a priority. The founder cancels an unnecessary reporting task so the lead has time for customer discovery.

That intervention might help if decision friction was central. It might not help if the employee wants a different career, or if trust has already gone. Retention work creates better reasons to stay. It cannot give an employer ownership of another person's future.

Measure the repair, not the enthusiasm at the announcement

Track whether agreed actions happen, whether recurring work friction reduces and whether people can describe their responsibilities clearly. Review workload and departures alongside these observations. Avoid inventing a single happiness score that is supposed to explain every team, season and professional ambition.

Counteroffers also deserve care. A salary increase may resolve a real pay problem. It will not automatically repair an absent manager, blocked career or broken trust. Consider the impact on colleagues and the consistency of your reward decisions, rather than turning every resignation into a private auction.

For a wider view of valuable contributions, read which people help a business grow. For career conversations, the promotion discussion guide explains how vague appreciation can become a concrete decision.

If your retention problem sits inside confusing responsibilities, product priorities or constant emergency work, I can help map the friction and bring the right people into a useful conversation. My work combines product leadership, delivery and corporate training. Tell me what keeps repeating in your team, and we can define a practical starting point.

Questions people ask

Why do high-performing employees leave a company?

Possible reasons include unfair pay, sustained overload, limited development, unclear responsibility and a working relationship that no longer feels worthwhile. Other departures reflect personal goals or better opportunities outside the company. Ask about specific experiences and look for patterns across departures. Do not assume one explanation applies to everyone, or interpret every departure as proof that management failed.

How can HR improve employee retention without a large budget?

Start with issues the organisation can actually change: clarify responsibilities, keep development promises, improve access to decisions and remove repeated unnecessary work. Discuss pay and workload honestly rather than presenting low-cost gestures as substitutes. Record an owner and review date for each action. Prioritise the friction employees identify, and check whether your changes helped before expanding the programme.

Should a company make a counteroffer to keep a good employee?

A counteroffer can be appropriate when it addresses a genuine, fixable gap and fits a fair reward approach. First ask what the employee wants and whether the underlying issue is salary, work design, trust or career direction. Do not pressure someone to stay. Consider consistency with colleagues and accept that a considered decision to leave may remain the right choice.

Something here sounds like your workplace?

Let’s have a real conversation ↗