Retention: knowing each person's actual motivator

What it is

Retention as a lead's discipline is two things: knowing what each individual actually wants, which is usually not what you assume, and noticing the departure three months before the resignation.

The six motivators, and they are not equally distributed:

  SCOPE        wants a bigger problem, more ownership, harder
               work
  LEARNING     wants to be growing; boredom is their exit signal
  MONEY        wants compensation, and says so or does not
  TITLE        wants the label, often for reasons outside this
               company (visa, family, next role, credibility)
  FLEXIBILITY  wants control over when and where; often
               non-negotiable for reasons you do not see
  TEAMMATES    stays for the people; the exit signal is someone
               else leaving

Most people have a primary and a secondary, and they change over time. A person motivated by learning at 26 may be motivated by flexibility at 34 for reasons that have nothing to do with work, and a lead operating on a two-year-old model of them is managing someone who no longer exists.

What this is confused with: engagement surveys and perks. An aggregate satisfaction score tells you the team's average and nothing about the person who is leaving. Retention is individual, and the information is in one-to-ones, not in a dashboard.

Also confused: retention and counter-offers. By the time someone has an offer, the decision is mostly made, and a counter-offer resolves the symptom that was easiest to name. Most regretted attrition is visible three months out, and that is where the intervention belongs.

The problem it solves

The default failure is a lead who assumes their own motivator is universal.

A lead motivated by scope, managing five people:

  Alex   also scope-motivated. Well served, gets bigger problems.
  Sam    learning-motivated. Given more of the same work, which
         reads to the lead as "trusting them with the important
         system" and reads to Sam as being stuck.
  Priya  flexibility-motivated, with a caregiving situation the
         lead does not know about. Offered a promotion that comes
         with more meetings at fixed times. Declines. The lead
         reads this as low ambition.
  Jo     money-motivated, in a market where their skills are
         repricing. Has never raised it, because raising it feels
         crass. Interviewing.
  Dev    teammate-motivated. Fine, until Alex leaves.

Four of five are being managed against the wrong model, and the
lead's own read is that the team is "solid".

And the cost of one regretted departure is large and mostly invisible:

Direct:      recruiting fees or recruiter time, interview loop
             time across 5 to 8 people, onboarding
Indirect:    3 to 6 months to full productivity for a
             replacement, and the departing person's knowledge
             leaves with them
Second-order: the team's remaining members reassess. A senior
             departure is often followed by others within two
             quarters, because it makes leaving thinkable.

Conservative estimates for a senior engineer commonly land
between six months and a year of salary, all in, and the
second-order effect is the part that is never counted.

Mechanics

Finding the actual motivator

You cannot ask "what motivates you" and get a useful answer, because people answer with what they think is expected. Ask about specifics and infer.

Questions that produce real information:

  "What was the best three-month stretch you've had at work,
   here or anywhere? What made it good?"
  -> the answer names the motivator without the person having
     to classify themselves.

  "If you could stop doing one thing entirely, what would it
   be?"
  -> the friction. Often flexibility or scope in disguise.

  "What's something you want to be able to do in two years that
   you can't do today?"
  -> learning, and specifically which learning.

  "When you look at people a level or two above you here, whose
   job would you actually want?"
  -> distinguishes people who want the next level from people
     who want more of what they do now, which is the most common
     mismatch in promotion conversations.

  "Is there anything about how we work that's harder for you
   than it needs to be?"
  -> the flexibility question, asked in a way that does not
     require disclosing why.

And then watch what they choose when given a choice, because stated and revealed preferences differ:

Offered an interesting but low-visibility project versus a
routine but high-visibility one:
  takes the interesting one   -> learning or scope
  takes the visible one       -> title, or promotion-directed

Offered a conference or the equivalent in a bonus:
  -> learning versus money, cleanly

Consistently protects a specific time block
  -> flexibility, and the reason is not your business unless
     they offer it

Write it down, per person, and revisit it every six months, because the failure is not usually ignorance, it is an out-of-date model.

The three-month signals

Most regretted attrition is visible in advance if you are looking, and the signals are behavioural rather than stated.

STRONG SIGNALS (something changed)
  - stopped arguing. A person who used to push back in design
    reviews and now agrees with everything has disengaged, not
    mellowed. THIS IS THE EARLIEST AND MOST RELIABLE SIGNAL.
  - stopped talking about the future. No more "next quarter we
    should", no opinions about the roadmap.
  - declining optional things they used to do: interviews,
    onboarding, the guild, the brown bag.
  - suddenly using vacation in single days, or a cluster of
    "appointments"
  - their work is fine and their initiative is gone. Tickets
    closed, nothing proposed.
  - social withdrawal: leaves the team channel banter, stops
    joining the optional coffee

WEAK SIGNALS (often nothing)
  - LinkedIn activity. Recruiters spam everyone.
  - one bad week
  - complaining. A person who complains is still invested;
    the ones who stop complaining are the ones to worry about.

"Stopped arguing" is the signal worth memorising, because it is early, behavioural, and counter-intuitive: engagement looks like friction, and a lead who enjoys the quieter version has mistaken disengagement for maturity.

Acting on a signal

DO NOT: ask "are you thinking of leaving?" It is unanswerable
        honestly, and it puts the person in the position of
        either lying or disclosing before they are ready.

DO:     name the change, specifically, and ask an open question.

  "You used to push back hard in design reviews and I've noticed
   you haven't in a while. That was useful to me and I miss it.
   What's changed?"

That is SBI feedback applied to a retention signal: a specific
situation, an observable behaviour, and the impact, followed by
a question rather than a conclusion.

The answers you get are usually one of:
  - a specific grievance you can address
  - "I'm bored", which is a fixable assignment problem
  - "I don't think I'm going anywhere here", which is a
    fixable-if-true career conversation
  - a life change you did not know about
  - or nothing, in which case you have at least signalled that
    you are paying attention

Recognise before they ask

The rule: address the motivator before the person raises it,
because by the time they raise it, they have already spent
weeks deciding whether to.

MONEY      Do the market check yourself, annually, per person.
           If someone is 15% below market for their level, that
           is your problem to fix before they discover it, and
           an off-cycle adjustment costs a fraction of a
           replacement.
           The uncomfortable truth: people rarely ask, and the
           ones most underpaid are often the ones least likely
           to.

SCOPE      Give the bigger problem before they ask for it. A
           person who has to ask for scope has already
           concluded you were not going to offer it.

LEARNING   Rotate deliberately. Boredom in a strong engineer is
           a retention risk with a cheap fix, and it is almost
           always cheaper than the replacement.

TITLE      Find out WHY the title matters. Sometimes it is a
           visa, a family expectation, or a credibility problem
           with an external partner, and some of those have
           solutions that are not a promotion.

FLEXIBILITY Say yes where you can, quickly, and without
           requiring an explanation. The cost is usually near
           zero and the loyalty return is disproportionate.

TEAMMATES  When someone leaves, the follow-up conversation with
           their closest colleagues is not optional. A
           departure makes leaving thinkable for everyone
           nearby.

The money one deserves the emphasis: internal raises are almost always cheaper than replacement, and the arithmetic is not close, yet the process for a proactive adjustment is usually harder than the process for a backfill requisition. That asymmetry is an organisational bug a lead can sometimes fix by arguing it in advance rather than in a resignation week.

The stay conversation

Run it before there is a problem, once or twice a year, explicitly framed.

"This isn't a performance conversation and it isn't a career
 plan. I want to know what would make you stay for another two
 years, and what would make you leave. You don't have to answer
 the second one."

Then ask:
  - "What is the best part of your job right now?"
  - "What is the part you'd change if you could?"
  - "What would another company have to offer you for you to
     take the call seriously?"   <- the most informative
     question, and it works because it is hypothetical
  - "Is there anything you want that you haven't asked for
     because you assumed the answer was no?"

The last question is the one that surfaces flexibility and
scope requests people have silently written off.

Counter-offers

The position: usually do not, and know why.

By the time someone has an offer:
  - the decision is mostly made; the offer is the conclusion of
    a process that started months earlier
  - a counter-offer fixes the most nameable reason, usually
    money, which is often not the actual reason
  - published follow-up on accepted counter-offers is
    consistently poor: a large fraction leave within a year
    anyway
  - and it teaches the team that resigning is the mechanism for
    a raise

THE EXCEPTIONS, and they are real:
  - the reason is genuinely and solely compensation, they are
    genuinely underpaid, and you can fix it permanently rather
    than as a retention bonus
  - the departure is catastrophic on a specific timeline and you
    need three months, in which case be honest that it is a
    bridge

Either way, treat the resignation as a failure of the previous
three months, and run the retrospective on yourself.

A worked example: five people, five different problems

A team of nine, two regretted departures in the previous year, a third person the lead suspected was looking. The lead's own model, written down before the conversations, turned out to be wrong for four of the five people they examined.

The stay conversations, run over two weeks:

PERSON   lead's assumed motivator   actual
------------------------------------------------------------
Alex     scope                      scope. Correct.
Sam      scope (they were the       LEARNING. "I've been the
         strongest engineer, so      streaming person for two
         the lead assumed they       years. I could do it in my
         wanted more of it)          sleep, and that's the
                                     problem."
Priya    money                      FLEXIBILITY. Had declined a
                                     promotion because it added
                                     three fixed-time meetings a
                                     week, and had never
                                     explained why.
Jo       learning                   MONEY. Market for their
                                     specialisation had moved.
                                     Had never raised it: "it
                                     felt like a bad look."
Dev      teammates                  TITLE, for a specific
                                     external reason: a
                                     permanent-residency
                                     application where the job
                                     title was material.

Four of five wrong is not unusual, and each wrong model had produced a specific management error:

Sam:   given MORE streaming work, as a reward. Read as being
       trapped.
Priya: read as unambitious for declining a promotion, which had
       quietly affected how the lead assigned work.
Jo:    given conference budget and interesting problems, which
       they enjoyed and which did not address the thing.
Dev:   given more responsibility without a title change, which
       was precisely the wrong currency.

The interventions, and their cost:

SAM (learning): moved off streaming as primary within six weeks,
  onto the new search-relevance work, which was genuinely
  unfamiliar. Paired with the job of growing Priya into
  streaming, which also fixed a bus factor.
  Cost: about six weeks of reduced throughput.
  Sam, six months later: "this is the first time in two years
  I've had to look something up."

PRIYA (flexibility): the three fixed meetings became two, one
  async. The promotion was re-offered and accepted.
  Cost: near zero. The lead's own note: "this was available the
  entire time and I never asked."

JO (money): market check confirmed roughly 18% below the current
  market for their specialisation. The lead built the case with
  three comparable data points and took it to their director as
  a retention risk with a number attached, before Jo had an
  offer.
  Outcome: an off-cycle adjustment of 14%, six weeks later.
  Cost of the adjustment, annualised: roughly a fifth of the
  all-in cost of replacing them.
  Jo's reaction, which is the part worth recording: relief,
  followed by "I didn't know that was something I could ask
  for."

DEV (title): the title mattered for a permanent-residency
  application, which the lead had no way to know and Dev had not
  volunteered because it felt like a personal matter. The
  company had a "Senior Engineer II" title that existed in the
  ladder and was not being used. Dev met the bar for it on the
  rubric. Granted at the next cycle, three months early.
  Cost: zero, other than the calibration conversation.

ALEX (scope): already correct. Given the cross-team platform
  ownership, which was the next available scope.

Two of the four fixes cost essentially nothing and had never been asked for, which is the recurring finding: the constraint was information, not budget.

The three-month signal, caught on the third person:

The engineer the lead suspected was looking had stopped pushing
back in design reviews about two months earlier. The lead had
noticed it and read it as "they've settled in".

The conversation, using SBI:
  "You used to be the person who found the hole in a design, and
   you haven't done that in a couple of months. That was useful
   to me and I've missed it. What changed?"

The answer: they had proposed a significant architectural
direction eight months earlier, it had been declined without a
reason they found satisfying, and they had concluded that
proposing things was not worth the effort.

That is a specific, addressable, entirely self-inflicted
problem. The lead's fix: revisited the original proposal
properly, wrote down why two-thirds of it was now viable and
one-third was not, and gave them the two-thirds to own.

They stayed. Their own later account was that the decision to
leave had been about 70% made when the conversation happened.

"Stopped arguing" was the only visible signal and it had been misread as maturity, which is the specific error this page exists to prevent.

Twelve months later:

                              before      after
regretted attrition        2 in 12 mo      0
people >10% below market        2           0 (both adjusted)
declined promotions             1           0
average tenure at review
  of motivator model           n/a      6 months, written down
stay conversations held         0        2 per person per year

And the honest caveat the lead recorded:

One of the two fixes that "cost nothing" (Priya's meetings) was
only free because the lead had authority over the meeting
structure. The money fix required a director who was willing to
run an off-cycle adjustment, which is not universally available.

Recorded so that the next person reading this does not conclude
that all retention problems are free to fix. Some are budget
problems, and the lead's job there is to make the arithmetic
visible early rather than to pretend otherwise.

Production evidence

Exit-interview research consistently finds that the reasons people give for leaving differ from the reasons that actually drove the decision, and that the decision typically forms over months, which is the empirical basis for the three-month window and for the limited value of counter-offers.

Published analyses of accepted counter-offers consistently report high subsequent turnover within a year, which is the evidence behind treating a counter-offer as a bridge rather than a fix.

Cost-of-turnover estimates for technical roles commonly range from six months to over a year of salary when recruiting, interviewing, onboarding and time-to-productivity are included, which is what makes a proactive market adjustment cheap by comparison.

Google's Project Oxygen identified career development and individual attention among the manager behaviours most associated with team outcomes, and its finding that managers matter measurably for retention is the large-sample version of this page's argument.

Self-determination theory (Deci and Ryan), and Daniel Pink's popularisation as autonomy, mastery and purpose, is the research basis for treating motivation as individually varied and largely intrinsic above a compensation threshold, which is why a single perk or a single lever does not work across a team.

"Stay interviews" are an established retention practice in HR literature, explicitly designed to gather the information an exit interview gathers, at a point where it can still be used.

The debate

Should you ask directly whether someone is leaving? No. It is unanswerable honestly and forces a disclosure before they are ready, and the answer you get is uninformative either way. Naming the observed behavioural change and asking an open question gets the real information, because it is about something specific you both saw.

Are counter-offers ever right? Rarely, and the two exceptions are real: when the reason is genuinely and solely compensation and you can fix it permanently, and when you need a specific bridge and are honest that it is one. Otherwise it fixes the most nameable reason rather than the actual one, and it teaches the team that resigning is the raise mechanism.

Is it the lead's job to fix compensation? To surface it with data, yes, always. The counter-argument that compensation is HR's domain is how people end up 18 percent below market without anyone noticing, and the person most underpaid is often the one least likely to raise it. The lead may not control the outcome; they control whether the arithmetic is visible before the resignation.

Do stay conversations feel artificial? Somewhat, the first time, and the framing removes most of it: saying explicitly that it is not a performance conversation and not a career plan resets the expectation. The alternative is learning the same information in an exit interview, where it is free to say and useless to act on.

Is high retention always good? No. A team with zero turnover for years accumulates a fixed set of perspectives and often has people who have stopped growing and stayed anyway. The goal is zero regretted attrition, and distinguishing the two honestly is part of the job.

Should you tell someone their motivator? Not as a label. Use it to make decisions, not to categorise people to their face, because the categories are a lead's working model rather than a truth about anyone, and being told you are "money-motivated" lands badly and inaccurately.

Follow-up Q&A

"How do you find out what actually motivates someone?"

Not by asking what motivates them, because people answer with what they think is expected. Ask about specifics and infer: what was the best three-month stretch you have had and what made it good; if you could stop doing one thing entirely what would it be; whose job a level or two above you would you actually want. Then watch revealed preference, which is what they choose when given a real choice between an interesting low-visibility project and a routine high-visibility one, or between a conference and the equivalent bonus. Write it down per person and revisit every six months, because the usual failure is an out-of-date model rather than no model.

"What is the earliest reliable signal that someone is leaving?"

They stopped arguing. A person who used to push back in design reviews and now agrees with everything has disengaged, and it is counter-intuitive because it looks like maturity and it is more comfortable for the lead. Other behavioural signals: no more opinions about next quarter, declining the optional things they used to do like interviews and onboarding, initiative gone while output stays fine. Weak signals include LinkedIn activity and complaining, and complaining is genuinely inverted: someone who complains is still invested, and the ones who stop are the ones to worry about.

"What do you do when you see the signal?"

Not "are you thinking of leaving," which is unanswerable honestly and forces a premature disclosure. Name the specific change with the impact and ask an open question: "you used to be the person who found the hole in a design and you haven't in a couple of months; that was useful to me and I've missed it, what changed?" In one case the answer was that a proposal had been declined eight months earlier without a satisfying reason, and they had concluded proposing things was not worth it. The decision to leave was about 70 percent made, and the fix was revisiting the proposal properly and giving them the two-thirds that was still viable.

"Why is a proactive market adjustment the right move?"

Because replacement costs commonly run from six months to over a year of salary all in, so a 14 percent adjustment is a fraction of the alternative, and because the people most underpaid are often the least likely to raise it. In one case an engineer was 18 percent below market for their specialisation and had never mentioned it because "it felt like a bad look." Their reaction to the adjustment was relief followed by "I didn't know that was something I could ask for." The lead's job is to do the market check annually per person and make the arithmetic visible before the resignation, even where they do not control the outcome.

"Should you counter-offer?"

Usually not. By the time there is an offer, the decision formed months earlier and the offer is the conclusion; a counter fixes the most nameable reason, usually money, which is often not the actual one; accepted counter-offers show consistently high subsequent turnover; and it teaches the team that resigning is the raise mechanism. The real exceptions are a genuine and sole compensation gap you can fix permanently rather than as a retention bonus, and a specific timeline where you need a bridge and say honestly that it is one. Either way the resignation is a failure of the previous three months, and the retrospective is on yourself.

"What is a stay conversation and how do you frame it?"

A twice-yearly conversation explicitly framed as neither a performance review nor a career plan: what would make you stay another two years, and what would make you leave, and you do not have to answer the second. The most informative question is hypothetical, "what would another company have to offer for you to take the call seriously," because it is safe to answer honestly. The most useful is "is there anything you want that you haven't asked for because you assumed the answer was no," which surfaces the flexibility and scope requests people have silently written off, and those are often the ones that cost nothing.

Common misconceptions

"Everyone is motivated by growth and interesting work." That is one of six motivators, and it is frequently the lead's own, projected onto the team.

"A complaining engineer is a flight risk." Complaining is investment. The one who stopped complaining and stopped arguing is the one to worry about.

"Ask them if they are happy." It is unanswerable honestly. Name a specific behavioural change and ask what happened.

"If they wanted more money they would ask." The most underpaid people are frequently the least likely to ask, and the lead's annual market check is the mechanism that does not depend on them asking.

"A counter-offer buys you time." Sometimes, and it usually fixes the most nameable reason rather than the real one, with high subsequent turnover and a lesson for the rest of the team.

"Zero attrition is the goal." Zero regretted attrition is. A team with no turnover for years often contains people who stopped growing and stayed.

Interview delivery note

Say this verbatim: "Most regretted attrition is visible three months out, and the earliest signal is that they stopped arguing. Someone who used to find the hole in a design and now agrees with everything has disengaged, not matured, and it is easy to miss because the quieter version is more comfortable for the lead." It is specific, counter-intuitive, and it is the observation that separates a lead who watches people from one who watches tickets.

The senior-versus-staff separator is doing the market check before anyone asks. A senior lead responds to a resignation. A staff lead runs an annual per-person market comparison, finds someone 18 percent below market for their specialisation, builds the case with three comparable data points, and takes it to their director as a retention risk with a number attached before an offer exists. The arithmetic, an adjustment costing a fraction of a replacement, is available to anyone; making it visible in the right week is the leadership.

The second signal is assuming your model of each person is wrong until checked. Saying "I wrote down what I thought motivated each of five people and I was wrong about four, and each wrong model had produced a specific management error, giving the bored engineer more of the work they were bored by and reading a flexibility constraint as low ambition" demonstrates that you treat your own read as a hypothesis.

The Staff & Team Lead Interview Reference